When multiple update sets need to move together as a single deployment, merging creates one consolidated set with all changes combined. You'll end up with a single export that contains everything and reduces your deployment complexity.
Why manual update set coordination fails
Before merging existed, teams had to export multiple update sets individually and manually track which ones belonged together for each deployment. This meant administrators had to remember the correct order, import each set separately, and troubleshoot conflicts when the same record was modified across sets. Platform teams managing releases quickly learned that multi-set deployments were error-prone and time-consuming, especially when sets contained overlapping changes that needed to be applied in sequence.
How update set merging works
Merging takes completed update sets and creates a new consolidated set containing all the changes. You select which sets to merge and ServiceNow combines their contents into a single export. The critical piece is merge order — if the same record appears in multiple sets, the version from the last merged set wins. This happens at the individual field level, so one set can contribute some fields while another overwrites different fields on the same record. The merged set becomes your single deployment unit.
Building merge discipline for production deployments
Once basic merging works, add strict naming conventions that identify what got merged and when. Most teams evolve to merging sets by feature or sprint boundaries rather than by developer. Advanced implementations include merge documentation that captures which sets were combined and what conflicts were resolved. The production-quality approach treats merged sets as immutable artifacts — you don't modify them after creation, you merge additional sets if changes are needed.
Before you start
- •admin role or update_set_admin role
- •At least two completed update sets ready for deployment
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Navigate to retrieved update sets
Go to System Update Sets > Retrieved Update Sets. This shows you all update sets in your instance, including ones you created locally. You'll merge from this list, not from Local Update Sets.
If your sets are still in progress, complete them first — you can't merge incomplete sets.
Select sets to merge
Check the boxes next to each update set you want to merge. Select them in the order you want them processed — this determines conflict resolution. The set you select last takes precedence for any overlapping changes.
Write down your selection order before starting — you can't see the merge sequence once you submit.
Access merge option
Right-click on one of your selected update sets and choose 'Merge Update Sets' from the context menu. This opens the merge configuration dialog where you'll name the merged set and confirm your selections.
Configure the merged set
Enter a descriptive name in the 'Name' field that identifies what got merged. Include the date and components, like 'HRSD_Sprint_15_Merge_2024-01'. Add a description that lists the original set names and any conflict resolutions you expect.
Use consistent naming patterns across merges — your future self will thank you when debugging deployments.
Review merge conflicts
Check the preview section that shows conflicting records. Each conflict displays which sets modified the same record and which version will win. Note any critical conflicts where you need the losing version instead — you'll handle those manually after merge.
Screenshot complex conflicts before proceeding — the merge preview disappears once you submit.
Execute the merge
Click 'Merge' to create the new update set. ServiceNow processes all changes and creates your consolidated set. The merged set appears in your Retrieved Update Sets list with a status of 'Complete' and contains all changes from the source sets.
Export the merged set
Find your new merged set in Retrieved Update Sets, right-click it, and select 'Export to XML'. This creates your single deployment file. Test the export in a development instance before moving to production — merged sets can have subtle issues that individual sets don't show.
Best practices
Name merged sets with date stamps and component identifiers so you can track what got combined months later.
Never modify a merged update set after creation — if you need changes, merge additional sets rather than editing the merged one.
Test merged sets in a clean development instance before production deployment — conflicts that merge cleanly can still break functionality.
Document which original sets went into each merge and what conflicts were resolved — this saves hours during production troubleshooting.
Merge sets by feature or sprint boundaries rather than by individual developer — this creates cleaner deployment units and reduces cross-team dependencies.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue