Best Practices for Migrating ServiceNow Customizations from Instance A to Instance B

[Puneet Hegde1]

Hi everyone,

I’m looking for guidance on how to migrate the customizations and configurations from one ServiceNow instance (Instance A for Company A) to another (Instance B for Company B). I don’t plan to modify any existing processes, so I’d like to capture all the custom work in bulk—ideally through a single Update Set—or move the entire application scope as is.

Has anyone done this before or have any tips on the best approach? Any guidance you can provide would be greatly appreciated!


Thank you in advance

[Community Alums · Accepted solution]

Hi @Puneet Hegde1 ,

You can use Batch update sets which enables you to group update sets together so you can preview and commit them in bulk.

 You need to perform your batching prior to moving to another instance, or do the batching in the 2nd instance for the additional item.

Process : https://www.servicenow.com/docs/bundle/xanadu-application-development/page/build/system-update-sets/...

[Rajesh Mushke]

Hi @Puneet Hegde1,

You can move them through the batch update set or entire application, it is up to your choice.

Based on my previous experience, you may encounter the the issues with the duplicate sys_id values. 

Eg: if your app table fields/any type of customization sys_id is already been used in the B Company instance with a record/data/any type of record. In this scenarios, you might need to recreate that in the B Company instance.

Let me know if you have any questions further.