Key takeaway
A successful move protects the whole business workflow, including email, forms and checkout—not just the homepage.
01
Inventory what already works
List the domain, DNS records, mailboxes, databases, scheduled jobs, certificates, redirects, analytics, and third-party integrations. Record traffic peaks and any checkout or form paths that must be tested.
02
Build and test the destination
Copy the site into an isolated environment, match the runtime versions, restore the database, and test forms, logins, search, email delivery, and key pages. Keep the current site live while this happens.
03
Prepare the switch
Lower DNS time-to-live in advance, freeze content changes for a short window, take a final backup, and agree on who makes the go/no-go decision. A rollback plan should be written before it is needed.
04
Watch the first 48 hours
Monitor uptime, errors, certificates, mail, forms, performance, and search indexing. Keep the old environment available briefly, then remove it securely after the new service is stable.
Your next-step checklist
- Record domain ownership and existing DNS records
- Test the destination before changing DNS
- Take a final backup and agree a rollback plan
- Check enquiries, email and checkout after the switch
Put this guide to work.
Tell us about your goals and current setup. We can help you discuss the requirements and plan a suitable next step.
Discuss your project