Import Sets
Jace Benson
Table of content
Import Sets are ServiceNow's built-in mechanism for getting external data into the platform. You load data into a staging table (the import set table), then run a Transform Map to move it into the actual production tables.
How Import Sets Work
- Define a Data Source — Tells ServiceNow where the data comes from (file upload, JDBC, web service, email, etc.)
- Load into a Staging Table — The raw data lands in an import set table, one row per record
- Run a Transform Map — Maps fields from the staging table to the target table, with optional scripts for complex logic
- Review and Commit — Check for errors, fix mapping issues, then commit or discard
Key Tables
| Table | Purpose |
|---|---|
sys_data_source |
Defines the import source (file, JDBC, web service, etc.) |
sys_import_set |
Tracks import set runs — one row per batch load |
sys_import_set_row |
One row per record in a loaded import set |
| Your staging table | Auto-created based on the import set definition — e.g., u_my_import_set |
sys_import_set_queue |
Web service import queue |
Import Methods
- File upload — CSV, Excel, XML (most common starting point)
- JDBC — Direct database connection to external systems
- Web service — REST/SOAP endpoints that post data directly to an import set
- Email — Inbound email can be parsed into an import set
- MID Server — For data sources inside your network
Further Reading
- Importing data using import sets
- Transform Maps
- Robust Transform Maps
- Maik Skoddow - Importing and Transforming Data