---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Update set use

# Update set use {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

These procedures help you manage your customizations and resolve potential collisions
before you move them to another instance.

Before using update sets, review [Get started with update sets](https://servicenow-prod.fluidtopics.net/Y0wxSDRv_Q1BEoAvJ40o3A "Because update sets make changes to an instance, review this information to avoid errors and performance issues. Learn how to plan the update process and avoid common mistakes.") to learn when to use
and when not to use update sets, and how to plan the update process and avoid common mistakes.
Then, create an update set and use it to make changes on a development instance. You can report
on updates, merge update sets, and compare update sets to ensure the desired changes are ready to
move.

When the update set is completed, you can transfer the update set to another instance according
to your test process. See [Update set transfers](https://servicenow-prod.fluidtopics.net/RC7nB0b3sUseMoarj6bkrg "When an update set is completed, you can transfer it between instances to move customizations from development, through testing, and into production.") for details.