How to Import Data in Bulk into ServiceNow - CSDM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Hello everyone,
I recently implemented CSDM in my ServiceNow instance.
We have Business Capabilities, Business Processes, Business Applications, Information Objects, Service Instances, Applications, Technology Management Services, Technology Management Offerings, Business Services, Business Service Offerings, and Service Portfolio and Assets.
Is there a way to import all this information in bulk, along with its respective relationships?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @mvelazquezs ,
The short answer is Import Sets + Transform Maps for the CI records, and a second import targeting cmdb_rel_ci for the relationships.
1. Map Each CSDM Entity to Its Target Table
Before you build any transform map, you need to know exactly where each entity lives.
2. Bulk Import Methods
Import Sets + Transform Maps (most common for one-time loads)
The classic approach. For each entity:
-
Prepare a spreadsheet with one row per record
-
Navigate to System Import Sets → Load Data and upload
-
Create a Transform Map pointing at the target table above
-
Use Field Maps (or auto-map) to align your columns
-
Run the transform and validate via Transform History
Starting with the Rome release, Integration Hub ETL provides a simplified UI that guides you through this process end-to-end including a test run on sample data without requiring scripting. https://www.servicenow.com/community/servicenow-ai-platform-articles/administration-importing-amp-tr...That's the preferred modern path if you have IH-ETL licensed.
A community video specifically covers importing CSV files to Business Application and Business Capability tables and building the relationship between them https://www.servicenow.com/community/servicenow-ai-platform-articles/administration-importing-amp-tr...worth watching before you start.
3. Importing Relationships in Bulk
This is the part most people miss. You can import CI relationships using an Import Set where the target table is cmdb_rel_ci.
You can navigate to cmdb_rel_ci.LIST in your instance, right-click the list header, and export to CSV to generate a pre-built template for your import. https://servicenowguru.com/cmdb/walking-servicenowcom-cmdb-relationship-tree/
Duplicate CI names: If you have CIs with the same name in different classes, pass sys_id values in the parent/child columns instead of names since these are reference fields, the transform map will resolve them correctly. https://www.servicenow.com/community/cmdb-forum/two-cis-with-the-same-name-in-the-cmdb-how-can-i-ens...
4. Recommended Sequencing
Don't import everything at once. Follow this order to avoid broken references:
-
Foundation data first (departments, locations, vendors)
-
Business Capabilities → Business Processes
-
Business Applications → Information Objects
-
Service Instances → Applications (Technical)
-
Business Services → Business Service Offerings
-
Technology Management Services → Offerings
-
Service Portfolio
-
Relationships last - once all CIs have sys_ids
If this helped - amazing, you're welcome, go click Helpful and Accept as Solution. If it didn't - well, at least you learned what not to do. Either way, we grow.
Cheers, Abby
ITAM Principal Solution Architect
