Overview: Once your sites are launched on the Dataweavers platform, you will typically decommission your legacy Sitecore environments. This task is not included in the Dataweavers onboarding process and is generally managed by your digital partner or the current tenancy operator. However, for upgrade projects, Dataweavers will include the decommissioning process in the scope of works.
After your new site goes live, there should be no dependencies on your existing tenancy, allowing it to be decommissioned without any impact.
Day After Go-Live:
Scale down the old Production (Prod) and Non-Production (Non-Prod) environments, including turning off all App Services.
Remove all origin groups in Azure Front Door (AFD) pointing to the old Prod and Non-Prod environments.
Two Weeks After Go-Live (or as needed):
Proceed with resource deletion, backups, and storage account management.
Complete any remaining deletions.
This process should be planned, managed, and executed by your existing team or partner after the onboarding go-live.
Recommendation: We recommend keeping your old environment available for 1-2 weeks post-launch as an emergency fallback. This period allows you to ensure the new environment is stable and provides an emergency rollback strategy if needed. User acceptance testing (UAT) on the new Production environment before launch minimizes the likelihood of requiring a rollback
.
Related to