Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Migration

Change email hosting without downtime: migrate mail without losing messages

Published August 2026 · 10 min read · Updated 2026-11-21

To change email hosting without losing mail, the order is what keeps you safe: build and test the new mailboxes first, copy your existing mail across while the old service is still receiving, change the routing only when the new home is proven, then run a catch-up copy for anything that arrived during the switch. Nothing is cancelled until the new service has been carrying your mail cleanly, so the move finishes with no downtime and no missing messages.

Inventory mailboxes, aliases, forwards, groups, and senders

Do not migrate only visible inboxes. Document shared addresses, catch-all behaviour, autoresponders, distribution groups, application SMTP accounts, forwarding rules, quotas, and any systems that send mail for the domain.

Create and test the destination before routing changes

Provision every destination mailbox and alias first. Authenticate through webmail or a client, prepare any required SPF, DKIM and DMARC changes, and verify controlled sending and receiving before public mail routing changes. Those three records are the internet’s proof that mail from your domain is really yours: SPF lists which services may send for the domain, DKIM signs outgoing mail so receivers can verify it, and DMARC tells receivers what to do with mail that fails those checks.

Copy historical mail before the cutover

Run an initial IMAP or provider-supported migration while the old service is still authoritative for incoming mail. This moves the bulk of existing messages before the routing change and shortens the final synchronization window.

Change MX only after the receiving path works

MX records are the address lines in your domain’s settings that tell the internet which mail service receives your email. Update them when the destination is ready, and preserve any unrelated DNS records the domain still needs. Other servers remember the old answer for a while, a wait time called the TTL, so some senders may continue delivering to the old provider during the transition. Lowering that wait time a day or two ahead of the change keeps the in-between period short. MX preference chooses among published mail exchangers; it is not a timed cutover switch.

Watch the change spread with the DNS propagation checker | See how DotMoose runs the whole move

Synchronize mail that arrived during the transition

Keep the old mail service reachable after the MX change and run another synchronization to collect messages that arrived there while caches were still using the previous route. Compare representative folders and message counts before declaring the move complete.

What the people emailing you notice

Done in this order, nothing. Senders keep using the same addresses, their messages keep arriving, and replies come from the same place. The only people who see anything change are your own team, when they sign in to the new mailbox or update a mail app’s settings, and that happens after the new service is already receiving mail.

If your email already runs on Microsoft 365 or Google Workspace

Then it does not need to move at all. Email on a separate specialist service stays exactly where it is when your website changes hosts: the MX records stay untouched, your team keeps the same mailboxes and apps, and only the website moves. The mistakes happen when a hosting move changes mail records it never needed to touch, which is why the mail setup is recorded in full before any move begins.

Update clients and retire the old service last

Give users exact incoming and outgoing settings, monitor both providers for bounces and authentication failures, and verify application senders separately. Cancel the old service only after mail flow has settled and no messages remain stranded there.

Common questions

Will I lose email while changing email hosting?

Not if the move runs in this order. Your existing mail is copied before the routing changes, the old service keeps receiving during the switch, and a catch-up copy collects anything that arrived there. Messages are only at risk when the old service is cancelled early or the routing changes before the new mailboxes exist.

How long does an email hosting move take?

Copying the mailboxes usually takes hours, depending on how much mail there is. The routing change itself takes minutes once the wait time on the records has been lowered ahead of time. Most moves are fully settled within a day, with the old service kept available until the new one is proven.

Do people who email me need to do anything?

No. Your addresses do not change, and senders cannot tell the move happened. Only your own team may need updated settings in their mail apps.

Can I move my website and keep Microsoft 365 or Google Workspace email?

Yes, and that is the normal case. Email on a separate service stays put, its records are left untouched, and only the website moves.

Next step

Change email hosting without downtime by preparing destination mailboxes first, copying historical mail, preserving aliases and authentication, switching MX carefully, and synchronizing messages delivered during the transition.

Plan an email migration

Keep reading

Related guides.

BIMI readiness: what has to be in place before a brand logo can appear

Check DMARC enforcement, logo format, certificate requirements and mailbox-provider support before spending time on BIMI records that cannot be used yet.

Read the guide

MTA-STS setup: publish and test an HTTPS mail transport policy

Configure the MTA-STS DNS record, HTTPS policy file and certificate, then test policy mode and MX coverage before relying on strict transport enforcement.

Read the guide

TLS-RPT setup: receive reports about mail transport security failures

Publish a TLS reporting record, choose a report destination and interpret failures alongside MTA-STS or DANE so transport problems are visible.

Read the guide

More email & deliverability guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move