How to Keep Email When Moving Website Host

“how to keep email when moving site host” is best treated as a controlled release rather than a single copy-and-cancel job. Website files are only one part of the move; databases, DNS, email, redirects and ownership details also need a planned handover.

For a UK site owner, continuity matters because the site must stay available, load quickly and remain easy to follow to manage. Inventory clear pages, dependable forms, secure administration and recoverable content, then test the chosen site platform against compatible software, enough resources, reliable backups and a clear support boundary on the new host before changing public DNS. Keep an independent export and retain the previous account until site and mail checks pass.

Treat the move as a controlled release

A hosting move is safest when the old service remains live until the replacement has been tested. Begin with a full copy of site files, database, DNS records, SSL details and mailboxes. Record any scheduled jobs, redirects, third-party integrations and domain contacts that could be forgotten. Build or import the site on the new host, then inspect it through a temporary address or local hosts-file entry. For the chosen site platform, test compatible software, enough resources, reliable backups and a clear support boundary; also submit forms, log in, search the site and complete a low-risk transaction where relevant. Reduce DNS time-to-live before the change when possible, schedule the switch outside the busiest period and freeze content briefly if two databases could diverge. Keep the old account and independent backup until DNS has settled, email is flowing and analytics show normal behaviour. Only then cancel the previous package. A measured overlap costs less than trying to reconstruct a missing order, enquiry or mailbox.

How this requirement changes the shortlist

Email makes the decision broader than web space. Check mailbox storage, aliases, sending limits, spam controls and migration help, plus whether the account works with the intended desktop or mobile app. During any nameserver change, preserve MX, SPF, DKIM and DMARC records so a site improvement does not interrupt business messages.

Migration language shifts attention to responsibility and verification. Ask exactly which files, databases, mailboxes, DNS records and redirects are included, who tests the result and how long the old service should remain active. A “free migration” is useful only when its scope matches the site and a rollback copy exists.

Staging test: Make one representative change to the chosen site platform away from the live site, test it and roll it back. This shows whether staging is a real workflow or only a feature label. Review this point before renewal and whenever the site takes on a new business-critical function.

Six checks before switching traffic

A controlled four-step migration

1. 1

   Inventory everything

   List files, databases, mailboxes, DNS, redirects, cron jobs, certificates, integrations and domain contacts. Note which supplier currently controls each item.

2. 2

   Back up and build

   Create an independent export, then import the chosen site platform to the destination. Keep the old site live and prevent search engines indexing a temporary copy.

3. 3

   Test before DNS

   Check clear pages, dependable forms, secure administration and recoverable content, forms, logins, email and analytics through a preview route. Compare important URLs and redirects so existing search visibility is not discarded.

4. 4

   Switch, observe, retain

   Change DNS during a quiet period, monitor both systems and keep the previous account through the propagation and verification window. Cancel only after recovery is proven.

What a safe migration setup looks like

Keep the domain under an account you control, lower DNS time-to-live in advance where practical and write the rollback values down. The old service is a recovery tool until external checks show the new one is complete.

Common mistakes to avoid

• Cancelling the old host as soon as files are copied, before DNS, email, forms, redirects and live transactions have been verified.
• Letting the hosting company or a web designer own the domain account, which can make a later move unnecessarily difficult.
• Treating a backup as proven recovery without downloading a copy or completing a test restore.
• Changing DNS, nameservers, plugins and server settings together, then being unable to identify which change caused the result.

Bottom line

For “how to keep email when moving site host”, overlap and testing are cheaper than reconstructing missing orders, enquiries or mail. Keep both the source and independent backup until the destination has passed the full visitor and owner journey.

Plan information: Provider features mentioned on this page were checked against public provider information on 11 September 2026. Prices and inclusions change, so confirm the live checkout before buying. Read our editorial policy and affiliate disclosure.