Swap environments
Now you have the know-how to create a new environment, and you’re confident about the purpose of your new environment. Once it’s time to turn the new environment into the new live version, it’s time for the big swap. Let’s take a good look at the necessary steps to ensure a smooth swapping process between your environments.
Before you swap
Implement a content freeze on the production environment to prevent content creators from making changes in live content, preserving content integrity during the transition. Once testing is completed in the non-production environment and considered ready, you can swap the environments by marking the non-production environment as the new production environment. Then, lift the content freeze to resume regular content production.Swap environments
Once you’ve made your final changes and with the content freeze in place, you can do the swap. You swap environments by marking a non-production environment as production.
Swapping environments in practice
Imagine a project with two environments, Live and UAT (User Acceptance Testing). Live is used for production purposes, whereas UAT is your recently cloned environment with a modified content model.When you mark the UAT environment as production, the contents and settings of the Live and UAT environments stay the same. Make sure to rename the environments after the swap to avoid confusion.
The Live and UAT environments before the swap. The production environment is in blue.Notice that the Live environment has an extra user Ron who wasn't invited to the UAT environment. After the swap, Ron won't be carried over to the new production environment.