--- schema_version: "1" id: d6e608878d77d1184c8c953d6a365dd95f8d192d80ab0fe6fc1cad7d310c3e83 title: Manage Environments collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_manage_environments.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_manage_environments.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 3b5042f7b56d0de7093c30d632639c56ffcc13e89a93757c24ba44f4cfbbed2b description: Replace or remove environments in Lifecycle Center as your project evolves. Environments are the Salesforce orgs, such as sandboxes, scratch orgs, or production orgs, connected to your Lifecycle Center pipeline. Available operations depend on the environment type and pipeline activation status. products: - Salesforce Platform release: "264" --- # Manage Environments Replace or remove environments in Lifecycle Center as your project evolves. Environments are the Salesforce orgs, such as sandboxes, scratch orgs, or production orgs, connected to your Lifecycle Center pipeline. Available operations depend on the environment type and pipeline activation status. ### Required Editions
Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions
Not available in: Government Cloud Plus. Contact your Salesforce account executive for more details.
Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. Lifecycle Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions.
Before you begin: - To replace an environment, create and configure the replacement environment first. - Make sure that no active work items are associated with an environment before you remove it. ## Replace an Environment Replace a development or pipeline environment after you activate the pipeline. Replace an environment when its sandbox is refreshed or its scratch org expires. - Development environments: Lifecycle Center moves unpromoted work items to the new environment and syncs changes from the pipeline branch. - Pipeline environments: Lifecycle Center moves connected work items to the new environment and deploys changes from the pipeline branch. For steps, see [Replace a Development Environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_replace_dev_environment.htm&release=264.0.0&type=5 "After a Developer or Developer Pro sandbox refreshes or a scratch org expires, the connection to Lifecycle Center becomes unusable. Replace the development environment in Lifecycle Center to restore the connection. Lifecycle Center deploys the pipeline stage branch to the new sandbox so that you can continue working with the correct metadata and configuration data.") or [Replace a Pipeline Environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_replace_pipeline_environment.htm&release=264.0.0&type=5 "Activating a refreshed sandbox permanently deletes the original environment and its data, which breaks the connection to Lifecycle Center. Replace the pipeline environment in Lifecycle Center before your team members promote changes to the associated pipeline stage. Lifecycle Center deploys changes from the pipeline branch to the new environment."). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/images/icon_note.png) Note In DevOps Center (Managed Package), this operation is called swap environment. ## Remove an Environment Remove an unused development environment. You can add it again later. You can't remove an environment that has an activity history. Instead, replace the environment. See [Remove an Environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_remove_environment.htm&release=264.0.0&type=5 "Remove an unused development environment from your Lifecycle Center pipeline. You can add a removed environment again later. You can't remove an environment that has an activity history, use replace instead."). - **[Replace and Connect a New Environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_replace_connect_environment.htm&release=264.0.0&type=5)** Maintain pipeline integrity by replacing an expired, deleted, or refreshed development or pipeline environment in Lifecycle Center. When you connect a new environment, Lifecycle Center restores the complete branch state, including metadata and configuration data, to keep it in sync with the pipeline. - **[Remove an Environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_remove_environment.htm&release=264.0.0&type=5)** Remove an unused development environment from your Lifecycle Center pipeline. You can add a removed environment again later. You can't remove an environment that has an activity history, use replace instead. #### See Also - [Lifecycle Center Environments](https://help.salesforce.com/s/articleView?id=platform.devops_center_environments_overview.htm&release=264.0.0&type=5 "Environments are the Salesforce orgs, such as sandboxes, scratch orgs, or production orgs, connected to your Lifecycle Center pipeline. Lifecycle Center uses different environment types for development, pipeline stages, and release.") - [Replace and Connect a New Environment](https://help.salesforce.com/s/articleView?id=platform.devops_center_replace_connect_environment.htm&release=264.0.0&type=5 "Maintain pipeline integrity by replacing an expired, deleted, or refreshed development or pipeline environment in Lifecycle Center. When you connect a new environment, Lifecycle Center restores the complete branch state, including metadata and configuration data, to keep it in sync with the pipeline.") - [Keep Your Development Environment in Sync](https://help.salesforce.com/s/articleView?id=platform.devops_center_sync_dev_environment.htm&release=264.0.0&type=5 "Use back sync to update your development environment with the latest changes from the first pipeline stage. Keeping your environment current helps maintain compatibility with your team’s changes and reduce merge conflicts.")