Moving 25 domains and their mail to a new server
Twenty-five client domains, with their websites and mailboxes, moved from a shared host onto our own Debian server, with a per-domain status report at the end.
The situation
The hosting desk had grown on a shared host we did not control. Each client domain needed the same sequence: a DNS zone we could edit, a mailbox sync that did not lose anything, a website moved and tested, and nameservers changed at the registrar in the right order.
What we did
Each domain got a Cloudflare zone and its records before anything moved. Mail was synced mailbox by mailbox with the originals left in place, so a cut-over could be undone. Websites were moved and checked on the new server before DNS pointed at it. The post-migration report lists every domain with its status and the action still outstanding, including one domain found to have been hijacked at the registrar, which is the kind of thing a migration surfaces.
Since then: DKIM signing and DMARC published per domain, SPF corrected where a client's mail also leaves from Microsoft 365, and a relay path for clients who run both, so an address that exists only on our server still gets its mail.
What changed
Twenty-three mail domains and 84 mailboxes now sit on a server we patch, back up and answer for, with a panel the clients can use themselves.
Sound familiar?
Tell us which part. A first look is usually read-only, and you get the write-up either way.
Start a conversation →