Service business
Moving a domain without killing the email
A business moving its website to a new platform, where the migration plan covered the site and said nothing about the email.
Anonymous, a WordPress-hosted business
The challenge
The business email was silently dependent on DNS records the migration was about to change. Nothing in the plan accounted for it, and nobody had noticed. It is the kind of dependency that is invisible right up until the moment every inbox stops receiving.
The old process
The migration was ready to proceed on the assumption that moving a website only affects the website. It is a reasonable assumption and a wrong one, and the failure it produces is both total and hard to reverse quickly.
The system we built
- Migration halted before cutover, rather than after the discovery
- Every email dependency on the existing DNS traced and verified first
- Cutover sequenced so mail delivery never had a gap
- The old administrator kept reachable throughout, so nothing was stranded behind the change
The technology
- DNS
- WordPress
- GoHighLevel
The result
The migration completed with email continuity intact and no interruption to delivery. The valuable part was not the migration. It was stopping to check, because this failure is unrecoverable in the moment and completely avoidable an hour earlier.