Migration

How to switch email providers without losing a single message

Fear of losing email is what keeps many companies for years with a provider that no longer serves them. This is what actually happens in a migration, what can go wrong, and what to demand from whoever carries it out.

July 28, 2026

The question that always comes first is the same one: "am I going to lose my old email?". The short answer is no, and it is worth understanding why, because knowing it changes the conversation with any provider.

What moves and what doesn't

Migrating email is three different things that usually get bundled into one:

  • Where new mail arrives. Defined by a DNS record called MX. Changing it is a matter of minutes.
  • Where the old mail lives. Your history is on the current server and gets copied to the new one. Copied, not moved: the original stays there until you decide to switch it off.
  • Who may send on your behalf. SPF, DKIM and DMARC have to be rebuilt with the new provider. It is the part most often neglected, and the one that decides whether your email reaches the inbox after the change.

That second line is the key to why nothing gets lost: during the migration there are two copies. The old one doesn't disappear just because you started.

Order matters

  1. Inventory. Mailboxes, aliases, distribution lists, forwarding rules, and — the most forgotten of all — every service that sends email with your domain: invoicing, CRM, campaigns, ticketing, the online store.
  2. Lower the TTL days in advance. The TTL is how long the world's servers remember your configuration. If it is set to 24 hours, your change takes up to a day to apply everywhere. Lowering it to five minutes ahead of time makes the real change almost instant. This step is the difference between a clean migration and a day of email split across two servers.
  3. Create the mailboxes and copy the history. It is copied over IMAP while email keeps arriving at the old provider. Nobody notices; there is no interruption.
  4. Change the MX records. From here on, new mail arrives at the new provider.
  5. Sync the backlog. Whatever reached the old provider during propagation gets passed across again. This second sweep is what guarantees nothing is left behind.
  6. Rebuild authentication. A new SPF with every sending service, DKIM signing on each platform, DMARC reviewed.
  7. Leave the old one switched on for a few days. It costs little and is your insurance against any surprise.

What goes wrong in practice

A high TTL

If nobody lowered it beforehand, for hours part of the world sends to the old server and part to the new one. Nothing is lost — the old one keeps receiving — but the email ends up split and has to be reconciled. It is the number one cause of migrations that "went wrong".

Forgetting who else sends on your behalf

The mailboxes get migrated, the SPF is rebuilt with the new provider… and the invoicing system is left out. Result: people's email arrives fine and the invoices start landing in spam. Nobody connects the two, because the email "does work".

Shared folders and aliases

Mailboxes migrate on their own; shared mailboxes, distribution lists and aliases have to be recreated by hand. If they are not in the initial inventory, they surface days later when somebody notices they stopped receiving something.

Application passwords

The printer that scans to email, the ERP that sends notifications, the reception phone. They all have stored credentials that stop working. They belong in the inventory.

Before migrating, look at where you stand today

If your current setup already has gaps, migrating without seeing them drags them to the new provider. The checker is free and takes seconds.

Check my domain

What to demand from whoever does it

  • That they lower the TTL in advance and tell you when they did it.
  • That they show you the inventory before starting, including the services that send with your domain.
  • That they run the second sweep after the MX change, not just the initial copy.
  • That they leave the old provider active for a few days.
  • That they rebuild SPF, DKIM and DMARC and show you the result. If this is not in the proposal, the migration is half done.
  • That they tell you how long the real risk window will be. If the answer is "there isn't one", be suspicious; if it is "a few minutes while DNS propagates", you are in good hands.

How long it really takes

Changing the MX is a matter of minutes. What takes time is copying the history, and that depends on volume: a few gigabytes copy in hours. That is why a typical SME migration fits in 48 hours end to end, with the bulk of the work happening while everyone carries on using their email as normal.

What doesn't fit in 48 hours is reaching p=reject on DMARC, because that requires days of reports to confirm that all your legitimate email aligns. Anyone promising you total protection against impersonation on day one is describing the process wrongly.

Keep reading