Recommended workflow for deployments
This feature is in beta, and is available to participating organizations.
To make sure that your deployments don’t have any unintended impact on your production environment, we recommend the following workflow to test changes in your sandbox and push them to production.
We also recommend that you complete all the steps of the workflow without significant delays between the steps. Delaying deployment after the scan can cause inconsistencies or failures if your production environment changes during the gap.
Step 1: Create two sandboxes
Create two sandboxes (or reuse two existing sandboxes) for the app in production you want to deploy changes to. Designate one of the sandboxes as your development environment and the other one as your staging environment.
Step 2: Copy data
Use the Copy all spaces or projects option and copy data from production to both the sandboxes.
If you have copied data before December 3, 2025, repeat the process of copying data to make sure that the list of configuration changes generated during deployment is accurate.
We recommend that you don’t use the Copy specific spaces or projects option as it may lead to duplicate data on your sandbox and impact the changes you want to deploy.
Step 3: Understand supported entities and operations
Review the list of supported entities and operations to learn which deployment types are not supported. What data is deployed from sandboxes
Step 4: Make configuration changes
Try out the configuration changes you want to apply to production on the development sandbox.
We recommend that you try out a limited number of configuration changes and deploy changes incrementally. This way, with each deployment, you can test and push configuration changes that are logically related and address a specific business requirement.
Only new entities added to the sandbox and entities modified on the sandbox can be included in the deployment. Your deployment won’t include any entities deleted on the sandbox.
Step 5: Deploy changes from the first sandbox
Deploy changes from the development sandbox to the staging sandbox. How to deploy configuration changes from a sandbox
Before you select an entity in your deployment, make sure to use the diff overview to review the changes you want to include.
Deploy changes only from lower environments to higher environments. That is from
developmenttouator fromuattostaging.
We recommend that you don’t deploy changes back and forth between two environments as it may lead to inconsistent configuration changes.
Step 6: Review changes in the second sandbox
Test and review the changes in the staging sandbox to make sure that changes are applied correctly and there are no unintended changes.
Step 7: Deploy changes from the second sandbox
After making sure that everything works as expected, deploy changes from the staging sandbox to your production environment.
Step 8: Review changes in production
Test and review the changes in your production to make sure that changes are applied correctly and there are no unintended changes.
Was this helpful?