Update sets are how you move customizations between ServiceNow instances without breaking existing configurations. This guide shows you how to import an update set XML file and preview it to catch conflicts before they become production problems.
Why preview before committing
Without previewing, committing an update set blindly overwrites existing configurations in your target instance. This breaks customizations that other developers built, creates inconsistent data, and causes mysterious application failures that take hours to debug. Platform teams — admins, developers, and anyone maintaining ServiceNow — need to see what will change before it changes. The preview process surfaces conflicts, missing dependencies, and 'no base record' situations where the update set references something that doesn't exist in your target instance.
How update set importing works
Importing happens in two phases: retrieve and commit. Retrieve uploads the XML file and creates a remote update set record — nothing changes in your instance yet. Preview analyzes what would happen if you committed, showing you exactly which records will be created, updated, or potentially cause problems. ServiceNow compares each update set record against what exists in your target instance and flags conflicts where the same record was modified differently. You resolve conflicts by choosing which version wins, then commit to make the changes permanent.
Handling complex migration scenarios
Production-quality update set management means establishing conflict resolution patterns for your team. Common enhancements include creating naming conventions for customizations to avoid conflicts, setting up dedicated integration instances for testing problematic update sets, and maintaining documentation about which customizations can't be cleanly moved via update sets. Some organizations build custom scripts to pre-validate update sets or automatically resolve predictable conflict patterns.
Before you start
- •admin role or update_set_admin delegated role
- •Update set XML file accessible from your browser
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 Remote Update Sets
Go to System Update Sets > Retrieved Update Sets. This shows update sets that have been imported but not yet committed. The list will be empty if this is your first import to this instance.
Bookmark this page — you'll return here to monitor preview progress and resolve conflicts.
Import the update set XML
Click the 'Import Update Set from XML' link at the bottom of the page. Click 'Choose File' and select your update set XML file, then click 'Upload'. ServiceNow creates a new remote update set record with the state 'Loaded' — this means the XML was parsed successfully but no preview has run yet.
Start the preview process
Click on the newly created remote update set record to open it. The record shows basic information like the source instance and number of changes. Click the 'Preview Update Set' button to start the analysis. ServiceNow changes the state to 'Previewing' and begins checking each update set record for conflicts.
Monitor preview completion
Refresh the remote update set record every 30-60 seconds to check progress. Large update sets can take several minutes to preview. When complete, the state changes to 'Previewed' and the Preview Problems section populates with any conflicts or warnings that need attention.
Don't navigate away during preview — if ServiceNow times out, you might need to restart the preview process.
Review preview problems
Scroll down to the Preview Problems related list. Each row represents a potential issue: conflicts show where the same record was modified differently, 'no base record' warnings mean the update set references something missing from your target instance. Click on individual problems to see detailed comparisons between the incoming change and what exists locally.
Resolve conflicts and warnings
For each conflict, click 'Accept remote' to use the incoming version or 'Skip' to keep your local version. For 'no base record' warnings, investigate whether the missing record should exist — you may need to manually create dependencies or exclude those update set records. Resolve all conflicts before committing.
Commit the update set
Once all preview problems are resolved, click 'Commit Update Set' on the remote update set record. ServiceNow applies all changes to your target instance and changes the state to 'Committed'. The update set records are now permanently part of your instance configuration and cannot be easily reversed.
Best practices
Always preview in a sub-production instance first — conflicts that seem minor can break critical workflows in unexpected ways.
Document your conflict resolution decisions in the work notes — six months later, you'll need to remember why you chose 'skip' over 'accept remote'.
Never commit an update set with unresolved 'no base record' warnings — these create dangling references that cause runtime errors.
Take a manual checkpoint or backup before committing large update sets — while rare, corrupted commits can require instance rollbacks.
If the same update set will be deployed to multiple instances, resolve conflicts consistently — different resolution choices create configuration drift.
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