Disclaimer: Importing configuration item data using excel spreadsheets is the worst method to import data. Often the data is old as soon as you start the import. Using ServiceNow Discovery, SCCM Plugin, Procurement, or anything else will produce better results.

However there are certain undiscoverable CI Classes and some companies just don’t have Discovery yet. Using Excel files and Import Sets is sometimes the only choice.

ServiceNow Documentation

Here is the official ServiceNow documentation on import sets.

Import Process

In this post, we are importing using import sets. Not the easy import feature.

Important Note: It is best practice to run the import in a development instance first to see if you have any errors or mistakes. It can be difficult to remove a mistake in data after it is within production.

Import set process is as follows

Data Source. Usually Excel.
Import Set. Data is imported to a Import Set, a temporary location for the data
Transform Map. Data is transformed to the Target Table
Target Table. The end result of the import. CIs, Users, Groups, etc.

Example Import

Step 1: Create Excel File

Here is an example excel file. You can import any number of columns and types.

Step 2: Load Data

1. Login as an administrator
2. Left Navigator Bar > System Import Sets > Load Data

Create Table
Import Set Table: CMDB Data Upload [u_cmdb_data_load]
Source of the import: File
File: Select your spreadsheet
Sheet number: 1
Header row: 1

3. Click Submit
4. After Import Set Table is created, Click Create Transform Map link.

Step 3: Transform Map

Transform Map

1. Fill in fields

Name: CMDB Data Load
Source Table: Configuration Item [cmdb_ci]
Target Table: Incident
Run Business Rules: true
Run Script: true
Enforce Mandatory fields: No
Copy empty fields: true (You can also put false if you don’t want to blank out fields)

2. Click Save

Field Maps

The field maps map the fields from the import set to the target table. In this example,

CoaleAse Methods

If you are just inserting records and not concerned with matching to existing record, no coalease (match) is needed.

However if you can set the coalease to match in the field map on a certain field if you want as well. A common field for matching for configuration items is serial number.

If you need something more complex, here is an article that can help:

Advanced Coalease Methods

Transform Scripts

Often data isn’t perfect. You may need to write a transform script to manipulate certain data. A common thing to do is write a transform script for a reference field to find a sys_id.

Here is an article on how to write transform scripts if needed:

Transform Scripts

Step 4: Transform!

After your Import Set, Transform Map, and Transform Script are ready. Transform the Import Set you created.

It is import to note, if there are certain emails you don’t want sent, you can disable them during the transform process as well.

Important Note: It is best practice to run the import in a development instance first to see if you have any errors or mistakes. It can be difficult to remove a mistake in data after it is within production.

After you import the data, there is a Related link to Transform.