How do you copy ci records to another instance?

[Kody]

Hello all,

How do you copy cmdb ci records from an instance to another instance?

I exported them as an xml file on cmdb_ci.list of my instance and then I ran "import xml" on cmdb_ci.list of another instance.

Exported ci records were copied into the target instance and they have all fields not only as cmdb_ci but also more fields as cmdb_ci_win_server for example.

However, I don't think that such export and import refer to IRE rules. 

Is there a way to properly store records in multiple tables according to the class each record possesses, respecting IRE rules?

[Mark Manders]

Why would you want them to run on the import? If the rules are the same on all instances, you should have the same data, because the rules were already applied on the source instance.

XML import doesn't run anything. No business rules, no IRE rules, no flows, nothing. You aren't following any normal process, but just dumping the records on the instance.

Using data sources/transform maps can run those rules, but you will need to set that up and especially with the cmdb_ci table, that could be a hassle with all the different classes and their fields.

[Kody]

Thank you for your reply.

If I use data sources or csv/xls/xlsx files with data sources/transform maps, I believe that the source requires all records have the same record format and the same number of fields.

When I exported records from cmdb_ci as an XML file, I found the records had various formats like cmdb_ci_computer, cmdb_ci_win_server, cmdb_linux_server, etc and these records were saved into correct tables.

From that situation, I had a question whether IRE rules could be applied to the records with xml-import.

From Your reply and Pavani P's reply, I understand that IRE rules cannot work with xml-import.

[pavani_paluri · Accepted solution]

Hi Kody,

Could you please try exporting the CI records via API integration to the target instance instead of using XML export/import?

ServiceNow provides the IRE (Identification and Reconciliation Engine) API out-of-the-box, which ensures proper validation during inserts and updates. This approach avoids potential issues like duplicates or improperly linked CI records that can occur when bypassing IRE.

Additionally, using the IRE API makes it easier to migrate CIs class by class, providing better control, traceability, and adherence to CMDB standards.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P