Inventory before copying
List domains, subdomains, databases, cron jobs, redirects, SSL, email and external services before touching DNS.
A reliable migration is more than copying files. Plan the website, database, DNS, SSL, email, scheduled jobs, third-party integrations, testing and rollback before changing traffic.

List domains, subdomains, databases, cron jobs, redirects, SSL, email and external services before touching DNS.
Keep a known-good copy of website files and databases. A backup is useful only when its contents and restore method are understood.
Check pages, forms, logins, checkout, media, PHP compatibility and database connections before directing visitors to the new server.
Lowering TTL in advance can help, but DNS propagation is not instant or identical for every resolver.
Confirm whether email is hosted with the website, Microsoft 365, Zoho or another provider before changing MX, SPF, DKIM or DMARC records.
Do not destroy the source immediately. Keep agreed rollback access until the new environment is verified and stable.
Find the cause before changing everything.
Read the guide →Recovery, access, updates and shared responsibility.
Read the guide →Updates, access, monitoring and recovery planning.
Read the guide →Product pages, categories, technical SEO and measurement.
Read the guide →Build costs, running costs and extras.
Read the guide →Choose the right amount of work.
Read the guide →Find the cause before choosing a fix.
Read the guide →Use the Hosting Plan Finder → · Open the customer help centre →
Often downtime can be reduced significantly, but a universal zero-downtime guarantee is not realistic. DNS caching, application behaviour and data changes during cutover can affect the result.
Not automatically. First identify where mailboxes are hosted and which DNS records they depend on. Website and email migrations can be separated when that reduces risk.
Typical migrations need source hosting or application access, destination access, DNS control and database access. The exact requirement depends on the platform and scope.
After the destination has been tested, DNS has settled, critical functions are verified and the agreed rollback period has passed.