Module wise migration

[Sneha KH]

Hello All!!
I have a requirement saying that in one instance all the configurations related to one module (eg: ITSM) is done. In another instance there is no module related data like plugins and all. So, I need to migrate between these instances. How can I achieve this? Even if I use update sets, incidents cannot be captured. I need to manually import/ export. Is there any way?

[Dr Atul G- LNG · Accepted solution]

Hi @Sneha KH 

Since you want to perform a migration, I assume you are referring to migrating the configuration and not the data (except for foundation data).

In this case, the first step is to check that both the source instance and the target instance are on the same version and release. This ensures that moving the configuration will not cause any errors.

Secondly, updates only capture the configuration, not the data. So you are safe. If you want to move additional information like groups or user extensions, you can use import/export.

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

https://www.servicenow.com/community/developer-blog/what-gets-captured-in-update-sets/ba-p/2280698

An update set in ServiceNow is a group of customizations that can be moved from one instance to another. This includes changes to tables, fields, forms, and scripts, among other things.

Answering your question:

a) Data Record - Not captured in an update set. Update sets do not capture data, they capture configuration changes.

b) Configuration Item - Not captured in an update set. Configuration items are data, and as mentioned, data is not captured in update sets.

c) New User/Group - Not captured in an update set. Users and groups are also considered data.

d) Views - Captured in an update set. Views are considered a configuration change, not data, so they are captured in update sets.

[Dr Atul G- LNG · Accepted solution]

Hi @Sneha KH 

Since you want to perform a migration, I assume you are referring to migrating the configuration and not the data (except for foundation data).

In this case, the first step is to check that both the source instance and the target instance are on the same version and release. This ensures that moving the configuration will not cause any errors.

Secondly, updates only capture the configuration, not the data. So you are safe. If you want to move additional information like groups or user extensions, you can use import/export.

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

https://www.servicenow.com/community/developer-blog/what-gets-captured-in-update-sets/ba-p/2280698

An update set in ServiceNow is a group of customizations that can be moved from one instance to another. This includes changes to tables, fields, forms, and scripts, among other things.

Answering your question:

a) Data Record - Not captured in an update set. Update sets do not capture data, they capture configuration changes.

b) Configuration Item - Not captured in an update set. Configuration items are data, and as mentioned, data is not captured in update sets.

c) New User/Group - Not captured in an update set. Users and groups are also considered data.

d) Views - Captured in an update set. Views are considered a configuration change, not data, so they are captured in update sets.

[Tanushree Maiti · Accepted solution]

Hi @Sneha KH 

Before moving any configurations, the target instance must have the foundational applications installed to accept the data.

• Activate Plugins: On the target instance, activate the same ITSM plugins (e.g., Incident, Change, Problem Management) that are active on the source instance.
• Ensure Version Match: Ensure both instances are on the same ServiceNow version to prevent configuration mapping errors

Start migration of Configurations

1.  Using Update Set

2. Using XML export/import

If you need Foundation data to migrate 

you can use Xml export/import process as well.