Best Practice for moving from default/global instance to Domain separated instance.

[BH10]

Hi guys,

Could you shed lights or your experience on approach for moving from default/global instance to domain separated instance.

-what things to consider during activity, and

-pros & cons if we go with clone from  default/global instance to new instance. ( which is domain separated instance)

-best practice for moving from default/global instance to domain separated instance.

-how to ensure and put right data, configuration, process are placed in right place., do & dont's etc.

and was tryting to access below KB article but they are not accessible with NowSupport permission id and require special privilege's. 

appreciate if anyone help and export kb article...

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

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

Thanks in advance. 

[Tony Chatfield1]

Hi, I suspect that exporting and sharing these KB articles would be a breach of a users legal agreement with ServiceNow, and if you require access to these records you should either log a case in SNC Support and\or engage your ServiceNow account manager.

Without any details\context to your requirement it is difficult to provide a focused response but
to clarify the deployment process I would deploy domain separation to a freshly cloned dev instance, test and validate. Then once happy, deploy domain separation to your prod instance.

[BH10]

Thanks for response and apologies for didn't mentioned details, will try explain here in point#2.

1.Mentioned kb link gives as 'reference to check' in other kb article, thought it should be related to support and should visible to customer/partner, if restricted to public. will check with account manager on this.

2.We are planning for moving from  a Single tenant ServiceNow instance to a Multi-tenant instance.(domain separation) and existing single tenant instance is live and we have to migrate data, process, configuration, etc. things to new domain separated instance. 

[Tony Chatfield1]

Hi, you do not normally 'move' to a domain separated instance, but you deploy domain separation to your instance and I would think a 'migration' process between 2 instances would be complicated and may result in a longer period where operational records are not aligned with the new structure. In addition you would have an ongoing migration window issue with 'new' records being created in one or other instance during the migration period.

The process is normally to deploy domain separation to your instance (activate the plugin), then create your domain structure and finally migrate\move your records into the domain structure.

But deploying domain separation to a production environment is complicated and not without risk

https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/company-and-domain-separation/concept/domain-sep-plugin.html

If you have no experience with domain separation, then I would consider engaging a ServiceNow partner (with proven domain separation experience) or ServcieNow PS to review\advise, so that you can understand the full deployment process, impact, potential downtime etc.

This doesn't mean that it is not possible to migrate to a domain separated instance without external support, but that if you proceed without experienced input you will need to spend a lot of additional time testing your migration process and validating the results in sub-production before considering a Prod migration.