--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Transform maps # Transform maps {#ariaid-title1} Release version: Brazil Updated September 10, 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 maps A transform map in ServiceNow defines how fields from an import set correspond to fields in an existing ServiceNow table, such as Incident \[incident\] or User \[sysuser\]. Once created, a transform map can be reused to map data from other import sets to the same target table, streamlining data integration tasks. The Transform Maps module allows administrators to specify destinations for imported data across any tables, using simple drag-and-drop operations to link source and destination fields dynamically. Show full answer Show less ## Key Features * **Auto-mapping:** The system can automatically map fields, but it is important to verify these mappings to avoid importing unnecessary or sensitive data, like encrypted passwords. * **Mapping Reference Fields:** When mapping reference fields, if the referenced sysid does not exist, the sysid may appear as a DisplayValue in the target record, which might be undesirable. Mapping many reference fields can affect performance due to validation checks. This overhead can be bypassed using transform scripts, such as setting target fields directly from source fields in onBefore scripts. * **Multiple Transform Maps:** Multiple transform maps can be applied to a single data source, but this generates one import set row per transform map, potentially creating many temporary records. Users can select multiple transform maps during data import, which are executed sequentially on the same import set. * **Transform Map Scripts:** These scripts allow customization of import operations with advanced logic. They integrate fully with the ServiceNow scripting environment and come in two types: * Explicit Transform Map scripts that define specific mapping rules * Transformation Event scripts that modify processing at different transformation stages ## Practical Benefits for ServiceNow Customers Transform maps enable efficient and flexible data import processes by clearly defining field relationships and supporting dynamic mapping. They help maintain data integrity by allowing you to control how reference fields are handled and by providing scripting capabilities to customize import logic. Understanding the impact of multiple transform maps on import set rows and system performance allows better planning of data import strategies. Overall, transform maps empower administrators to reliably and repeatedly import data into ServiceNow tables with control and precision. A transform map is a set of field maps that determine the relationships between fields in an import set and fields in an existing ServiceNow table, such as Incident \[incident\] or User \[sys_user\]. After creating a transform map, you can reuse it to map data from another import set to the same table. The Transform Maps module enables an administrator to define destinations for imported data on any tables. Transform mapping can be as simple as a drag and drop operation to specify linking between source fields on an import set table and destination fields on any table. Use transform mapping to map source and destination fields dynamically. For a video overview of transform maps, see the [Transform Maps](https://youtu.be/iMjSpK3OaUY?si=SzrhUInpF16Xon5) video on the ServiceNow Dev Program YouTube channel. ## Transform considerations {#c_CreatingNewTransformMaps__section_tx1_dlc_cgb} Auto-mapping : Double-check that fields the system maps automatically are actually required. For example, encrypted passwords probably should not be mapped. Mapping reference fields : If you are mapping reference field data and the sys_id does not exist, the sys_id could potentially appear in the target record as the DisplayValue, and this may be undesirable. : Field mapping a large number of reference fields incurs additional performance overhead because the system checks that the referenced sys_id actually exists before performing choice actions at the field level. Note: You can bypass the performance overhead using transform scripts such as onBefore (on the assumption that there is no requirement to validate the import of reference fields). For example, target.<field_name> = source.<field_name>. ## Using multiple transform maps {#c_CreatingNewTransformMaps__section_zr3_vwc_m1b} Multiple transform maps can be applied to a single data source. One import set row is created per transform map, which can cause a large number of temporary records to be generated. Note: If you use multiple transform maps for the same import set, the transform creates multiple entries in the import set table. ## Run multiple transforms off a single import set {#c_CreatingNewTransformMaps__section_r35_2xc_m1b} Users can select multiple transform maps during data import. The selected transform maps will be executed on the same import set in the order specified. ## Transform map scripts {#c_CreatingNewTransformMaps__section_ywc_1yc_m1b} Transform Map scripts allow you to customize import operations using a robust programming interface to introduce advanced logic. A transform map script executes as events occur while an import set is being transformed onto a ServiceNow table. Transform Map scripting is fully integrated into the ServiceNow scripting environment. There are two types of Transform Map scripts: * Explicit Transform Map scripts, which explicitly define mapping relationships * Transformation Event scripts, which modify the processing of events at different stages of a transformation {#c_CreatingNewTransformMaps__ul_vdc_2gs_sq}