Data Imports

Jace Benson

Table of content
  1. How Data Imports Work
  2. Import Set Tables
  3. Transform Maps
  4. Async Processing
  5. Data Sources
  6. Additional Resources

Docs

Data imports are how you get structured data into ServiceNow from external sources. They run asynchronously because they can process thousands of rows at a time.

How Data Imports Work

The import process has two phases:

  1. Load — data is loaded into a staging table (the import set table, sys_import_set_row)
  2. Transform — a transform map copies the staged data from the import set table to the target table, applying field mappings and business logic along the way

This two-phase approach means you can validate data before it hits your production tables. The load runs first, then transformation runs separately.

Import Set Tables

When you import data (CSV, Excel, XML, JDBC), it lands in an import set table — a staging table with generic columns (u_number, u_name, u_value1, etc.). Each source file creates its own import set.

// Programmatic import
var imp = new GlideImportSetTransformer();
imp.setImportSetRow('sys_id_of_row');
imp.transform();

Transform Maps

Transform maps define the mapping between import set columns and target table fields. They can include:

Async Processing

Imports are async because they can take a while. The ImportSetWorker scheduled job processes import sets in the background. You can monitor progress on the Import Set Rows (sys_import_set_row) table.

The async behavior means:

Data Sources

ServiceNow supports importing from:

Additional Resources