Exchange Server to Microsoft 365 Migration
Exchange on-prem is dying. Cutover, staged, or hybrid. Public folders, transport rules, shared mailboxes — all preserved. 300+ Exchange migrations, 0 data loss, fixed-fee SOW, rollback in writing.
300+ Exchange Projects · 99.8% Success · Microsoft Partner
Every mailbox. Every public folder. Every calendar.
What's killing on-prem Exchange.
Exchange 2016 mainstream support ended 2020. Extended support runs out. Security patches drying up. Hardware refresh means new CALs, new server, or admit defeat and move to M365.
When internal teams run cutover alone, MX, SPF, DKIM, or Autodiscover misconfigurations cause full mail outage for 72+ hours. Our 2-4 hour window stays on track with rollback signed off.
Zero data loss across 300+ Exchange migrations. Every mailbox verified pre-cutover with SHA-256 hash comparison, every public folder permission mapped and re-applied.
Incremental sync handles mailboxes over 100 GB efficiently. Delta sync on the final weekend means the cutover window stays under 4 hours even at scale.
Every mailbox. Every public folder.
Cutover, staged, or hybrid
Cutover for under 150 users in one weekend. Staged for 150-2000 users over weeks. Hybrid for long-running coexistence and phased cutover — we pick the right one after discovery.
Public folder migration
Public folder hierarchies, permissions, mail-enabled folders, and nested structures. Migrate to Exchange Online public folders or Microsoft 365 Groups — mapped to usage pattern.
Transport rules & journaling
Every custom transport rule, connector, journaling configuration, and message hygiene setting recreated in Exchange Online. Compliance continues unbroken.
Shared mailboxes & delegates
Shared mailboxes, room/equipment mailboxes, send-as / send-on-behalf, full-mailbox delegate permissions — mapped pre-cutover and validated before MX flip.
Outlook profile + mobile
Autodiscover configured before cutover. Users get one-click profile reset on Monday morning. iPhone/Android Outlook app rollout guide included.
Exchange decommission
After cutover we verify every mailbox, public folder, and mail-flow route. Documented decommission steps, hybrid teardown (or keep minimal hybrid), hardware sign-off.
Four phases. One playbook.
Assess
1-3 days · Exchange version + mailbox inventory, public folder scan, third-party integration audit, fixed-price SOW.
Plan
3-5 days · M365 tenant provisioned, hybrid config wizard, security baseline (MFA, Conditional Access, DLP), runbook + rollback signed off.
Pilot
1-2 days · 10-20 users migrated first. Validate Outlook profiles, mobile Autodiscover, shared mailboxes, mail flow. Fix every issue before full wave.
Cutover
1-5 days · Wave-based migration with 24/7 monitoring. Delta sync captures changes, MX flip runs in a 2-4 hour off-hours window. Rollback ready.
The engineers on your project.
No outsourced ticket triage. The same three engineers handle Hybrid Configuration Wizard, public folder routing decisions, MX cutover, and post-migration decommissioning on every Exchange engagement.
Sreenivasa Reddy
Founder & Principal Migration Engineer
MCSE Messaging · 25 yrs on Exchange (5.5 → SE) · 500+ migrations led
Owns hybrid coexistence architecture and the EOL migration calls. When Exchange 2010/2013/2016/2019 reaches forced-migration territory, this is the call that gets made. Direct contact for enterprise SOW + multi-site DAG → M365 cutovers.
Roshan Pujari
Senior Migration Engineer · Hybrid + Cutover Lead
Microsoft Certified · Exchange + M365
Runs the Hybrid Configuration Wizard, OAuth trust setup, Azure AD Connect sync, and the actual cutover scheduling. Owns the staged + hybrid migration playbook end-to-end.
Bhargav
Senior Migration Engineer · Mail Flow + Public Folders
Microsoft Certified · Exchange + M365 Messaging
Public folder migration architect (Modern Public Folders vs M365 Groups decision), transport rule porting, Safety Net replay, and post-cutover delta sync. Owns the Exchange-specific gotchas other MSPs miss.
Three engagements. Three different shapes.
Anonymized. Scope → challenge → fix → outcome. The kind of operational detail you need before trusting an MSP with a hybrid coexistence cutover or an EOL migration under regulatory pressure.
Banking & Finance · ~600 mailboxes · Pennsylvania · Hybrid · Hybrid Exchange → Microsoft 365
Hybrid coexistence migration with FFIEC compliance + zero customer-facing email disruption
Scope
Mid-size Pennsylvania bank running on-prem Exchange 2016 in a multi-site DAG configuration. ~600 mailboxes including teller-level shared inboxes, branch-level distribution lists, and executive accounts with regulatory retention requirements. FFIEC compliance review scheduled within 90 days of planned cutover. Could not have customer-facing email outages during business hours.
Challenge
Hybrid coexistence required so both on-prem and M365 mailboxes could coexist during the transition (executives moved last per the bank's preference). Public folder hierarchy used heavily for shared compliance archives — needed migration to either M365 Groups or modern public folders depending on usage pattern. Audit trail required for every mailbox touch. FFIEC reviewer expected documentation of every mail flow change.
Fix
Phased migration over 6 weeks with Hybrid Configuration Wizard + OAuth trust setup. Wave 1: pilot of 20 IT/admin users. Wave 2: branch tellers (300 mailboxes). Wave 3: corporate office. Wave 4: executive team last. Public folders evaluated per-folder: low-traffic compliance archives became M365 Groups, high-volume shared inboxes became M365 shared mailboxes. Free/busy federation kept calendars working across hybrid throughout. Mail flow rules ported and validated in Exchange Online before each wave cutover.
Outcome
~600 mailboxes migrated cleanly with zero business-hours outages. FFIEC reviewer received complete migration audit documentation, no findings on the email infrastructure portion of the review. Executive mailboxes (with retention/legal-hold requirements) preserved hold continuity through the cutover.
Healthcare / HIPAA-regulated · ~120 mailboxes · Multi-clinic · Exchange 2013 (EOL) → Microsoft 365
Exchange 2013 EOL forced migration with PHI in mailboxes + signed BAA
Scope
Multi-clinic healthcare provider on Exchange 2013 — long past mainstream support. PHI present in email body, attachments, and shared clinical inboxes (referrals, lab reports, prescription approvals). Required signed BAA with Microsoft and full audit trail. Could not stay on Exchange 2013 (no Security Updates, mounting compliance risk).
Challenge
Exchange 2013 reached EOL in April 2023 — already 3+ years past expiry when engagement started. Standard cutover migration (preferred for <150 mailboxes) requires admin credentials and IMAP/Outlook access — both stable on 2013 but with known auth quirks. PHI handling required encryption-in-transit + at-rest on every transfer with verifiable integrity. Sensitivity labels needed pre-deployment so PHI auto-classified on arrival.
Fix
Pre-migration: M365 tenant configured for HIPAA — BAA signed, Microsoft Purview sensitivity labels deployed for PHI auto-classification, Conditional Access for PHI-classified content, audit log retention extended to 7 years. Cutover migration over a single weekend. SHA-256 verification on every transferred item. Sensitivity labels auto-applied during M365 ingestion. Post-migration the on-prem Exchange 2013 was decommissioned per HIPAA-compliant decommissioning checklist (data wipe, audit log, certificate revocation).
Outcome
~120 mailboxes migrated under full HIPAA controls. Compliance officer received complete audit reports. Sensitivity labels auto-applying to PHI from day one. On-prem Exchange 2013 decommissioned cleanly. Customer eliminated their largest unsupported-software compliance risk.
Manufacturing / SMB · ~85 mailboxes · Single-site Exchange 2016 · Exchange 2016 (EOL) → Microsoft 365 (cutover)
Standard SMB cutover for an org caught by Exchange 2016 end-of-life
Scope
~85-mailbox manufacturing SMB on single-server Exchange 2016. No Hybrid required (full move to cloud). Customer realized post-Oct-2025 EOL that they could not stay on 2016 without ESU enrollment. Wanted to consolidate to M365 + decommission the on-prem server.
Challenge
Exchange 2016 stopped receiving Security Updates without ESU enrollment. Customer's budget didn't justify ESU for a single year of stay-pat — wanted to migrate before next quarter's budget cycle. Standard cutover migration was right-sized (under 150 mailboxes). Public folders existed but lightly used (mostly old engineering archives).
Fix
Standard 4-phase delivery (Assess, Plan, Pilot, Cutover) condensed to 3 weeks. Public folders archived to PST and offered as a downloadable resource rather than migrated (low usage didn't justify the effort). M365 Business Standard licensing recommended (right-sized vs E3 over-spend). MX flip Friday night, weekend delta sync, Monday morning all 85 users on Outlook.
Outcome
85 users on M365 within 3 weeks of engagement start. Exchange 2016 server decommissioned. License model right-sized — customer saved ~$30/seat/month vs the E3 quote they'd gotten from another MSP. Engineering archives preserved as PST for future reference, no functional loss.
The Exchange-specific things we plan for.
Generic M365 migration guides skip these. They are the operational decisions that separate a clean Exchange cutover from a broken hybrid + orphaned public folders + lost retention holds.
Cutover vs Staged vs Hybrid — picking the right path
Cutover (under 150 mailboxes, simplest, weekend cutover). Staged (150-2000 mailboxes, Exchange 2003/2007 sources only — modern Exchange uses Hybrid instead). Hybrid (any size, allows long coexistence, required for organizations that need free/busy federation or phased executive moves). We pick during assessment based on size, source version, and coexistence requirements — not by default.
Public Folders — Modern Public Folders vs M365 Groups vs Shared Mailboxes
Public folder migration is per-folder, not all-or-nothing. Low-traffic compliance archives → M365 Groups (better search, simpler ACLs). High-volume shared inboxes → M365 shared mailboxes (better mail flow, no group sprawl). Document-heavy folders → SharePoint document libraries. We audit usage patterns first; one-size migration breaks user workflows.
Hybrid Configuration Wizard + OAuth trust
Hybrid Configuration Wizard sets up the trust between on-prem Exchange and Exchange Online: free/busy federation, cross-premises mail flow, mailbox move endpoints, OAuth for modern auth. Modern Hybrid (vs Classic) uses lighter-weight Exchange Hybrid Agent — preferred for orgs not running on-prem Exchange long-term. Classic Hybrid still required for some advanced scenarios.
Mailbox-level retention + legal hold continuity
Mailboxes under retention policy or legal hold need continuity through the cutover. We migrate the mailbox, then re-apply hold/retention from M365 Purview before any source-side cleanup. For regulated industries (banking, healthcare, legal) this isn't optional — losing hold continuity during migration creates legal exposure.
Exchange 2010/2013/2016 EOL + ESU strategy
Exchange 2010 EOL Oct 2020 (no ESU available — must migrate). Exchange 2013 EOL Apr 2023 (no ESU). Exchange 2016/2019 EOL Oct 2025 (ESU extended through Oct 2026 for enrolled customers). For customers caught past EOL we offer either: (a) emergency cutover migration to M365, or (b) ESU enrollment + phased migration plan. Decision is cost vs risk — most under-200-mailbox orgs go (a), large enterprises go (b).
Decommissioning on-prem Exchange after migration
Common mistake: organizations migrate then leave Exchange Server running for years "just in case." This is wrong — unsupported Exchange is a major attack surface (see HAFNIUM, ProxyLogon, ProxyShell historical CVEs). After the last mailbox moves we run the decommissioning checklist: remove from Hybrid configuration, uninstall in correct order (mailbox roles last), revoke certificates, document the process for compliance. Most engagements include this as part of the migration scope.
Frequently Asked Questions
How long does a typical Exchange migration take?+
Will there be downtime during the Exchange migration?+
What Exchange versions do you support?+
Do you migrate public folders?+
Can you migrate very large Exchange mailboxes (50GB, 100GB+)?+
How much does an Exchange migration cost?+
My Exchange 2016/2019 reached end-of-life — should I migrate to M365 or enroll in ESU?+
Cutover, staged, or hybrid — which migration type do we need?+
How do you handle public folders during the migration?+
Will mailboxes under retention or legal hold preserve their hold during migration?+
After migration, what happens to the on-premises Exchange Server?+
Retire Exchange. Land clean.
Hybrid Exchange, public folders, shared mailboxes — all preserved. 300+ migrations, 0 data loss. 30 days hypercare.
Microsoft Solutions Partner · Exchange-certified engineers · Fixed-fee SOW · 30 days hypercare
Migrations Hub
All 12 migration practices — platforms, pricing, timelines.
Learn More →Microsoft 365 Migration
Email, OneDrive, Teams, SharePoint — all sources.
Learn More →Tenant-to-Tenant
M&A, divestiture, rebrand — clean tenant consolidation.
Learn More →Microsoft 365 Licensing
Business, Enterprise E3/E5, right-size your seats.
Learn More →Cloud Migration Strategies & Step-by-Step Guides
Google Workspace to Microsoft 365 Migration: The Complete 2026 Playbook (Gmail, Drive, and Shared Drives)
A step-by-step migration playbook for moving from Google Workspace to Microsoft 365 covering Gmail to Exchange Online, Drive to OneDrive/SharePoint, identity migration, DNS configuration, and post-migration security — with tool comparisons and timeline estimates.
Comprehensive Guide to Successfully Performing a Cutover Migration from Exchange Server to Microsoft 365
Migration of an organization’s email system from an on-premises Exchange environment to Microsoft 365 or Office 365 is generally strategic in nature but improves collaboration, scalability, and access to cloud services. A cutover migration involves a complete and immediate switchover to the Microsoft 365 email system. This guide will provide a step-by-step process for a […]
50 Cloud Migration Statistics for 2026 — Success & Failure Rates
A comprehensive roundup of 50 cloud migration statistics for 2026 covering success rates, failure causes, migration costs, timelines, repatriation trends, and multi-cloud strategy data from Gartner, IDC, Flexera, and Forrester.
55 Cloud Computing Statistics for 2026: Spending, Migration & Adoption
55 cloud computing statistics for 2026 covering global spending ($679B), migration timelines, multi-cloud adoption, data center investment, and SMB cloud budgets with sourced data.