Email migration without downtime: the sequence that moves a company's mail safely

The domain's mail records are the steering wheel of a migration: whoever controls them decides where mail goes, so the cut happens there, deliberately, not in the mailbox.

Ask around and you will collect at least one story of a company that moved its email and lost a chunk of its history, or spent a week with mail trickling to two homes while customers wondered who had stopped answering. Migration is not risky because mail is fragile. It is risky because the sequence, done in reverse by people in a hurry, turns a routine move into an outage nobody planned.

The honest sequence starts before any technical move: inventory who exists and what history matters. Every address in use, every alias, every distribution list, every system that sends mail on the company's behalf, and then the archives, because years of correspondence are a record with legal and commercial weight. You cannot move what you have not counted, and the census is where the surprises live: the forgotten mailbox receiving supplier invoices, the device that mails itself, the old account a partner still writes to.

Next, stand up the new home while the old one still answers. The two systems run side by side, the mailboxes are filled with history, and nothing customer-facing changes yet. This is the step the rushed version skips, and it is the step that buys a calm handover: for a while the company has two mail homes and one direction of truth, and you rehearse on the new one while the old one keeps catching everything.

Then comes the cut, and the cut lives in the domain's mail records, not in anyone's mailbox. Those records are the steering wheel: they tell the world's mail systems where your addresses actually point. Change them deliberately, on a chosen day, and keep both systems alive through the handover window, because mail sent moments before the change will still arrive at the old house and needs collecting there. Retire the old setup only when the window has closed and the trickle has actually stopped.

Done in reverse, the same move breaks in ways that look like bad luck and are not. Cut the records first and the new home stands empty while messages scatter. Move the people first and replies bounce between two homes mid-conversation. Skip the inventory and the quiet senders surface for months afterwards as missing mail nobody can trace. Every one of these is a step executed out of order, which means every one was avoidable.

We run this sequence for companies as part of our cloud and domains work, and we plan it around the business calendar rather than against it. The honest caveat: every mail system has its edge cases, and those belong to whoever runs that system, read from its current documentation rather than from memory. What we own is the sequence and the records: an inventory agreed in advance, a cut performed deliberately, and a handover window watched until it is genuinely quiet.