Moving Your Email to a New Host (Without Losing a Message)

The fear every business owner has when switching email providers: losing mail in the middle of the move. Done right, you don't. Done wrong, it's a mess for weeks. Here's what actually happens.

Why people leave their current host

• Microsoft 365 keeps raising prices. What was $5/user a few years ago is now well over $10, with features moving up into more expensive tiers.
• GoDaddy email is rough. Slow webmail, frequent deliverability complaints, expensive add-ons.
• Cobbled-together setup. Mail at one provider, domain at another, DKIM at a third — nobody owns the whole thing.
• Deliverability problems. Outgoing mail keeps landing in spam (often a SPF, DKIM, and DMARC issue, but sometimes the current host is on a bad-reputation IP range).
• Business sale or rebrand. New domain, want to start clean.

What actually gets moved

• All existing mail. Every folder, including custom folders and subfolders, copied server-to-server via IMAP. Years of archive included.
• Mailboxes and aliases. Every [email protected] address and every alias (e.g., sales@ → jason@) gets recreated on the new host.
• Forwarders and mailing lists. If info@ was forwarding to three people, that gets rebuilt.
• Catch-all rules (if you had one).
• Auto-responders / vacation messages — usually need to be re-set on the new host, but we capture the wording before the move.

What doesn't always move cleanly: calendars and contacts when migrating from Exchange to a non-Exchange host (we'll talk about options if that applies to you), encrypted/signed mail (the keys stay with whoever holds them), and mailbox-level rules — those usually need to be re-created on the new host.

The migration process, in plain English

1. Inventory. Get a list of every mailbox, alias, forwarder, distribution list, and auto-responder on the current host. This is the most-skipped step and the one that causes "where did X go?" calls a week later.
2. Build the new host in parallel. Mailboxes, aliases, and forwarders get set up on our server before any DNS changes. Nothing is live yet.
3. Initial IMAP sync. Server-to-server copy of every existing message from the old host to the new one. Usually runs overnight for typical small-business volumes.
4. Lower MX TTL. 24–48 hours before cutover, we drop the time-to-live on your MX records to 5 minutes. This means the cutover itself is fast instead of taking a day to propagate.
5. Cutover. MX records updated to point at the new host. SPF, DKIM, and DMARC updated to match. Within minutes, new mail arrives at the new host.
6. Delta sync. Any mail that arrived at the old host between the initial sync and the cutover gets copied across. This is the step most amateurs skip, and the reason mail "disappears".
7. Reconfigure clients. Outlook, Apple Mail, iPhones, Androids — each device points at the new server. Modern setups using autodiscover often handle this automatically; older Outlook profiles sometimes need manual help.

What usually goes wrong

• No delta sync. Mail that arrived at the old host during cutover is stranded there. Customer thinks the new system "lost" mail; really, it was never copied across.
• Old SPF record left behind. Domain authorizes the old host as a sender even though new mail is going through the new host. Outgoing mail flagged as suspicious until SPF is updated.
• Distribution list forgotten. Inventory step was skipped, so the new host doesn't have the everyone@ list. Internal emails bounce for a few days until someone notices.
• TTL not lowered first. Cutover takes 24+ hours instead of 5 minutes because the old MX records are still cached at recipients' DNS resolvers.
• Auto-responder lost. The "I'm out until Monday" message was on the old host; new host doesn't have it; customers don't get a response.

How long it takes

• Small business (1–5 mailboxes, under ~5 GB each): half a day of setup work, overnight initial sync, fast cutover next morning.
• Medium (5–25 mailboxes, mixed sizes): 1–2 days end-to-end, usually scheduled around a weekend.
• Large (more than 25 mailboxes, or single mailboxes over ~50 GB): we plan it over 1–2 weeks — staged migration so we're not betting the whole company on one overnight sync.

How we do this for customers

We've done this many times: Microsoft 365 to us, GoDaddy to us, Bluehost and generic shared-hosting accounts to us, and the occasional in-house Exchange box to us. We quote a fixed price up front based on the inventory, schedule the cutover for a quiet time (overnight or weekend), and run the delta sync so nothing's stranded on the old host.

If you're thinking about switching, tell us what you're running today and we'll give you a quote. If we're not the right fit, we'll say so — sometimes Microsoft 365 really is the right answer for a specific business.