---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Explore

# Exploring System Update Sets {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Exploring System Update Sets

System update sets in ServiceNow are groups of configuration changes packaged as XML files that can be transferred between instances.
They enable developers to create and test customizations in non-production environments before promoting these changes to testing and production instances.
An update set contains unique record details, a list of tracked configuration changes, and a state indicating whether it's ready for transfer and application on another instance.
Show full answer Show less  

## Key Features

* **Create and Manage Update Sets:** Developers and admins can create update sets, select the current update set to capture changes, and mark them as complete when ready.
* **Transfer and Apply Changes:** Update sets can be retrieved from remote instances, compared to identify differences, and committed to apply changes.
* **Back Out and Batch Processing:** Admins can back out changes from applied update sets and batch multiple update sets for bulk preview and commit.
* **Tracking Customizations:** Update sets track modifications to application tables, fields, and records, ensuring consistent migration of configuration changes.
* **System Properties and External Files:** Configuration of update set-related system properties is supported, along with exporting update sets as XML files for manual transfer.

## Typical Workflows

Two common workflows for moving update sets are:

* **Three-step process:** Development instance → Test instance → Production instance. Each step involves creating, completing, retrieving, and committing update sets, with fixes developed as new update sets if needed.
* **Two-step process:** When using a combined staging instance for development and testing, changes are developed and tested there before retrieving and committing on production.

It is important to maintain a consistent migration path and avoid migrating the same update set from multiple sources.

## Use Cases and Best Practices

* Use update sets primarily for migrating customizations and specific application versions between instances.
* Do not combine update sets with Application Repository development for scoped apps to avoid skipped changes and commit errors.
* For large data transfers, use import sets or web services instead of update sets.
* Update sets track changes to both applications and platform features, but migrating update sets from newer to older releases or between different app versions should be avoided due to compatibility and data loss risks.
* After installing an app from the Application Repository, continue to use the repository for updates rather than update sets.

## Benefits for ServiceNow Customers

* Efficiently manage and migrate configuration changes across instances with controlled workflows.
* Reduce risk of errors by testing updates in intermediate environments before production deployment.
* Enable teamwork by allowing developers and admins to create, compare, merge, and back out changes systematically.
* Maintain consistent application versions and customization states across the ServiceNow environment.

## Next Steps

To maximize the use of system update sets, customers should explore detailed guidance on configuring, using, and managing update sets, including working with batched update sets and executing update set transfers effectively within their ServiceNow instances.  
An update set is a group of configuration changes that can be moved from one instance to another. Update sets enable developers to create functionality on a non-production instance, and promote the changes to another instance
for testing or deployment.

## System update sets overview {#exploring-system-update-sets__cf-exploring-parent-overview}

