Before changing MX records, export the current zone, inventory shared mailboxes and aliases, and confirm SPF, DKIM, and DMARC for the destination platform. Test autodiscover and mobile profiles with a pilot group when possible.
Pre-migration checklist
Plan migration windows, validate outbound mail after DNS changes, and keep rollback steps documented — including how to revert MX if deliverability issues appear.
Typical starting point
- Export current DNS zone and document TTL values
- Inventory shared mailboxes, aliases, and distribution lists
- Confirm SPF, DKIM, and DMARC for destination platform
- Plan pilot group for mobile and desktop profiles
- Document rollback MX values and test window
After structured delivery
- Documented registrar, DNS, and hosting ownership
- Exported MX, SPF, DKIM, and DMARC records
- Named approvers for infrastructure changes
- Backup and restore paths for mail and site
- Rollback plan before every migration
- Support paths that survive staff changes
What was improved
The delivery focus was practical: address the highest-friction gaps in servers, hosting, email & dns without overclaiming results or forcing a rip-and-replace mandate.
Representative proof snapshots




What similar businesses can learn
Plan migration windows, validate outbound mail after DNS changes, and keep rollback steps documented — including how to revert MX if deliverability issues appear.

