Exchange to Office 365 Migration Step by Step — 2003 to 2019, Cutover, Staged & Hybrid (2026)

Every Exchange version has a correct path to Office 365 and several wrong ones. This is the version-by-version map plus the step-by-step for each method — condensed from 500+ Exchange migrations, including the 2003 boxes still running in 2026.

Which method your Exchange version allows

Method 1 — Cutover migration, step by step (under ~150 mailboxes)

1. Verify your domain in Microsoft 365; do NOT change MX yet.
2. Enable Outlook Anywhere/EWS on Exchange, grant the migration account ApplicationImpersonation or full access.
3. Exchange admin center (M365) → Migration → Add migration batch → Cutover. Connect via Outlook Anywhere autodiscovery.
4. Start the batch — ALL mailboxes sync. Watch per-mailbox status, not just the batch summary.
5. When synced: assign licenses, flip MX/Autodiscover DNS off-hours, complete the batch (final delta).
6. Reconfigure Outlook profiles (Autodiscover does most), re-sync mobiles, then decommission properly.

Method 2 — Staged migration (2003/2007 only)

Requires directory synchronization first. Mailboxes migrate in CSV-defined batches; migrated users get forwarding from on-prem until everyone is across, then DNS flips and the org converts. Slower but the only native path off 2003 at scale. Sequence: Entra Connect → batch CSVs → migrate waves → convert mailboxes to mail-enabled users → MX flip → decommission.

Method 3 — Hybrid migration, step by step (2010+)

1. Prereqs: healthy Exchange (patched to latest CU), valid third-party certificate, Entra Connect with password hash sync or PTA.
2. Run the Hybrid Configuration Wizard (minimal hybrid for simple moves; full hybrid for long coexistence with shared free/busy).
3. Enable MRS proxy: Set-WebServicesVirtualDirectory -MRSProxyEnabled $true.
4. Create migration batches (remote move) in waves — pilot IT first, then departments. Users keep coexistence: free/busy works across both sides during the move.
5. Complete batches per wave; Outlook profiles repoint automatically via Autodiscover.
6. After the last wave: point MX at M365, tear down hybrid config, and keep recipient management per the last-server rules.

Public folders — the forgotten workload

Public folders migrate separately in every method: modern public folder migration (batch-based, 2010+ → M365 public folders) or conversion to shared mailboxes/M365 Groups — usually the better end-state. Inventory with Get-PublicFolderStatistics, decide per-folder, and do it BEFORE user cutover so permissions map while both sides exist.

When to skip native and go third-party

Third-party tools (BitTitan, CodeTwo) beat native when: the source is unhealthy (native moves need working EWS end-to-end), you need per-item reporting, 2003/2007 double-hops loom, or timeline is tight. Comparison: migration tools 2026.

FAQ

How long does an Exchange to Office 365 migration take?

Cutover under 50 users: one week including prep, cutover weekend included. Hybrid 200-500 users: 3-6 weeks in waves. Data volume and source health set the floor — throttling sets the ceiling.

Can I migrate from Exchange 2003 directly to Office 365?

Not via cutover or hybrid (no EWS). Staged migration works; otherwise third-party tools or a double-hop through 2010. In 2026, third-party is almost always the sane answer for 2003.

Do I need to keep an Exchange server after hybrid migration?

If you keep directory sync: yes for recipient management, unless you're on 2019 CU12+/SE where management-tools-only is supported. Full detail: decommission guide.