Migrating & Merging Update Sets
In the previous topics, we discussed how update sets are created, and changes are made based on requirements. These configurations need to be transferred from one instance to another, and multiple developers working on individual Update sets have to bring it all together during and after deployment.
In this topic, we will be covering the two important processes of migrating and merging update sets. We will be discussing what they are, why it is important to understand them, and how they are different.
Migrate Update Sets Servicenow
Migrating update sets is an overall process of Update Set migration between instances as part of the deployment pipeline. As we discussed previously, export, retrieve, preview, and commit are major steps in the process of migration. The standard migration process includes:
Development Instance → QA/ Test Instance → Production Instance.
Apart from this, in ServiceNow you can also migrate multiple update sets together under Parent/Child relationship. Rather than exporting, retrieving, previewing, and committing each update set individually, you can make one Update set a parent of one or more sets as its children.
After that,
- In the update set record, set the parent update set to another update set. It makes the current update set a child of that parent.
- Once linked, the child update sets cannot be moved individually.
- When you export the parent record, the child records automatically move as a Batch Update Set ServiceNow.
Important rules while migrating update sets.
- One parent → many children: A single parent Update Set can have any number of children.
- One child → one parent only: A child cannot be linked to more than one parent at a time.
- Same scope required: Parent and child Update Sets must belong to the same application scope. You cannot create a parent/child relationship across two different applications.
- No new Update Set is created: Unlike merging, setting up a parent/child relationship does not create any new record. It simply links existing ones.
Merge Update Sets Servicenow
Merging Update sets in ServiceNow is a way of combining two or more update sets instead of creating a parent-child relationship. Merging update sets combines the changes and creates a new Update set. The steps to do so are:
- Select one update set you want to combine and select Merge with another update set.
- Choose the other update set to merge with.
- Finally, ServiceNow will create a new update set combining changes from both update sets.
Merging and migrating update sets might be a useful approach based on the need. If you want to keep update sets separately identifiable and auditable, then migrate using the parent/child approach. However, if you want a simple, unified update set, merge the update sets.
Difference between Merge vs Parent-Child Update Set
| Differences | Parent-Child | Merge |
|---|---|---|
| Result | No new Update Set is created. The existing ones are linked. | A new Update Set is created containing combined changes. |
| Structure | Hierarchical, with one parent, one or more children. | Flat, as two or more sets become one. |
| Scope requirement | Must be the same application scope. | Merged Update Sets should be compatible or from the same instance. |
| Typical use case | Coordinating deployment of several already-separate, completed pieces of work as one release. | Consolidating overlapping or related work into a single, simplified Update Set. |
| Reversible | Yes, by just removing the parent/child link. | Not directly, as the merge produces a new record. You would need to manage/discard it if the merge was a mistake. |
Conclusion
Update sets in ServiceNow are not a separate standalone feature. They are used in almost everything you build in ServiceNow. From tables to business rules, and UI policies to applications you create, the movements among instances will be done in similar processes.
This module covers everything you need to understand about how to create, manage, deploy, and combine Update sets in practical ServiceNow projects. In the next module, we will be focusing on MID Server, how the records are created, and the integration of MID Server in Servicenow.
Next Chapter
