Exchange migrations: SE, Online and tenant moves
Exchange 2016 and 2019 have been out of support since October 2025, and since September 2026 Exchange Online has been progressively throttling and blocking outdated on-premises servers. Depending on the starting point, the route leads to Exchange Server SE, to Exchange Online or from one tenant to another. I plan and support all of these routes, with a focus on mail routing, gateways and coexistence.
- Exchange Server SE
- Exchange Online
- Exchange 2016/2019
- Tenant-to-Tenant
- Cross-Forest
- Hybrid
Migration paths
- Exchange 2016/2019 to SEExchange 2019 with a current CU can be upgraded in-place to Exchange Server SE; Exchange 2016 requires a migration to new servers. Coexistence, certificates, connectors and namespaces are planned in advance.
- Exchange Server SE to Exchange OnlineHybrid as a transition, mailbox migration in waves, moving the MX and upstream gateways.
- Tenant-to-TenantMergers, divestitures and rebrandings: moving mailboxes, domains and mail routing between Microsoft 365 tenants, with a planned domain handover.
- Cross-Forest and consolidationMerging or separating Exchange organizations across multiple Active Directory forests.
- The last Exchange serverAfter the cloud migration, a server often remains for management and SMTP relay. Whether it can be shut down and what is missing afterwards is clarified in advance.
More than mailboxes
Every Exchange migration also moves mail routing, certificates, application mail, gateways and authentication records. For the route from Exchange Server to Exchange Online, the Exchange Online migration page describes the details of mailbox migration, device mail and the gateway move.
How an engagement runs
- InventoryVersions, mailboxes, connectors, submitting systems and dependencies in the directory.
- Target design and coexistenceMigration path, sequence and the phase in which the old and new environments run in parallel.
- Migration in wavesPilot group first, then batches with defined checkpoints, routing changes one at a time and reversible.
- DecommissioningCleanly uninstalling the old servers, cleaning up the directory, documenting the target environment.
Real-world examples
- Transport enforcement for outdated Exchange servers: why Exchange 2016 and 2019 lose mail flow in hybrid.
- EXO migration without remote move: the controlled rebuild of mailboxes when the standard route is not available.
- Aggregating sending IP addresses: the inventory of the systems that are easily forgotten in a migration.
- Common causes of mail loops: the most frequent failure pattern after routing changes.
