Migration Guide
How to Migrate Email to Microsoft 365 with Minimal Downtime
A mail migration that goes badly shows up immediately — bounced messages, missing calendar invites, a flood of "I can't send email" tickets. The difference between a smooth cutover and a chaotic one is almost entirely in the sequencing.
The sequence that keeps mail flowing
Downtime during an email migration almost always traces back to skipping one of these steps, not to Microsoft 365 itself being unreliable.
- Lower DNS TTL early. Reduce your MX record's time-to-live 24–48 hours before cutover so the eventual switch propagates fast.
- Enable dual delivery. Route mail to both the old and new systems during migration so nothing sent mid-transition is lost.
- Migrate in batches. Move mailboxes in scheduled groups, starting with a small pilot, rather than all at once.
- Cut over and reconnect devices. Switch MX records once mail is fully migrated, then reconnect desktop and mobile clients on a set schedule.
Why the pilot batch matters here too
A small pilot group surfaces device reconnection issues or missing distribution list members before the whole organization hits the same problem at once.
The most common mistake
Switching MX records before the DNS TTL has been lowered in advance, which leaves some recipients' mail servers using stale routing for hours or days.
Migration Checklist
| Task | Status |
|---|---|
| Lower DNS TTL 24–48 hours before planned cutover | ☐ |
| Enable dual delivery between old and new mail systems | ☐ |
| Migrate a pilot batch and validate mail flow | ☐ |
| Migrate remaining mailboxes in scheduled batches | ☐ |
| Switch MX records at the planned cutover window | ☐ |
| Reconnect desktop and mobile devices post-cutover | ☐ |
Frequently Asked Questions
Can email migrate without any inbox downtime at all?
Near-zero downtime is realistic with staged batches and a low DNS TTL before cutover, though a short mail-flow pause during the final MX switch is normal.
What happens to email sent during the migration window?
Dual delivery routes mail to both the old and new systems during the transition, so nothing sent mid-migration gets lost.
Do mobile devices need to be reconfigured after cutover?
Yes, devices typically need to reconnect to the new mailbox, which is usually scheduled right after cutover to avoid a gap in access.
How far in advance should we lower our DNS TTL?
At least 24–48 hours before the planned cutover, so the MX record change propagates quickly instead of taking the default TTL to clear.
Related Guides
Conclusion
Minimal-downtime email migration comes down to preparation done days in advance — lowering DNS TTL, enabling dual delivery, and validating a pilot batch before committing the rest of the organization. Businesses that treat cutover as a single weekend event, without that lead time, are the ones most likely to see a spike in support tickets on Monday morning.
Rua Technologies plans and executes Microsoft 365 email migrations with staged cutovers designed to avoid disruption.
