How to Migrate Exchange Server to Office 365 (Cutover & Hybrid Guide 2026)

Decommissioning an on-premises Exchange Server cluster and transitioning mailboxes to Exchange Online removes the overhead of managing Database Availability Groups (DAGs), physical server maintenance, and local storage arrays.

However, planning the migration requires selecting the appropriate architecture: Cutover, Minimal Hybrid, Full Hybrid, or offline database extraction if server hardware is inaccessible.

Native Microsoft Migration Architecture Comparison

Selecting the appropriate migration method depends on mailbox counts, existing Active Directory configurations, and business coexistence requirements:

Pre-Flight Migration Checklist

Complete these preparation steps on-premises before initiating synchronization:

1. Scrub and Repair Mailboxes:

• Clean out unneeded items from Deleted Items and Junk folders to reduce synchronization time.
• Run New-MailboxRepairRequest on on-premises databases to resolve corrupted items before migration.

2. Verify Custom Domain in Microsoft 365:

• Add and verify your custom domain (company.com) inside the Microsoft 365 admin center via TXT record validation.

3. Configure Outlook Anywhere (RPC over HTTP):

• Verify that Autodiscover and Outlook Anywhere are functional externally with valid public SSL certificates signed by a trusted Certificate Authority.

4. Assign Migration Administrator Permissions:

• Create a dedicated migration account on-premises and assign it Organization Management and Receive As permissions across all target mailbox databases.

Method 1: Cutover Migration for Smaller Deployments

A Cutover migration transfers all mailboxes, contacts, and distribution groups concurrently over a scheduled maintenance period.

┌────────────────────────────────────────────────────────┐
│  EXCHANGE CUTOVER MIGRATION PIPELINE                   │
├────────────────────────────────────────────────────────┤
│  1. Test RPC Proxy: autodiscover.company.com           │
│  2. Exchange Online Endpoint: New-MigrationEndpoint    │
│  3. Initial Sync Batch: New-MigrationBatch             │
│  4. Cutover MX Records to Exchange Online Protection   │
│  5. Final Delta Sync & Decommission Batch              │
└────────────────────────────────────────────────────────┘

1. Test Outlook Anywhere Configuration

Run this PowerShell command on-premises to verify that external RPC over HTTP requests resolve cleanly:

Test-OutlookAnywhere -Server "ExchangeServer01" `
  -MailboxFetchCount 1 -TrustAnySSLCertificate:$false `
  -ClientAccessServer "autodiscover.company.com"

2. Configure the Migration Endpoint

Connect to Exchange Online PowerShell and establish the RPC endpoint:

Connect-ExchangeOnline -UserPrincipalName admin@company.onmicrosoft.com

New-MigrationEndpoint -ExchangeRPCConfig `
  -Name "OnPremisesExchangeEndpoint" `
  -EmailAddress "migrationadmin@company.com" `
  -RPCProxyServer "autodiscover.company.com" `
  -Credentials (Get-Credential)

3. Create and Start the Migration Batch

Initiate the migration batch to synchronize mailbox contents:

New-MigrationBatch -Name "ExchangeCutoverBatch" `
  -SourceEndpoint "OnPremisesExchangeEndpoint" `
  -AutoStart -NotificationEmails "admin@company.com"

# Check synchronization progress
Get-MigrationBatch -Identity "ExchangeCutoverBatch" | Select-Object Name, Status, TotalCount, SyncedCount

4. Switch DNS Records to Complete Cutover

Once all mailboxes display the Synced status:

1. Update domain MX Records to point to: company-com.mail.protection.outlook.com.
2. Update Autodiscover CNAME to: autodiscover.outlook.com.
3. Update SPF TXT record to include: include:spf.protection.outlook.com.
4. Allow 72 hours for global DNS propagation, then complete and close the migration batch.

Method 2: Minimal Hybrid Migration for Mid-Sized Organizations

For organizations with 200 to 1,000 users that require seamless desktop profile transitions without manual profile recreation:

1. Download the Microsoft Hybrid Configuration Wizard (HCW) from the Microsoft 365 admin center.
2. Select Minimal Hybrid Configuration.
3. Configure Password Hash Sync via Microsoft Entra Connect to synchronize on-premises user credentials to the cloud.
4. Execute individual or batched mailbox moves via New-MoveRequest in Exchange Online PowerShell. Mailboxes synchronize in the background while users continue working.

Method 3: Offline Database (EDB) Extraction via Prism Tools

When on-premises Exchange servers have already suffered catastrophic hardware failure, unmounted databases, or corrupt Active Directory schemas, native cutover and hybrid tools cannot connect.

In these disaster recovery scenarios, administrators extract mailboxes directly from offline .edb files:

1. Locate the offline database files (Priv1.edb) and transaction logs.
2. Launch Prism EDB Converter Tool or Prism PST Converter Tool.
3. Mount the dismounted .edb file directly without requiring an active Exchange Server or Active Directory domain controller.
4. Preview mailboxes, folders, and attachments.
5. Export recovered mailboxes into individual Unicode PST files.
6. Upload the resulting PST files to Microsoft 365 using the Microsoft Purview Network Upload service.

Technical Comparison: Migration Paths

Frequently Asked Questions (FAQs)

How long does an Exchange Server migration to Office 365 typically take?

Deployments with under 50 mailboxes can typically complete initial synchronization over a weekend. Mid-sized deployments with hundreds of mailboxes typically pre-sync data over one to three weeks before executing final MX cutover.

Will migrating to Office 365 interrupt active email users?

In a Minimal Hybrid migration, users continue accessing on-premises mailboxes while data copies to Exchange Online. Outlook prompts users to restart once their specific mailbox move finishes and points to the cloud. In a Cutover migration, users switch to cloud mailboxes after MX and autodiscover records are updated.

Can I migrate mailboxes if the on-premises Exchange server hardware is non-functional?

Yes. If the server cannot boot or Exchange services will not start, native migration tools cannot operate. However, if the database disk is intact, you can parse the raw .edb database using Prism EDB Converter Tool to extract mailboxes into PST files for upload to Microsoft 365.

Summary

Migrating from on-premises Exchange to Microsoft 365 modernizes corporate messaging infrastructure. For smaller environments under 200 mailboxes, native Cutover migration offers a direct path. Mid-sized organizations benefit from Minimal Hybrid configurations that preserve existing user profiles. When servers are offline or databases damaged, Prism EDB Converter Tool and Prism PST Converter Tool provide reliable offline recovery and staging capabilities.

Related Guides:

• How to Export Office 365 Mailboxes to PST via PowerShell
• How to Import PST to Office 365 Shared Mailbox
• How to Convert OST to PST Without Exchange