Migrate data between Instance A from Company A to Instance B of Company BSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Customer Support assistance for these activities is limited to functional guidance only. These requests are considered implementation‑related and fall outside the standard Technical Support (break‑fix) scope. For implementation assistance, customers are advised to work with their Account Representatives to engage ServiceNow Professional Services. OOB Option We have an existing module by which this can be initiated very quickly, as well as the documentation. Instance Data Replication Restore Option Restore Instance A from Company A to Instance B of Company B Customers may request that a backup from one company be restored to an instance belonging to another company. This process requires two separate support cases: Source Company Case: The Primary Customer Contact must explicitly approve the use of their backup, including all data and configurations.Target Company Case: The Primary Customer Contact must explicitly approve the restoration of the backup over the target instance, including all data and configurations. The restore is performed internally by ServiceNow using backend automation. As this is a full automated backup restore, all data, configurations, cross‑instance references, and security‑related information (including sensitive data) are included. Selective exclusion of data is not supported. The restore activity will proceed only after approvals are received from both companies on their respective cases. Please ensure that all cross-data references and security considerations, especially those involving sensitive information, are carefully evaluated. Plugins and Store applications if it is restored from Company A to Company B If the source company has purchased plugins or Store products, these will be restored to the target company in an ACTIVE state as part of the restore process. Customers must work with their Account Representatives to address any licensing or entitlement considerations. Once installed, plugins cannot be uninstalled and will remain active. Plugins are configuration artifacts and are automatically copied as part of the full backup restore. Uninstall a ServiceNow pluginPlugins Visibility / Activation / Licensing Manual Migration Migration of configuration Configurations can be transferred from one instance to another in Update-sets. Migration of Custom Scoped app Custom scoped applications that are in an Installed state will be transferred to the target instance as Installed. If the custom application was published and installed using APPREPO, publishing and installation of updates are supported only when the instances belong to different companies. Each custom application scope is uniquely identified using the format x_<appcreatorcode>_*, where the app creator code is specific to the owning company. If the target instance is not linked to the organization that owns the corresponding app creator code, the Publish option will not be available, and published application updates cannot be installed. In such cases, the app creator code on the target instance will differ from that of the source instance. Should there be a need to install these application updates, the process must be completed using update-sets. The customer will need to obtain the update-set XML directly from the other company in order to proceed. You can refer to more information in the section "How to move Custom Scoped Applications between instances" Migration of data Data can be exported in supported formats such as XML, Excel, or CSV and transferred to the target instance using standard Import Set functionality. Manual data migration is complex and requires careful planning. In addition to primary records, dependent data such as reference data, attachments (sys_attachment), audit records (sys_audit), and other related system data must also be migrated. These elements have interdependencies and must be validated and tested in SUBPROD environments before applying any changes to PROD. Failure to migrate dependent data may result in orphaned records, which require additional analysis to identify and export the missing dependencies. Export limitations (including record count and file size) may apply. To mitigate these constraints, data should be exported and imported in smaller, manageable batches. More details on Exporting data Before migrating data, customers must ensure that the table schema is aligned between the source and target instances. Store applications, custom applications, and plugins are configuration components and may introduce additional columns or fields to database tables. If the target instance does not contain the required fields, the data will not be imported successfully. Customers must therefore verify that the same plugins, Store apps, and custom applications are installed on both instances. A migration plan should be in place to identify and remediate any missing configurations or table fields between the source and target instances prior to data migration.