How to import/migrate 1,00,000 REQ , RITMS , SCTASK from one instance to another instance?

shabbir5 · ‎06-17-2025

Hi All

what is the best way to finish this ?

Regards

Shabbir Shaik

Ankur Bawiskar · ‎06-17-2025

@shabbir5

what's the business requirement to migrate those from instance A to instance B?

If you are storing the REQ, RITM, SC Task as part of replicating then why not handle it as soon as it's created?

Why are you doing bulk migration?

Regards,
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

View solution in original post

Vishal36 · a month ago

Hi @shabbir5,

Migrating over 100,000 REQs, RITMs, and SCTASKs between ServiceNow instances isn’t just about volume, —it’s about accurate data migration. Your approach will depend on the following factors:

What’s your goal—just data transfer or full fidelity?: Are you simply moving ticket data, or do you also need attachments, comments, task hierarchy, approvals, SLA histories, and state transitions?
Are both instances configured the same way?: Even minor differences in workflows, custom fields, or catalog definitions can lead to data loss, errors, or misaligned records during migration.
Do you need to preserve relationships across records?: RITMs and SCTASKs are often tied to REQs in parent-child structures. If not handled properly, these links break and context is lost.
Do you need auditability and rollback capability?: With high volumes, it’s risky to proceed without visibility into what succeeded, failed, or partially imported.

You may consider OpsHub Migration Manager, a ServiceNow Partner that helps you migrate at scale with zero downtime and non-disruption—while keeping relationships, context, and traceability intact across records. No scripting or export import hassles.

Hope it helps!:)

View solution in original post

Dr Atul G- LNG · ‎06-17-2025

Hi @shabbir5

Why do you want to bring transactional data from one instance to another? 100,000 records are too many—I prefer cloning as the best option.

Clone from prod to dev / test not vice versa.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

shabbir5 · ‎06-17-2025

Hi @Atul,

Here there are 2 instances , not a kind of same DEV , TEST , PROD.

2 separate instances , one is X and another is Y

we need to perform migrade , as part the data migration , we need to move REQ , RITM , SCTASK data from X to Y ?

so to make it success , is there any best way? please suggest

Regards,

Shabbir Shaik

Mark Manders · ‎06-17-2025

Why? What is your business/use case to do this?

Reason for asking is not the records, because you can just export them in batches and import again, but the logic behind it won't be imported. If your request is somewhere in an approval step, nothing will ever happen, because it's not in the (work)flow that handles it. You are only importing the records.

And the number also sounds weird. Why would you need so many records? If it's already closed records, why do you need them? If they are open, they are useless (see above).

Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

shabbir5 · ‎06-17-2025

Hi Mark,

Thank you for the response.

The business need is to import the data from one instance to another instance , our customer want us to perform the migration of data from one instance to another instance

Please suggest some best ideas to perform this

Regards,

Shabbir Shaik