Exchange Server to Microsoft 365 migration

It is the process of moving mailboxes and email operations from an on-premises Exchange organization to Exchange Online. Depending on the environment, it can involve hybrid configuration, identity synchronization, remote mailbox moves, temporary coexistence, DNS, public folders and a post-migration plan to keep or retire on-premises Exchange.

No. Microsoft ended support for Exchange Server 2016 and Exchange Server 2019 on October 14, 2025. In 2026, the current on-premises product line is Exchange Server Subscription Edition. A 2016/2019 server may continue to run technically, but it no longer receives normal product support and servicing.

A technical path may exist, but these are out-of-support versions and we do not treat them as a standard migration. Depending on build, topology and workloads, the project may require an upgrade, a bridge version, Active Directory remediation or a specialized tool before data can be moved.

Full Hybrid is designed for coexistence and phased mailbox moves with a more integrated experience. Minimal Hybrid reduces the coexistence footprint for a shorter transition. Cutover moves the organization in a concentrated window and is not intended for prolonged coexistence between source and destination.

Microsoft documents a maximum of 2,000 mailboxes for cutover migration, while also noting that approximately 150 or fewer is more practical because of the time needed to create and migrate users. Mailbox count alone does not determine the strategy: identity, dependencies and the change window also matter.

With an Exchange-to-Exchange Online mailbox move, mailbox content includes email, calendar, contacts, tasks and rules stored in the mailbox. Organization-level transport rules, connectors, relays and other configuration objects are not part of the mailbox and require separate work.

Microsoft documents that explicit permissions such as Send As, Full Access, Send on Behalf and folder permissions can migrate in a hybrid deployment. We still validate groups, inherited permissions, automapping and cross-premises delegations because dependencies can require remediation.

They use a dedicated migration procedure rather than moving automatically with each mailbox. Microsoft defines separate prerequisites and limits, and the final stage of a native public-folder migration requires a lockout or downtime window for those folders.

There is no universal timeline. It depends on mailbox count and size, MRS throughput, Exchange/AD health, public folders, dependencies, number of migration waves and coexistence requirements. Pilot moves provide real throughput measurements before the schedule is finalized.

We design the project to minimize user impact, particularly with phased hybrid moves. We do not promise zero downtime: Outlook may require a restart or authentication, some older mobile devices may need reconfiguration and DNS or external applications can introduce a transition period.

Not automatically. Public folders, DNS, hybrid configuration, SMTP relay, applications and Exchange attribute management must be resolved first. Microsoft now supports several end states: keep Exchange, shut down the final server and use Management Tools in eligible scenarios, or transfer the Source of Authority for Exchange attributes to the cloud and follow Microsoft's documented uninstall procedure.

Yes. Microsoft currently documents Exchange Hybrid support with Cloud Sync and Exchange attribute writeback. Connect Sync still provides capabilities that may be required in certain topologies, so the choice should be based on the complete identity architecture rather than a single feature.