Email migration without losing a thing

What an email migration involves

A mailbox looks like a list of messages, but it is really four things stacked together. There are the messages themselves, the folder structure someone built over years, the flags that record what has been read, starred or replied to, and the addresses and settings that make the account send and receive. A migration has to carry all four across, not just the first.

That is why it is more than exporting a file and importing it somewhere else. The messages have to keep their folders, the read states have to survive, the account has to keep working for every person and device still pointed at it, and incoming mail has to arrive without a gap while the switch happens. Miss any one of those and the move technically succeeds while quietly failing the people who use it.

There are two halves to the job. The first is the copy, pulling the full mailbox from the old provider and reproducing it on the new one exactly. The second is the cutover, the moment new mail stops flowing to the old provider and starts flowing to the new, which is governed by your DNS records and takes time to spread across the internet. Treating these as one rushed step is where most of the pain comes from. Treating them as two careful ones is how a migration stays invisible.

Moving without downtime or lost mail

The reliable way to move email is a copy that works at the IMAP level, the same protocol your mail clients speak. It reads each message with its folder and flags and writes it to the new mailbox so the destination mirrors the source instead of flattening into one heap. A good copy is also safe to run more than once without making duplicates, because real migrations rarely finish cleanly on the first pass and usually need a top up for whatever landed late.

The rule that keeps the whole thing safe is simple: leave the old mailbox untouched until the new one is verified. You copy, you compare message counts, you spot check a few folders, and only then do you move people over and retire the old account. Treating the source as read only means the worst case is running the copy again, never discovering the original has been damaged. Before any of that, though, walk this checklist in order.

1. Back up both ends firstExport a copy of the old mailbox before you touch anything, so there is always a known good version to fall back to if a step goes wrong.
2. Lower the DNS TTL in advanceDrop the time to live on your mail records a day or two ahead, so when you flip them the change propagates in minutes rather than hanging on for hours.
3. Verify the receiving recordsConfirm the new provider's MX, SPF, DKIM and DMARC are correct before cutover, so mail is accepted and does not start landing in spam the moment it arrives.
4. Test with a pilot mailboxRun the full copy on one account first and check folders, flags and counts, so you catch any quirk on a single box instead of across the whole company.
5. Cut over, then top upSwitch the DNS during a quiet window with both mailboxes live, then run one final copy once it settles so nothing that arrived late is left behind.

Timing and communication carry as much weight as the technical steps. Move during an evening or a weekend, tell people what will change and when, and keep both mailboxes reachable through the propagation window so mail arriving at either place is never lost. A migration that is flawless on paper but sprung on people mid workday still feels like an outage. This kind of careful cutover is part of the platforms and infrastructure work we take on, and the sequence above is the one we follow every time.

Common questions

Will I lose my folders and read and unread status?

Not with a migration done properly. An IMAP level copy carries the folder structure and the flags across, so the new mailbox mirrors the old one down to what was read and what was starred. Losing those is a symptom of a careless move, and it is exactly what careful tooling is built to prevent.

How long will my email be down during the move?

It should not be down at all. The copy happens while the old mailbox keeps running, and the cutover is a DNS change that routes new mail to the new provider. With a lowered TTL and both mailboxes live through the switch, people keep sending and receiving the whole time.

Can you move email between any two providers?

In general, yes, as long as both support IMAP, which nearly every mainstream provider does. Because the copy works mailbox to mailbox over that protocol, it is not tied to one vendor's import feature, so moving between two different services works the same way as moving between two accounts on one.