Choose an email migration window when the business, its administrators and required support contacts can all verify the result. A quiet hour is useful only when the destination is ready and someone can handle unexpected delivery or sign-in problems.
01 Schedule a controlled cutover
- Review working hours, customer locations, payroll or finance deadlines and any scheduled campaigns. Identify periods when delayed communication would have the greatest impact.
- Complete a pilot migration and measure the remaining data transfer. Resolve authentication, unsupported items and destination quota issues before setting a firm date.
- Confirm administrator access at both providers and the authoritative DNS service. Assign one change coordinator and name the people responsible for validation.
- Prepare the destination mailboxes, aliases, groups and sending applications. Give staff the new sign-in route and any device changes they must make.
- Write the change sequence, expected observation period and rollback criteria. Include a final reconciliation for messages that arrive at the source during transition.
- Announce the planned window through an approved business channel. State what users should do, where to report a problem and who will confirm completion.
- During cutover, record timestamps and test external inbound, outbound and internal delivery. Keep the source available for the agreed overlap.
Common questions
Is a weekend always best?
Not if the necessary staff or provider support is unavailable. Select a period that balances business impact with the ability to respond.
Does a low DNS TTL guarantee immediate switching?
No. Resolver caches and sending systems can behave differently. Plan an overlap and verify actual delivery rather than promising an exact instant.
What should trigger a pause?
Examples include failed pilot validation, missing administrator access, insufficient destination storage or unresolved routing. Correct a readiness problem before beginning the production change.