Migrating operational data PROD A→PROD B without clone. what is the best method?

[Puneet Hegde1]

Context:
We’re consolidating two production instances (servicenow Instance A → ServiceNow Instance B). A clone is not possible due to tenant isolation and timing constraints. We only need to move operational data (not configuration) and keep the destination’s existing configuration intact.

Goal:
Migrate the following from A (prod) to B (prod) while preserving relationships and history where feasible:

• incident, change_request, sn_customerservice_case, sc_request, sc_req_item, 

• Related/child data: sys_journal_field (work notes/comments), attachments (sys_attachment + sys_attachment_doc),  streams, and key related lists.

Constraints / Requirements

• No outage window long enough for a full export/import freeze; may need an incremental cutover.

• Preserve sys_ids where possible so references stay intact.

• Prefer to retain timestamps (sys_created_on, sys_updated_on) and authors if supported.

• Volumes are mid-to-high (hundreds of thousands of tasks + journal entries).

• Destination does not contain live data.

• This is a one-time transformation as we are migrating from instance A to instance B

Question:
Given these constraints, what is the best and most reliable method to migrate this operational data between two production instances while maintaining data integrity, relationships, and history?

Additionally, are there any ServiceNow-recommended best practices or documented runbooks for performing this type of production-to-production operational data migration?


Thank you,
Puneet

[Dr Atul G- LNG]

Hi @Puneet Hegde1 

Explore: IDR - Instance data replication

https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/administer/instance-data-re...

[Puneet Hegde1]

Dear Atul,
As IDR is a paid plugin it will not meet our requirement as we need to transfer data only once as we are migrating from instance A to instance B. Is there any other best practice for this type of requirement?

Thank you,
Puneet

[Dr Atul G- LNG]

Hi @Puneet Hegde1 

I'm not 100% certain, but it's possible to build an integration between A and B. From A, you could use the update API to send all data to B. In this case, the timestamps will differ, but I believe all data will still be transferred.

Integration between SN to SN is relatively simple and straightforward. However, it's a time-consuming task, as you'll need to configure the API for each record individually. Alternatively, you could try using XML import/export, but that would also require importing and exporting records one by one.

[Bhuvan]

@Puneet Hegde1 

I would highly recommend to use Instance Data Replication IDR as this would be the perfect scenario for 'Build Vs Buy' option. To build integration from scratch using Scripted REST API or Flow Designer or any other methods for such a scenario would create technical debt with detailed testing pre-requisites, development efforts and overall cost of purchasing IDR solution could be a better option than building and maintaining a custom solution.

Refer below article for more information on IDR

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1191897

Talk to your Accounts team to get in touch with ServiceNow representative and discuss the options.

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan