Seeking Best Practices for Migrating an Existing ServiceNow Instance into a Brand-New MSP instance

[MiaoZhan]

I’m working with a customer who plans to migrate their current ServiceNow production instance into a brand-new MSP (Managed Service Provider)-hosted instance.

Specific Questions:

• What is the recommended high-level approach? (e.g., Cloning? UpdateSets move?)
• If Cloning is Yes, may i know the Cloning best practices specific for instance migration?
• How do you identify and isolate "must-migrate" vs. "leave behind" customizations in a legacy instance?
• How have others handled integration reconfiguration (e.g., SSO, email, REST APIs) when endpoint
• URLs/credentials change in the new environment?
• Are there common pitfalls to avoid when migrating into an MSP-managed topology ?

We’re aiming for a clean, maintainable foundation—not just replicating technical debt. Any templates, checklists, or lessons learned from similar MSP onboarding/migration projects would be greatly appreciated!

[KvitoslavaM]

Hi!

Strict governance is crucial as an MSP instance is a shared system used by multiple customers. One wrong configuration can cause data leaks between companies. By following a compatibility checklist, you protect the MSP’s "Gold Image," ensuring your custom logic doesn't override the provider’s core billing or security tools. Use Scoped Applications instead of the Global scope to keep your custom code separate and make future ServiceNow upgrades easier. Replace hardcoded URLs with Connection Aliases so integrations work correctly with the MSP’s firewall and proxy settings.