Who this is for
- You still run Exchange Server 2016 or 2019, which reached end of support on October 14, 2025.
- Patching, certificate renewals and cumulative updates take up IT weekends.
- A partial move years ago left a hybrid setup nobody fully understands.
- Scanners, ERP systems, monitoring tools or scripts relay mail through the Exchange server.
- You want to retire on-premises Exchange, or keep only what is still justified.
What is in scope, and what is not
Usually in scope
- Inventory of user, shared and resource mailboxes, archives, public folders, transport rules, connectors, journaling and certificates
- A relay inventory: every app, scanner and device that sends mail through Exchange, with a replacement option for each
- Cutover or hybrid recommendation with the trade-offs written down
- Target readiness: licensing, directory sync, MFA and connectors
- Mailbox moves in planned batches, with delegates and shared mailboxes kept together
- MX, Autodiscover, SPF, DKIM and DMARC changes and Outlook and mobile reconnection
- A decommission checklist for the last Exchange server
Handled separately or agreed during discovery
- Rewriting custom applications that use Exchange Web Services. We find them during discovery; the code work is its own project. See EWS retirement remediation.
- Upgrading servers you keep on-premises to Exchange Server Subscription Edition.
- Replacing third-party archiving or journaling products.
- Replacing printers or devices that cannot send mail by any supported method.
Cutover or hybrid: how we choose
| Question | Cutover migration | Hybrid deployment |
|---|---|---|
| Size | Small environments; Microsoft caps cutover at 2,000 mailboxes and recommends it for far fewer | Any size, including large or phased moves |
| Move window | Everyone moves together | Batches over weeks, with mailboxes in both places meanwhile |
| Identities | Cloud accounts, no directory sync needed | Directory-synced identities from on-premises Active Directory |
| Coexistence | None after the switch | Shared free/busy and mail routing between on-premises and cloud |
| After the move | Exchange server can usually be removed | A supported recipient-management method must be in place before the last server goes |
How the project runs
- Assessment. Versions, mailbox sizes, archives, public folders, connectors, certificates and relays.
- Method decision. Cutover or hybrid, written down with the reasons.
- Relay redesign first. Apps and devices are moved to authenticated SMTP, direct send or a connector before the first batch, not after.
- Target readiness. Licensing, directory sync, MFA and Conditional Access checked.
- Pilot batch. A small group that includes delegates and shared mailbox users.
- Production batches. Planned moves with user notices and a known support channel.
- Mail flow cutover. MX and Autodiscover changes, then validation of Outlook, mobile and every relay sender.
- Decommission. What still needs a server, for how long, and the checklist to remove the rest.
More risks we plan for
| Risk | How we handle it |
|---|---|
| Large mailboxes and archives slow batches | Sizes measured in discovery and the largest mailboxes scheduled early |
| Old clients use basic authentication, which Exchange Online no longer accepts | Clients and apps checked for modern authentication before cutover |
| Hybrid certificate expires mid-project | Renewal date and owner recorded during assessment |
| DNS changes take longer than expected | Record TTLs lowered ahead of cutover |
What we need from you
- Exchange and Active Directory admin access, plus Microsoft 365 admin access
- DNS access for your mail domains
- Any list you have of apps and devices that send mail, and who owns them
- A network or firewall contact if hybrid is used
- Pilot users, including an assistant who manages someone else's calendar
- Maintenance windows for cutover
How long it takes
Our Exchange Server exit package lists a typical duration of 4 to 10 weeks depending on mailbox count and relay dependencies, set after discovery.
Proof from similar projects
- Getting off Exchange Server without breaking the apps that send mail: full inventory of apps, scanners and relays, with the relay redesign done before final decommission.
- Exchange Server SE hybrid update to Microsoft Graph: about 460 mailboxes, 2 Exchange SE servers, 3 coexistence features tested, 4 weeks from assessment to handoff.