1. Inventory the build.
Record core, extensions, custom code, hosting and connected systems. Confirm source ownership, backups and a suitable controlled copy.
Process
Check the site and the publishing workflow before release.
The first review establishes what exists and which content or behavior must survive the change.
2. Choose the responsible path.
Review compatibility and migration needs for the intended target. Name unsupported or uncertain parts before fixing the scope.
3. Rehearse the change.
Apply the planned work in a controlled environment. Preserve repeatable steps and an exception list rather than relying on undocumented manual fixes.
4. Check complete tasks.
Review representative public pages, links, files, forms and search. Have an intended editor create, review and publish content using the agreed roles.
5. Release under agreed conditions.
Account for content edited since the rehearsal, verify redirects and important journeys, and document recovery limits and ongoing maintenance.