Email Migration Cutover Strategy

Migrating email: strategy defines the risk

Email is the most sensitive service in any migration, because any interruption is immediately visible to the whole company. When moving mailboxes to Exchange Online, the choice of migration strategy determines risk, timeline and user experience. There is no single right answer; there is the right answer for your size and source.

As a Microsoft Solutions Partner and CSP, RHC sizes the strategy to the source environment and the client's risk appetite.

The three main strategies

Cutover

Cutover migrates all mailboxes in a single move, with no coexistence. It is simple and fast, ideal for small bases. The risk is concentrating everything in one window; if something fails, it affects everyone at once.

Staged migration

Staged migration moves batches of mailboxes over time, keeping part on the source. It suits mid-size bases that want to spread the effort, with partial coexistence during the transition.

Hybrid migration

Hybrid creates rich coexistence between on-prem Exchange and Exchange Online: unified mail flow, shared calendar availability and on-demand mailbox moves. It is the approach for large bases that must migrate with no perceptible interruption, at the cost of greater configuration complexity.

The role of DNS and MX

Regardless of strategy, the mail-flow cutover revolves around DNS:

• The MX record points to where messages are delivered.
• Autodiscover directs clients to connect to the right server.
• The TTL of records should be lowered before the cutover to speed propagation.

Planning the MX and autodiscover change with a low TTL avoids messages stuck in transit during cutover.

Preparation before the cutover

A safe cutover depends on what you do beforehand:

1. Provision and license users in Microsoft 365.
2. Pre-sync as much data as possible before the final window.
3. Validate identity and access (Entra ID, MFA, conditional access).
4. Communicate to users the date, time and what changes.
5. Prepare support for post-cutover hypercare.

The cutover window

During the final window:

• Run the delta sync of data changed since the pre-sync.
• Adjust the MX record and autodiscover to Exchange Online.
• Reconfigure clients (Outlook, mobile) or let autodiscover do the work.
• Validate send, receive, calendar and mobile access with a pilot group.

After the cutover

The work does not end at cutover:

• Monitor mail queues and delivery reports for a few days.
• Adjust transport rules, connectors and signatures.
• Decommission the source environment only after a stability period.
• Close pending items for shared mailboxes, lists and resources.

Email cutover checklist

• Strategy chosen by size and source.
• Users provisioned and licensed in Microsoft 365.
• DNS TTL lowered before the window.
• Pre-sync completed and validated.
• MX and autodiscover change plan ready.
• User communication sent.
• Hypercare support staffed.
• Rollback plan documented.
• Source decommission criteria defined.

RHC plans and executes email migrations to Exchange Online with the right strategy, minimizing downtime and caring for the user experience.