Exchange Hybrid vs
Cutover Migration

What cutover migration actually does

Cutover migration moves all mailboxes from on-premise Exchange to Exchange Online in a single operation, typically over a defined window ranging from a weekend to a few days depending on data volume. Once complete, the on-premise Exchange server is decommissioned — there's no ongoing coexistence between the two environments. Users are provisioned directly in Microsoft 365, mail flow points entirely to Exchange Online, and the migration is, in a meaningful sense, finished.

This is the simpler of the two approaches both technically and in terms of ongoing management overhead, because there's nothing left running in parallel once cutover completes.

What hybrid migration actually does

Hybrid migration keeps on-premise Exchange and Exchange Online connected and operating together, sometimes for the duration of a phased migration, sometimes indefinitely as a permanent architecture. A hybrid configuration establishes trust and mail flow between both environments, allowing mailboxes to be migrated in batches over weeks or months while users on both sides continue to email each other seamlessly, share free/busy calendar data, and appear in the same global address list.

Hybrid is significantly more complex to configure — it requires deploying and maintaining Azure AD Connect for identity synchronisation, configuring a hybrid mail flow connector, and in most cases keeping at least one on-premise Exchange server running even after most or all mailboxes have moved, purely to manage recipient objects and hybrid configuration.

The decision factors that actually matter

Organisation size and mailbox count

Cutover migration has a practical ceiling. Microsoft's own guidance and most implementers treat cutover as suitable for roughly 150 mailboxes or fewer — beyond that, the single migration window becomes unwieldy, and the lack of coexistence means every user is affected simultaneously with no ability to stage the transition. Organisations above this size are typically better served by hybrid, purely for the ability to migrate in controlled batches.

Tolerance for a single cutover event

Cutover means every mailbox moves at once. For a small business where all users can reasonably be briefed and supported through a single migration weekend, this is a strength — the project has a clear, contained end date. For larger organisations, or those with departments that cannot all be unavailable or disrupted simultaneously, a single mass cutover is a real operational risk, and hybrid's batch-based approach is the safer path.

Whether on-premise infrastructure needs to persist

Some organisations have applications, printers, scanners, or line-of-business systems that relay email through an on-premise Exchange server and cannot be immediately reconfigured. Hybrid allows this infrastructure to keep functioning during a longer transition, or in some cases indefinitely, without forcing every dependency to be resolved before mail can move. Cutover requires all of this to be addressed before migration, since there's no on-premise environment left afterward.

Directory and identity requirements

If the organisation needs to maintain synchronised identities between on-premise Active Directory and Microsoft 365 — for single sign-on, for managing distribution groups from an existing on-premise tool, or because of a broader Active Directory-dependent application landscape — hybrid (or at minimum, Azure AD Connect without full hybrid Exchange) is generally required. Cutover migrations typically move to cloud-only identity management.

Comparison at a glance

A third option worth knowing about: minimal hybrid

Microsoft also supports a "minimal hybrid" or Hybrid Configuration Wizard Express configuration, which provides the coexistence benefits of hybrid — mail flow and free/busy sharing — without the full weight of a permanent hybrid architecture. This suits organisations that want a smoother, staged migration experience without committing to hybrid as a long-term state, and can be decommissioned once all mailboxes have moved, unlike full hybrid deployments which are often left in place by design.

What this decision does not need to be

This choice is sometimes treated as a permanent architectural commitment, but for most organisations migrating fully to the cloud, hybrid is a transitional state, not a destination. The goal for most businesses is a fully cloud-based Exchange Online environment; hybrid is the path some of them need to get there without disruption, not the end state itself. Deciding cutover vs. hybrid is really a decision about how much staging and coexistence your organisation needs during the transition — not a decision about your long-term Microsoft 365 architecture.

For a broader look at planning timelines regardless of which architecture you choose, see our guide to how long a Microsoft 365 migration actually takes.

CloudyNex runs both hybrid and cutover Exchange Online migrations, and the right approach is always determined during discovery — based on your mailbox count, infrastructure dependencies, and tolerance for a single cutover event — rather than assumed in advance.