← Work / Civil & commercial paving /

Artisan Paving — Email Migration

Moving a twenty-year-old business email setup to a new platform without a single customer noticing. Every address kept working, two decades of history came across, and the authentication records went in ahead of the switch so quotes and invoices never started landing in junk.

Result

No bounced mail, no lost history, nobody outside noticed

Delivered

Aug 2026

The migration nobody was supposed to notice

Email migrations go wrong in public. Addresses stop working, replies come from the wrong name, twenty years of history gets stranded on an old platform, and — the expensive one — authentication records don’t follow, so the company’s quotes and invoices quietly start landing in customers’ junk folders. Nobody tells you. You just stop hearing back.

The brief here made that risk sharper: nothing was to change publicly. Same addresses on the website, same addresses on invoices, no note to customers. Which meant the migration had to be invisible rather than merely quiet.

How it was sequenced

Everything that could be built and tested while mail was still flowing to the old platform was built and tested first. Accounts, addresses, send-as behaviour, signatures and the first full history import all happened before a single piece of mail moved.

Only one DNS record actually moves mail, and it went last. The others — domain verification and the mail-signing keys — were published early so they were live and fully propagated before anything flowed through the new platform. The record’s cache time was dropped to five minutes two days ahead of the switch, so the cutover propagated in minutes instead of most of a day.

Why there was effectively no downtime

During the propagation window some senders still deliver to the old platform and some to the new. Nothing is rejected; mail just lands in one of two places. Forwarding from the old mailboxes closed that gap live, and a second sweep-up import afterwards caught anything that arrived mid-switch, so the two sides matched.

The details that decide whether it worked

Replies had to go out from the right address automatically rather than relying on someone remembering to switch, each address kept its own signature, and the authentication records were right on day one rather than fixed after the first complaint. Those three are the whole job. Get them wrong and the migration is technically complete and practically broken.

Services

Email Migration · DNS & Mail Authentication (SPF/DKIM) · Mailbox & History Import · IT Support