---
sourceDocument: Australia Service Exchange
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/service-exchange

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Service Exchange

ft:clusterId :

    - sebrdg

bundleId :

    - sebrdg

workflow :

    - Customer and Industry


---

# Transform framework

# Transform data with the Service Exchange transform framework {#ariaid-title1}

Release version: Australia  
Updated May 13, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Transform data with the Service Exchange transform framework

The Service Exchange Transform Framework enables seamless integration and data transformation of remote tasks between two ServiceNow instances.
It supports the exchange of incidents, cases, and service requests by converting data between corresponding tables and fields, facilitating clear communication between providers and consumers during issue resolution.
Show full answer Show less  

## Key Features

* **Transform Types:**
  * **Simple:** Uses predefined mappings for inbound and outbound fields, such as converting incident states between instances.
  * **Advanced:** Executes scripts to dynamically transform data values, for example correlating sysids in reference fields.
  * **Virtual Inbound:** Applies scripted transformation to inbound virtual fields with mandatory inbound field specification.
  * **Virtual Outbound:** Applies scripted transformation to outbound virtual fields with mandatory outbound field specification.
  * **Global:** Defines default transforms applicable to all consumer accounts, which are overridden by company or account-specific transforms.
* Transforms are reusable across multiple remote task definitions, promoting consistency and efficiency.
* The framework processes transforms twice per update to detect field changes, which may cause conditions to trigger actions twice; careful configuration is recommended to avoid false positives.

## Practical Guidance for ServiceNow Customers

Using the Transform Framework, ServiceNow providers can effectively manage inbound and outbound remote task data exchanges with consumers, ensuring data consistency and reducing manual effort. Customers should select appropriate transform types based on their data transformation needs and be aware of the double execution behavior to prevent unintended outcomes. Creating transforms once and applying them broadly simplifies ongoing management.  
Use the Transform Framework to integrate tasks between two ServiceNow instances to transform remote task data in the Service Exchange application.

As a provider, you can use the Transform Framework to transform your inbound and outbound data of the remote tasks between your ServiceNow instance and your consumer's instance. The data can be incidents, cases, and service requests. To learn what a remote task is, see [Remote tasks](https://www.servicenow.com/docs/sTSWmhW7LnpEdhW8zppZGg "Learn how you, as a provider, can resolve and fulfill multiple consumer tasks, such as incidents, cases, and service requests, by using remote tasks. Also as a consumer, you can assign the incidents to multiple providers for resolution.").

While using the Service Exchange for Providers application, you and your consumer can exchange the remote task data through tables and fields. The Transform Framework helps you to convert the data between those tables and fields. This
enables you and your consumer to easily communicate while resolving incidents, cases, and consumer requests. Transforms can be created once and used across all remote task definitions.  
You can use the following transform types in the Transform Framework for your remote tasks:

* Simple: Select the simple transform option to use the predefined values of the inbound and outbound fields for your remote tasks. For example, you convert the Open state of an incident in the provider's ServiceNow® instance to the In Progress state in the consumer's ServiceNow® instance.
* Advanced: Use an advanced transform where you run a script to determine the inbound and outbound data values for your remote tasks. For example, use this transform type to convert an incoming sys_id into a correlated sys_id for a reference field.
* Virtual Inbound: Use this to transform or set a value for an Inbound Virtual field. This option uses a script to transform the data and adds a mandatory Inbound Field field.
* Virtual Outbound: Use this to transform or set a value for an Outbound Virtual field. This option uses a script to transform the data and adds a mandatory Outbound Field field.
* Global: Use the global transform option to create a default transform definition that can be applied to all consumer accounts.  
  Note:  
  A matching company or account specific transform overrides the Global transform option.
{#service-bridge-v2-transform-about__ul_e3d_nfd_txb}  
Note:  
A transform runs twice on every update to determine which of the mapped fields have changed. If the transform includes a condition, that condition can be met on both runs, causing the action tied to it to run twice instead of once and produce a false positive. To learn more about the behavior, see [Service Bridge: Preventing False Positives in Service Bridge Transform Conditions](https://www.servicenow.com/community/technology-articles/service-bridge-preventing-false-positives-in-service-bridge/ta-p/3481929) on the ServiceNow Community.

To learn how to create a transform, see [Create a transform in Service Exchange](https://www.servicenow.com/docs/DfPfU5OFPgJ3~beVMHEZ_Q "As a provider or a consumer, create a transform in Service Exchange to integrate tasks between connected instances.").