Choosing the right migration path
There is no single "best" Exchange migration — only the best fit for a given tenant size, bandwidth, downtime tolerance and regulatory posture. For under 150 mailboxes with a maintenance window, a Cut Over migration is fast and clean: every mailbox moves in one batch and the on-premises Exchange org is decommissioned. For larger estates, Staged migration moves batches over weeks while keeping the on-premises server alive for legacy mailboxes.
Hybrid is the answer when mailboxes must live on both sides for an extended period — typically because of compliance, large archive footprints, or a phased business rollout. IMAP migration is a last-resort path for non-Exchange source systems (Lotus Domino, Gmail, IMAP hosts) where only mailbox contents, not calendar/free-busy, need to move.
Tenant preparation before the first mailbox moves
Verify the public domain is added and verified in the M365 tenant, set Exchange Online as the intended target, and confirm the accepted domains match what users will address mail with. Run the Microsoft 365 network connectivity test from a representative client site to confirm the path to Exchange Online is clean.
- Add and verify the public domain in the M365 tenant
- Create mail-enabled users and assign Exchange Online licences
- Configure accepted domains and email address policies
- Run the M365 network connectivity test from each branch
- Confirm DNS TTLs are lowered 24h before cutover
Hybrid configuration with Azure AD Connect & ADFS
A true Hybrid needs Azure AD Connect synchronising on-premises identities into Entra ID, plus the Hybrid Configuration Wizard (HCW) to establish free/busy, mail flow and mailbox routing between the orgs. When SSO is required, ADFS (or Pass-Through Authentication) gives users a seamless sign-on experience so they are not prompted twice.
The most common Hybrid break I see is certificate expiry on the ADFS / Exchange federation endpoints. Put a calendar reminder for renewal 30 days before expiry and test the metadata refresh in advance — a failed token-signing certificate takes down SSO for the whole tenant.
Mail-flow hardening after cutover
Once mailboxes are in Exchange Online, harden the mail path: publish SPF, DKIM and DMARC, enable Defender for Office 365 policies, and configure outbound connectors for any on-premises SMTP relay devices (scanners, LOB apps). Test the relay with authenticated submission rather than open connectors.
Lessons learned
- Always run a pilot batch of 5–10 mailboxes before bulk migration
- Lower DNS TTLs 24 hours before cutover so MX changes propagate fast
- Keep the last on-premises Exchange server for management even after migration — do not rush to decommission
- Document the Hybrid connector and certificate renewal dates in the runbook
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.