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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Merge update sets

# Merge update sets {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Merge multiple update sets into a single update set.

## Before you begin

The batch update sets feature accomplishes the same outcome with a more predictable and robust solution. See [Update set batching](https://www.servicenow.com/docs/Oz42DFsXBooB7J8pd304gA "Batched update sets enable you to group update sets together so you can preview and commit them in bulk.").

Role required: admin

## Procedure

1. Navigate to AllSystem Update SetsMerge Update Sets or Merge Completed Sets.
2. Filter the list to show only the update set that you want to merge.  
   You can only merge update sets that belong to the same application.
3. Enter a Name for the new update set.
4. **Optional:** Enter a Description for the update set.
5. Select Merge.
6. In the confirmation dialog box, select OK.  
   The most recent change for each object is moved from the original sets to the new set. Only changes that aren't merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped.  
   Note:  
   The system determines which record is the most recent by comparing the Updated field for the records, NOT the sys_updated_on value in the payload.
7. Open the old update set records in the Merged Update Sets related list and verify that the correct changes were moved.
8. Delete or empty the original update sets to avoid committing an older change by mistake.

*[\>]: and then