HRSD configuration-only migration from one instance to another – recommended technical approaches?

[Gopi22]

Hello All,

We currently have HRSD implemented and managed by a service provider in a separate ServiceNow instance (Instance B). We are now planning to implement HRSD in our primary enterprise instance (Instance A) and want to migrate only the HRSD configurations from Instance B to Instance A — not any HR transactional data (cases, tasks, profiles, attachments, historical data).

After installing HRSD and required plugins in Instance A, we’re evaluating technical approaches for this migration. Have anyone successfully done a configuration-only HRSD migration between instances, and if so, what approach worked best? Any gotchas or recommendations from real-world experience would be greatly appreciated.

Thanks,

Gopikrishnan

[chaithu1489]

One key concern is the number of application scopes affected as part of HRSD implementation, along with configuration data not captured in update sets.

[Gopi22]

Thank you @chaithu1489 
We will know what we missed, only after moving them to instance A (primary instance) , I guess. 
There is no other way to know what we missed right?

[Mark Manders]

It was implemented on Instance B, so assuming it was all done with update sets, you can just get those from B and commit them on A. Evaluate what you have and what you are still missing, but that will exclude any cases and historical data.

Since the users/groups will probably have different sysIDs, just set them as you need them, don't export/import those. 

[Gopi22]

Thank you @Mark Manders