Importing data into ServiceNow involves usingImport Sets, which act astemporary staging tablesbefore transferring data to the target table. The correct sequence of steps is as follows:
Load the Data
Upload data from an external source (CSV, Excel, XML, JDBC, or API).
The data is stored in anImport Set table(temporary staging table).
Create Transform Map
ATransform Mapdefineshowdata from the Import Set should be mapped to thetarget table(e.g.,incident,cmdb_ci).
Example:Mapping " Full Name " in Import Set → " User Name " in sys_user table.
Transform Data
Executes theTransform Map, moving data from the Import Set into the target table.
Anydata conversion rules or business logic(such as field mapping, script processing) are applied.
Clean Up Import Table
After a successful import, thetemporary Import Set tablecan be deleted to free up space.
A. Select source file; Run automap; Transform data; Clean up target table
Automapis optional and does not apply in every scenario.
Cleaning up the target tableis incorrect—the cleanup applies to theImport Set table, not the target table.
B. Set up LDAP; Test map; Create update set; Run import; Apply update set
LDAP is foruser authentication, not for importing data.
Update Sets are used formoving configurations, notdata imports.
C. Identify source; Import transform map; Run transformer; Verify import
" Run transformer " is incorrect—the correct step is " Transform Data " .
Importing does not require averification step; instead, data is reviewed usingTransform History.
[References:ServiceNow Documentation:Import Set Process, ServiceNow Developer Guide:Creating Transform Maps, , , ]
