How to migrate data from CMDB-C to Servicenow

[shabbir5]

Hi All,

How we can migrate data from CMDB-C to Servicenow??

CMBD-C is BMC Remedy Data base which is having Different Sources(almost 20+ data sources).

Our goal is to get all the data from different sources to servicenow target tables?

is there any OOB plugin available to achieve this ? or we need to migrate this via custom integration

Please help me with your inputs

@Ankur Bawiskar 

Regards,

Shabbir

[AJ-TechTrek · Accepted solution]

Hi @shabbir5 ,

As per my understanding, below approach might be helpful for you

1. OOB Options from ServiceNow
* There is no official OOB plugin from ServiceNow that directly connects to BMC CMDB-C or pulls from multiple external sources into CMDB.
* ServiceNow has:
* IntegrationHub ETL framework (to map & transform data into CMDB).
* Import Sets + Transform Maps (classic ETL approach inside SN).
* IntegrationHub spokes for certain sources (but not BMC Remedy/CMDB-C).
* So no one-click migration, but the OOB ETL framework can be used with custom connectors.

2. Typical Migration Approach
You’ll need a custom ETL pipeline. Two main ways:

Option A — Staging via CSV / Database Export (One-time migration)
1. Extract data from BMC CMDB-C into flat files (CSV, Excel) per source table.
2. Load into ServiceNow Import Set tables.
3. Transform into target CMDB tables using:
* Transform Maps
* Coalesce rules for matching
4. Validate data (check duplicate rules, CI identifiers, relationships).
5. Repeat for each of the 20+ sources.

Option B — API-based / Database Connector (Ongoing sync)
1. Use BMC Atrium CMDB REST/SOAP APIs or direct database queries (if allowed).
2. Push the data into ServiceNow Import Set API.
3. Apply Transform Maps to populate CMDB.
4. Schedule recurring jobs if it’s not just a one-time migration.

3. Using ServiceNow ETL (IntegrationHub ETL)
If you have ITOM or IntegrationHub ETL:
* You can create Data Sources for each BMC source (database, API, file).
* Use ETL Transformations to map BMC classes → ServiceNow CMDB classes (like BMC_ComputerSystem → cmdb_ci_computer).
* Validate with Data Certification module to ensure clean migration.

4. Key Migration Considerations
* Data Model Differences: BMC CMDB uses Common Data Model (CDM); ServiceNow uses CSDM-aligned CMDB model.
* Identifiers: Ensure unique keys (serial number, hostname, FQDN, etc.) are set so you don’t duplicate.
* Relationships: Migration should handle BMC_Relationship → cmdb_rel_ci mapping.
* Data Cleansing: Remove duplicates and stale records before importing.
* Testing: Always run in a sub-prod SN instance first.

5. Recommended High-Level Steps
1. Discovery: Identify all BMC classes in scope & mapping to ServiceNow classes.
2. Extraction: Export from BMC (via DB, API, or CSV).
3. Mapping: Create mapping spreadsheet (BMC field → SN field).
4. Staging: Load into Import Sets.
5. Transformation: Apply Transform Maps (with coalesce).
6. Validation: Check CI count, relationships, and attributes.
7. Cutover: Perform migration in production during planned downtime.
8. Post-Migration: Reconcile and fix missing/mismatched records.

6. Final Answer as per my understanding.
* OOB Plugin: Not available for BMC CMDB-C → ServiceNow.
* Best Path: Custom ETL/migration using Import Sets + Transform Maps or IntegrationHub ETL.
* If this is a one-time migration → CSV/Excel → Import Set is easiest.
* If this is ongoing sync → build an API-based integration

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025