Web Host Lens

Web Host Lens field guide

The zero-surprise website migration guide

Move the site, database, email and DNS with a tested rollback plan rather than hoping a plugin handles everything.

Updated 17 July 2026Primary sources linkedAffiliate-neutral
The zero-surprise website migration guide

Editorial verdict

The short answer

A migration is complete only when the website, forms, scheduled tasks, mailboxes, certificates, redirects, analytics and DNS work, and when the old service remains recoverable through the validation period.

Before you buy

Questions the provider must answer

  1. 01Who performs the migration and what is excluded?
  2. 02Are email and DNS records included?
  3. 03How large is the expected outage?
  4. 04Can the old environment remain online?
  5. 05What is the rollback trigger?

Decision process

A practical, repeatable method

1

Inventory the current system

List files, databases, versions, cron jobs, mailboxes, DNS records, certificates and third-party integrations.

2

Create independent backups

Export outside both providers and verify the archive can be opened.

3

Lower DNS time to live

Reduce it before migration so a later switch propagates faster, then restore it after stability.

4

Clone and test privately

Use a temporary address or local hosts entry. Test checkout, forms, login, redirects and scheduled tasks.

5

Freeze changing data

Plan how orders, comments or account changes are handled during the final database sync.

6

Switch, monitor and retain rollback

Change DNS, monitor errors and transactions, and keep the old service until the agreed validation window ends.

Avoidable errors

Common mistakes

  • × Cancelling the old host before validation
  • × Migrating files but not email
  • × Changing DNS without recording old values
  • × Testing only the homepage
  • × Forgetting cache, cron and payment webhooks

Frequently asked questions

What buyers ask next

Can migration have zero downtime?

Often nearly zero, but dynamic data requires careful final synchronisation and DNS planning.

Are free migrations comprehensive?

Not always. Confirm email, multiple sites, custom applications and size limits.

When should the old plan be cancelled?

After traffic, transactions, email and monitoring are stable and rollback is no longer needed.

Should the domain be transferred simultaneously?

Usually separate hosting migration from registrar transfer to reduce variables.

Evidence

Primary and supporting sources

Prices and terms can change. Recheck the provider page and checkout before purchasing.

How to use this guide

Separate facts, estimates and judgement.

Provider documentation establishes product terms. Calculations explain their financial effect. Regional suitability requires checkout verification and testing from the intended audience. A recommendation is editorial judgement only after those layers agree.

Official termCalculated modelRegional verificationEditorial conclusion