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

[shabbir5]

Hi All

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

what is the best way to finish this ?

Regards

Shabbir Shaik

[Ankur Bawiskar · Accepted solution]

@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?

[Dr Atul G- LNG]

Hi @shabbir5 

Generally, data is never moved from a lower to a higher instance, especially transactional data. So, I’m still not clear on the business need to move this data, especially when the instance flow is from development to production or vice versa.

[Mark Manders]

Just doing something because it is asked is the worst possible reason to do something. What is the business goal. Why are you asked to do this? Did you read my reasons why you shouldn't do this? 

There can be reasons why you should, but it's going to give you a lot of trash in your other instance. Especially when it could even be that customization on one or the other is going to break even more than just the (work)flows behind it.

[Ankur Bawiskar · Accepted solution]

@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?

[Vishal36 · Accepted solution]

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!:)