Moving email affects more than an inbox. Password resets, customer replies, shared mailboxes, calendars, devices and accounting notifications may all depend on the same domain. A provider’s migration tool can copy messages while those other dependencies still fail. Start by identifying the whole service and the people who can authorise changes.
Inventory before changing DNS
Record domain/DNS ownership, current provider, individual and shared mailboxes, aliases, forwarding, calendars, contacts, archives and connected applications. Check licences and the actual migration method supported by the chosen plans. Keep administrator recovery independent of an email address which may stop working during the move. Do not reset or close the old account merely because a new mailbox opens.
List applications that send mail, including websites, scanners, invoicing and support systems. Their authentication and permitted sender configuration may need separate changes. A public form’s accepted receipt does not prove an operator notification or customer email was delivered. Keep those outcomes distinct in the test plan.
Plan a controlled transition
Agree the window, responsible owner, backup/export and fallback. Rehearse with suitable synthetic or authorised material. Explain any period where messages could reach either provider and how new items will be reconciled. DNS changes propagate according to caching and provider behaviour; do not promise a universally instantaneous switch or use a fixed delay as proof of completion.
Update only the records required by the verified provider instructions, preserving unrelated website and verification records. Check authentication for every legitimate sender. For DMARC, check that a passing SPF or DKIM identity aligns with the domain recipients see in the From address, as required by the domain’s policy. Copying another business’s record without understanding it can break delivery or weaken protection. Use the actual provider’s current configuration and check the result.
Verify the business can work
Test inbound and outbound mail with authorised controlled recipients, shared mailbox access, replies, aliases, calendars and common devices. Check junk/rejection behaviour and website/accounting notifications separately. Avoid sending real customer campaigns as a test. Review message counts and representative historical items rather than assume a progress bar establishes complete migration.
Remove temporary permissions only after confirming the new service and recovery path. Retain the old environment/export for the agreed lawful period and assign a final reconciliation/closure owner. Keep confidential mail out of public repositories and screenshots. A mailbox transfer may involve personal data and location/processor changes, so the contractual/privacy assessment belongs before the move.
The practical completion record should say which mail functions were independently verified, what remains uncertain, where recovery material is held and who will handle delayed or missing mail. That is more useful than a generic “migration successful” message.
Sources and review
Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.
Next review: 4 May 2027