An update set is an XML file that contains:  
* A set of record details that uniquely identify the update set.
* A list of configuration changes.
* A state that determines whether another instance can retrieve and apply configuration changes.
{#exploring-system-update-sets__ul_jdc_gbk_wr}

## Users {#exploring-system-update-sets__cf-exploring-parent-users}

{#exploring-system-update-sets__table_lqr_lpq_jfc__entry__2}

| User | Description |
|-|-|
| Admin | Creates, compares, and merges update sets while also managing how update sets store, retrieve, preview, and apply configuration changes between instances. |
| Developer | Creates update sets for specific versions of an application and specifies which application tables to track. |
[ ]

{#exploring-system-update-sets__table_lqr_lpq_jfc}

## Workflows {#exploring-system-update-sets__cf-exploring-parent-workflow}

A common process for developing customizations with update sets involves moving changes from development
to test and production instances.
Figure 1. Three-step import process  
1. Create an update set on the development instance.
2. Make customizations and changes on the development instance.
3. Mark the update set as complete.
4. Log in to the test instance and retrieve the completed update set from the development instance.
5. Commit the update set on the test instance, and test customizations thoroughly.
6. If the update set has problems in the test instance, repeat steps 1--5 to develop the fix on the development instance with another update set.
7. Identify a common path for update sets to move from instance to instance and maintain that model. Never migrate the same update set from multiple sources. Move update sets from dev to test and then from test to production.
8. Commit the update set on production. If the update set required a fix, commit both update sets in the order they were made.
{#exploring-system-update-sets__cf-exploring-parent-workflow-ol}

If your development environment consists of only two instances, you can combine your development and testing instances into a single staging instance.
Figure 2. Two-step import process  
1. Create an update set on the staging instance.
2. Make customizations and changes on the staging instance.
3. Mark the update set as complete.
4. Test customizations thoroughly on the staging instance.
5. If the update set has problems, repeat steps 1--4 to develop the fix on the staging instance with another update set.
6. Log in to the production instance and retrieve the completed update set from the staging instance. If the update set required a fix, retrieve both update sets.
7. Commit the update set on production. If the update set required a fix, commit both update sets in the order they were made.
{#exploring-system-update-sets__ol_y21_f5w_wgc}

## Benefits {#exploring-system-update-sets__cf-exploring-parent-benefits}

{#exploring-system-update-sets__table_oqr_lpq_jfc__entry__3}

| Benefit | Feature | Users |
|-|-|-|
| Create an update set to store local changes. | [Create and select an update set as the current set](https://www.servicenow.com/docs/nO2ZJd9Sqn2NuO887EEgwQ "Create an update set to store customization changes and select it as the current set.") | Developer |
| Select the current update set to store local changes. | [Select the current update set in Unified Navigation](https://www.servicenow.com/docs/a0eV71YSd3QsF8yq4chQ6g "You can change the current update set at any time using the update set picker in Unified Navigation.") | Admin |
| Commit an update set to prepare it for distribution. | [Commit an update set](https://www.servicenow.com/docs/bAVsEysYvl5scUnB4D_2yA "After resolving any issues from previewing, commit the update set to apply all changes and generate a local copy with records of each update.") | Admin |
| Compare update sets to determine what differences they contain. | [Compare local update sets](https://www.servicenow.com/docs/IS6cL49qXok5Zz3y8iUzZg "Administrators can preview local and remote (retrieved) update sets and compare the sets with one another to resolve conflicting changes.") | Admin |
| Create an external file from an update set. | [Save an update set as a local XML file](https://www.servicenow.com/docs/UShM_jVi9c86_aWDsfUKdQ#t_SaveAnUpdateSetAsAnXMLFile "Administrators can export an update set as an XML file to save a specific version of an application or set of changes.") | Admin |
| Retrieve update sets from remote instances. | [Retrieve an update set](https://www.servicenow.com/docs/XgTgeUKvPUb_U5gkxU0HHg "Retrieve completed update sets from another instance.") | Admin |
| Back out changes applied from an update set. | [Back out an update set](https://www.servicenow.com/docs/~w3OJRTHLq~1r41Q5Pa~YA "You can back out changes to existing records for any committed update set.") | Admin |
| Set system properties related to update sets. | [Update sets properties](https://www.servicenow.com/docs/19TEU9extYCQBE5hMa3M8w "A reference topic that contains information on the system properties used with update sets.") | Admin |
| Track customizations to application tables, fields, and records. | [Customizations tracked by update sets](https://www.servicenow.com/docs/DrNqh0_mDYvRvbHsWYpjIA "Update sets track customizations to application tables, fields, and records.") | Admin |
| Batch update sets together so you can preview and commit them in bulk. | [Working with batched update sets](https://www.servicenow.com/docs/0nrJHymFFfX3EV2mFflLHQ "Batched update sets enable you to group update sets together so you can preview and commit them in bulk.") | Admin |
[ ]

{#exploring-system-update-sets__table_oqr_lpq_jfc}

## Use cases {#exploring-system-update-sets__section_bxm_wcx_wgc}

Choose update sets or the application repository depending on the result that you want to achieve. Don't use both Update Sets and the Application Repository for scoped app development. Combining the usage of both results in skipped
changes and commit errors. After installing an app from the Application Repository, continue its usage for development and publishing. Update sets can only transfer limited application files. For larger transfers, export and import data
using import sets or web services.

Update sets
:
    * Storing changes to a base system or installed application.
    * Storing and applying a particular version of an application.
    * Producing a file for export.
    {#exploring-system-update-sets__ul_gkx_k3c_xgc}

Application repository
:
    * Installing and updating applications on all company instances.
    * Managing application update sets.
    * Restricting access to applications from the same company.
    * Deploying completed applications to end users.
{#exploring-system-update-sets__ul_fr3_1jc_xgc}  
Warning:  
Update sets track changes to applications and system platform features. Update sets from older releases can be loaded onto newer instances without problems. Moving update sets from newer to older releases, or between different ServiceNow Store app versions, should be avoided due to potential compatibility issues and risks of data loss.

## What to explore next {#exploring-system-update-sets__cf-exploring-parent-links}

To learn more about configuring, using, and managing system update sets see:

* [Configuring System Update Sets](https://www.servicenow.com/docs/lnjjrZ0ez8hi~J75uJ8G0Q "Configure your instance with tracked app installations or merge update sets into a single update set.")
* [Working with update sets](https://www.servicenow.com/docs/l0r1WxT0ZhthZDHGxCwMTQ "Manage your customizations and resolve potential collisions before you move them to another instance.")
* [Working with batched update sets](https://www.servicenow.com/docs/0nrJHymFFfX3EV2mFflLHQ "Batched update sets enable you to group update sets together so you can preview and commit them in bulk.")
* [Update set transfers](https://www.servicenow.com/docs/_J259HfzWUwLtg6c6kgxVw "When an update set is completed, you can transfer it between instances to move customizations from development, through testing, and into production.")
{#exploring-system-update-sets__ul_pqr_lpq_jfc}