Inventory more than the visible pages
A website can depend on files, databases, scheduled jobs, email, DNS records, certificates and external services. Record the current platform and runtime versions, where the database is hosted, which forms send email and whether the site accepts live orders. Include subdomains and integration callbacks. Moving the homepage successfully does not show that checkout, notifications or background tasks work.
Create a backup you can restore
Keep an independent copy of the site files and an appropriate database export before making changes. Verify that the archive opens and that the expected data is present. For a transactional site, agree how changes made during migration will be captured; an early database copy may miss later orders. Keep secrets out of shared tickets and agree an authorised secure access method with the person performing the work.
Test the destination before changing traffic
Prepare a preview that lets you check the actual application on the destination. Test key pages, login, forms, links, media, permissions and scheduled jobs. Use a sandbox for payment testing where available, and ensure a test system does not send unintended messages to customers. Confirm that SSL, redirects and canonical URLs will work with the production hostname.
Plan DNS and the final data change
DNS links names to the resources clients need to reach. Review which records should change and which must remain, especially email-related records. Caches and record lifetimes can make a switch appear at different times for different visitors. Agree a cutover window, a final content or database synchronisation and the checks required before announcing completion. Do not promise a universal instant switch or zero downtime without a design that supports it.
Keep a rollback and acceptance checklist
Record the previous configuration and who can authorise a rollback. Keep the previous environment available for an agreed period when practical, while ensuring it cannot unintentionally process duplicate orders. After the switch, check production forms, authentication, email behaviour and application logs. A rollback of a site with new transactions needs a data plan; simply pointing DNS back can create inconsistent records.
DNS terminology: MDN Web Docs ↗
Your decision checklist
- Independent files and database backup
- Tested destination and integration checks
- Authorised cutover and final synchronisation
- Documented rollback and acceptance checks
