Start with the release boundary
Update Set
Move a defined collection of tracked configuration changes from a source instance to a target instance.
Application Repository
Publish a tested application version and let entitled company instances install or upgrade it.
Source control
Use Git from a non-production development instance for team collaboration, branches and change history.
CSA exam clue
Configuration migration points to an Update Set. Versioned application distribution points to App Repo. Developer collaboration and Git history points to source control.
Compare the three mechanisms
Update Sets: capture, complete, retrieve, preview and commit
- Create a clearly named local Update Set and make it current before development begins.
- Make the planned configuration changes and verify the customer updates that were captured.
- Do not bundle unrelated work, secrets or customer records into the release.
- Mark the set complete, then retrieve or import it into the target instance.
- Preview it and review every incoming record, missing object, collision and scope warning.
- Resolve all preview problems before commit, then test the resulting behavior and review the commit log.
Never treat preview as a formality. A collision means the target has a newer change to the same object. Compare local and remote versions, then deliberately accept the remote update or skip it.
Application Repository: publish a tested version
After developing and testing a custom application, publish it to the organization's Application Repository. Entitled company instances can then install that version. This creates a clearer versioned release path than moving a sequence of loosely connected changes.
- Use it for an application lifecycle with explicit versions and release notes.
- Confirm target-instance entitlement and application dependencies.
- Test installation or upgrade in a non-production instance before production.
- Do not alternate between App Repo and Update Sets for the same scoped app. ServiceNow documents skipped changes and commit errors as possible results.
Source control: development history, not production deployment
ServiceNow Studio can link an application to a dedicated Git repository so developers can commit, pull and manage changes. Use a restricted token or SSH credential and confirm network access from the non-production instance.
ServiceNow does not support linking source control to an application or customization on a production instance. Install production applications through an approved deployment method such as Application Repository or an Update Set.
Worked release scenario
A team builds a scoped request application
Developers collaborate in Git from development instances. After integration testing, the release owner publishes version 1.2.0 to Application Repository. Test installs that exact version, validates dependencies and regression scenarios, and production installs the approved version. The team does not also transport the application through Update Sets.
An administrator changes a global incident form and Business Rule
Create a named Update Set, capture and inspect both configuration changes, complete it, retrieve it in test, preview and resolve collisions, commit, then run form, API and rule-regression tests before the production change window.
Troubleshoot a failed or incomplete migration
- Confirm the method: Update Set, App Repo version or source-control branch.
- Check scope and dependencies: ensure the target has the required application and referenced artifacts.
- Inspect evidence: customer updates, preview records, commit log, application version or Git history.
- Resolve preview problems: compare collisions, supply missing objects and address uncommitted dependencies.
- Check excluded data: determine whether required records were configuration or business data and move them through an approved data process.
- Retest security and integrations: ACLs, credentials, properties and endpoints often differ by environment.
- Validate rollback: do not assume every change is safely reversible; use a tested backout and recovery plan.
ServiceNow CSA practice checks
A retrieved Update Set reports a collision. What should happen next?
Best answer: compare the incoming update with the target version and choose the intended action. Resolve the preview problem before commit.
Developers need branching and shared change history. Which mechanism?
Best answer: source control on a non-production development instance. It supports collaboration but does not replace the production installation method.
A tested scoped app must be installed on entitled company instances as version 2.0. Which mechanism?
Best answer: Application Repository. Publish the tested version, then install it on entitled targets.
Frequently asked questions
Do ServiceNow Update Sets move business data?
Update Sets primarily capture tracked configuration and customization records. They are not an instance backup or a general-purpose method for moving transactional records, credentials or customer data. Confirm that every required artifact is captured before migration.
What is the difference between Application Repository and source control?
Application Repository publishes versioned applications so entitled company instances can install them. Source control links development work to a Git repository for collaboration and history; ServiceNow does not support linking it to an application on a production instance.
Why must an Update Set be previewed before commit?
Preview compares incoming changes with the target instance and identifies missing objects, collisions, scope problems and other risks. Resolve every preview problem before committing.
Can Update Sets and Application Repository be mixed for one scoped app?
ServiceNow warns against mixing these methods for the same scoped application because it can cause skipped changes and commit errors. Select one release method and use it consistently.
Official ServiceNow references
Use the current ServiceNow documentation for previewing remote Update Sets, committing an Update Set, Application Repository, application-management constraints and linking an app to source control. Features vary by release and entitlement.