---
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


---

# Retire a sandbox

# Retire a sandbox {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Retire sandboxes that are outdated or no longer needed to make room for new Developer Sandboxes in your instance.

## Before you begin

Save your work, for example commit it to source control or export update sets. For more information, see [Update sets transfer between sandboxes and base instance](https://www.servicenow.com/docs/gLMTiSeB8or1cI7s3xDMhA "When a sandbox is ready, update set sources are automatically created on both the sandbox and the base instance, enabling transfers in either direction without manual configuration.").

Role required: admin or sandbox_manager

## About this task

You should manually retire sandboxes when your work is complete to maintain a healthy development lifecycle.  
Warning:  
Because sandboxes are retired automatically after an upgrade or clone, ensure any work that you want to keep is preserved before upgrading or cloning.

* For upgrades, you can restore work from the remote update sets that Developer Sandboxes automatically created from prior sandboxes.
* For clones, you must manually save and restore all work in sandboxes.
* Any custom table configuration changes or fixes must be reapplied after an upgrade. Contact Now Support to open a case.

## Procedure

1. Navigate to AllSandbox ManagementSandbox Management Home.
2. Select the more options icon ![]()in the Developer Sandboxes dashboard, and then select Retire sandbox.  
   Figure 1. Retire a sandbox
3. Confirm the retirement by selecting Retire.

## Result

After it's retired, the sandbox is no longer available for use. However, you can allocate new sandboxes as needed. For more information, see [Allocate a sandbox](https://www.servicenow.com/docs/RKFnqDgjM0dkHTH4~hvWRg "Allocate sandboxes to your development teams so they can start using them for development.").

The update set sources associated with the sandbox are automatically removed during retirement. The source on the base instance pointing to the sandbox is deleted, and the source on the sandbox is dropped along with the rest of the sandbox data. No manual cleanup is needed.

*[\>]: and then