--- 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 --- # Key concepts # Import sets key concepts {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Import sets key concepts Import sets in ServiceNow provide a staging area for data imported from external sources before it is transformed and loaded into target tables like Incident or User tables. Import sets help manage data import processes efficiently while preventing system issues caused by importing excessively large data chunks. Show full answer Show less ## Key Concepts * **Import Set Table:** Temporarily stores imported records; columns are auto-generated based on input data and should not be manually modified to avoid cleanup issues. * **Data Source:** Defines the origin of the import data, which can be files, databases, or directories like LDAP. * **Transform Map:** Maps fields between the import set table and the target ServiceNow table, controlling how data is transformed and inserted. * **Coalesce:** Enables updating existing records by matching key fields during transformation, preventing duplicate records. * **Robust Import Set Transformer:** An alternative to transform maps that separates transformation and processing for greater flexibility and supports loading data to multiple target tables. * **Foreign Record Insert:** Occurs when an import updates a related table (e.g., updating a caller on an incident modifies the sysuser table). ## Supported Import Formats and Data Sources * **File Formats:** CSV (RFC4180 compliant), Excel (XLS/XLSX), XML, JSON (RFC-4627 compliant with specific path requirements), and custom scripts. * **External Data Sources:** JDBC, LDAP, OIDC, ServiceNow REST (Integration Hub), and custom scripted imports---all require valid transform maps. ## Operational Considerations * **Import Set Scheduled Cleanup:** A scheduled job runs daily at midnight to delete import sets older than 7 days and their associated records, preventing table bloat. This job must be active and import set tables should not exceed 5 million records total to avoid performance issues. * **Manual Cleanup:** Customers can manually delete specific import set tables and related transform maps or clear data while retaining table structures, supporting efficient data management. * **System User Execution:** Import sets run as the System user and cannot add data to encrypted fields. ## Practical Benefits for ServiceNow Customers Understanding and correctly using import sets, transform maps, and data sources enables customers to efficiently bring external data into their ServiceNow instances with minimal risk of duplicates or performance degradation. Scheduled and manual cleanup options help maintain system health, while flexible transformation methods like robust import set transformers provide enhanced data processing capabilities. Adhering to supported formats and import best practices ensures smooth, reliable data imports aligned with ServiceNow standards. Learn about import sets before importing data to your instance. The import sets table acts as a staging area for records imported from a data source. Note: Do not import data in extremely large chunks. Creating an extremely large import set can cause delays and system outages. A transform map determines the relationships between fields displaying in an import set table and fields in an existing ServiceNow table, such as the Incidents or Users table. Importing sets skip records when the data in the instance matches the data being imported. Note: Import sets run as user System and therefore cannot add data to encrypted fields. ## Import sets terminology {#c_ImportSetsKeyConcepts__table_rv4_gxf_f5__entry__2} | Term | Definition | |-|-| | Import Set table | A table that acts as a staging location for records imported from a data source before transforming those records. Fields on these tables are generated automatically based on imported data and should not be modified manually. Note: Columns in an import set table are generated automatically and shouldn't be added manually. Manually adding columns can negatively impact the table's scheduled cleanup and may lead to an incomplete cleanup and orphaned records. If you need to add columns to an import set table, first add the column to the input data, then select Test Load 20 Records or Load All Records to auto generate the columns in the import set table. Columns in an import set table might not have the same type as the input data. For example, a currency column may be represented as a string column in an import set table until it's assigned to a target table column that is of type currency. | | Data source | A record that defines where to get the data to import. A data source may point to a file, a JDBC-compatible database, or an LDAP organizational unit. | | Transformation | The conversion of data from an import set table to another table according to the rules defined in a transform map. | | Transform map | A set of field maps that define the relationships between fields in an import set and fields on a table, such as Incident. During transformation, data is copied from the Import Set table to the destination table based on the transform map. A single import set field may be mapped to multiple fields on other tables. | | Robust import set transformer | Extract, transform, and load data to one or more target tables. Separate the transform and processing functions, providing a more flexible alternative to transform maps. | | Foreign record insert | A foreign record insert occurs when an import makes a change to a table that is not the target table for that import. This change happens when updating a reference field on a table. For example, when updating a value for the caller on an incident, the import is actually updating the sys_user table. | | Coalesce | Lets you update existing target table records when transforming import data. You can specify whether a Target field should be used to coalesce on when import set records are transformed. If the field map Coalesce option is selected, when the import set row is transformed, the instance checks for an existing record in the target table that has the same value in the Target field as the import set row Source field. If an existing record with a matching value in the target table is found, that record is updated. If no matching record is found, then a new record is created in the target table. | [Table 1. Key terms] {#c_ImportSetsKeyConcepts__table_rv4_gxf_f5} ## Supported import formats {#c_ImportSetsKeyConcepts__section_uyv_ylc_m1b} You can import data from several different file formats or external data sources. {#c_ImportSetsKeyConcepts__table_mwq_nl1_kr__entry__2} | Format | Limitations | |-|-| | CSV | CSV files must comply with the proposed CSV standard in [RFC4180](http://tools.ietf.org/pdf/rfc4180.pdf). In particular, this means that double quotes may not appear inside fields. The first row of data in an imported CSV file becomes the header row and defines the columns for that import set. | | Excel | Excel files must have the XLS or XLSX extension. | | XML | XML files must have a consistent XPath for each data row. | | JSON | * For JSON arrays, the path for each row must specify the array root element twice, such as `/incidents/incidents`. * JSON files should follow [RFC-4627](https://www.ietf.org/rfc/rfc4627.txt). For example, a single comma should separate a value from the following name. Names within an object should be unique. * Predicates such as `@element`, `[index]`, or `text()`, as well as Axis such as children, siblings, or ancestors are not supported. {#c_ImportSetsKeyConcepts__ul_mgp_3kr_5x} | | Custom (Parse by Script) | You can write custom JavaScript to parse input lines into the list of maps. | [Table 2. File formats] {#c_ImportSetsKeyConcepts__table_mwq_nl1_kr} The ServiceNow® platform can import data from the following external data sources. {#c_ImportSetsKeyConcepts__table_nck_jm1_kr__entry__2} | Data Source | Limitations | |-|-| | JDBC | JDBC imports require a valid transform map. Some network configurations may require a ServiceNow® MID Server. | | LDAP | LDAP imports require a valid transform map. | | OIDC | OIDC imports require a valid transform map. | | ServiceNow® REST (Integration Hub) | REST imports require a valid transform map. | | Custom (Load by Script) | Custom imports require a valid transform map. | [Table 3. External data sources] {#c_ImportSetsKeyConcepts__table_nck_jm1_kr} For more details about the different data sources, see [Data sources](https://www.servicenow.com/docs/fKrXfgAr7aVRp5qVWQXyGA "Data sources are used to create an import set so that data can be processed, if necessary, prior to being mapped onto a production table."). ## Transform maps versus robust import set transformers {#c_ImportSetsKeyConcepts__section_gkz_blr_cjb} Both transform maps and robust import set transformers convert data. Transform maps convert data from the staging table to the destination file. Robust import set transformers convert data from a source table to a message listener. If a data source has both a transform map and a robust import set transformer, the system uses the robust import set transformer instead of the transform map. ## Import set scheduled cleanup {#c_ImportSetsKeyConcepts__section_rzy_t3d_m1b} The Import Set Deleter scheduled job cleans up old import set data every day at midnight. By default, the job deletes all import sets that are older than 7 days, as well as the associated import set table records. If this scheduled job is not active on your instance, activate it to mitigate the growing import set tables you may have, especially when using recurring imports. Note: If scheduled cleanup is not currently active on your system, you must ensure that your import set tables are not too large (\> 5 million records total across all tables) before enabling this cleanup. If the tables are too large, manually delete the records first before proceeding. Contact Customer Service and Support to coordinate the deletion of this data. Figure 1. Scheduled Script Execution For procedures, see [Delete import sets](https://www.servicenow.com/docs/jswNLDzkdtxVMbr3QIfITw "Delete import sets to clean up your database on a scheduled basis, one time only, or on demand."). ## Import set table deleter {#c_ImportSetsKeyConcepts__section_yhm_4lt_1jb} You can manually delete any or all of the following import set tables: * Computer * User * Notification * Location {#c_ImportSetsKeyConcepts__ul_ihz_xlt_1jb} You can also delete the related transform maps, or you can delete data only and preserve the table structure.Figure 2. Tables available for deletion For procedures, see [Delete import set tables](https://www.servicenow.com/docs/nICyJDZV1jSh47mbntJCdg "Delete import set tables, related transform maps, or data only (preserving the table structure) to clean up your database.").