Exchange Hybrid Mailbox Migration: Step-by-Step Guide with Minimal Downtime

by

Step-by-step Exchange hybrid mailbox migration guide covering prerequisites, remote move batches, large mailboxes, and third-party tools.

Exchange hybrid mailbox migration allows administrators to move mailboxes from on-premises Exchange to Exchange Online with minimal downtime by synchronizing data in the background and completing the final switch in minutes.

Migrating user mailboxes in an Exchange hybrid environment (on-premises Exchange + Exchange Online) can feel risky if not planned properly. The good news is that Microsoft’s remote move migration process is designed to move mailboxes with near-zero downtime, no mail flow disruption, and minimal user impact—when done correctly.

This guide covers prerequisites, step-by-step hybrid mailbox migration, large mailbox handling, and post-migration validation, using proven best practices from real production environments.

What Is an Exchange Hybrid Mailbox Migration?

In an Exchange hybrid deployment, mailboxes are moved using the Mailbox Replication Service (MRS). Mailbox data synchronizes in the background while users continue to work on their on-premises mailbox. Only the final switch requires a short interruption.

Key advantages:

  • Minimal downtime
  • No mail flow disruption
  • Unified Global Address List (GAL)
  • Seamless free/busy and delegation

Recommended Migration Strategy (Minimal Downtime)

The recommended and most stable approach is to use migration batches with “Manually Complete Later” enabled.

How it works:

  • Around 95% of mailbox data syncs in the background
  • Incremental sync runs every 24 hours
  • Completion takes 5–10 minutes
  • Outlook briefly disconnects and reconnects
  • Users can continue working during sync

Schedule finalization during off-hours to avoid user impact.

Prerequisites for Exchange Hybrid Mailbox Migration

Before initiating any mailbox move, confirm the following:

1. Hybrid Configuration Wizard (HCW)

Your environment must have a fully configured hybrid setup, created using the Hybrid Configuration Wizard.
This enables secure connectivity, OAuth authentication, free/busy sharing, and hybrid mail routing.

2. Microsoft Entra Connect (Azure AD Connect)

  • Users must be synced from on-prem AD
  • UPN and proxyAddresses must match
  • Shared mailboxes must exist as mail-enabled users

3. MRSProxy Enabled

Ensure MRSProxy is enabled on all on-prem Exchange servers:

Get-WebServicesVirtualDirectory | fl MRSProxyEnabled

4. Permissions

The migration account must have:

  • Organization Management (on-prem)
  • Exchange Administrator (Exchange Online)

5. Network and Firewall

Allow outbound HTTPS (TCP 443) to Microsoft 365 endpoints.
Validate connectivity using Microsoft Remote Connectivity Analyzer.

6. Licensing

Microsoft 365 licenses can be assigned after migration completion (within 30 days).

How to Initiate Remote Move Migrations

Using Exchange Admin Center (EAC)

  1. Go to Exchange Admin Center -> Recipients -> Migration
  2. Select Migrate to Exchange Online
  3. Choose Remote move migration
  4. Add users or upload a CSV
  5. Select or create a migration endpoint
  6. Choose, and manually complete the batch
  7. Start the batch and monitor progress

Recommended batch size: 50-100 mailboxes.

Using PowerShell (Preferred for Large Environments)

New-MigrationBatch `
-Name "HybridBatch01" `
-SourceEndpoint HybridEndpoint `
-CSVData (Get-Content users.csv -Encoding Byte) `
-TargetDeliveryDomain tenant.mail.onmicrosoft.com `
-AutoComplete $false

Monitor:

Get-MigrationBatch
Get-MigrationUserStatistics -IncludeReport

Finalize:

Complete-MigrationBatch -Identity HybridBatch01

Handling Large Mailboxes in Hybrid Migrations

Large mailboxes are the most common reason for slow or failed migrations.

Exchange Online Limits

  • Primary mailbox: 100 GB
  • Archive: Unlimited (auto-expanding archive)

Best Practices

  • Enable auto-expanding archives
  • Move older items using retention policies
  • Reduce primary mailbox size below 100 GB
  • Migrate during off-peak hours
  • Monitor MRS performance closely

Mail Flow During Hybrid Migration

Mail flow is handled automatically:

  • During sync, mail is delivered to the on-prem mailbox
  • After completion, targetAddress updates automatically
  • Inbound and outbound mail routing continues seamlessly
  • No transport rule changes required

Ensuring Outlook, Mobile, and Delegated Access

Outlook

  • Autodiscover updates automatically
  • Outlook reconnects post-move
  • A restart may be required once
  • Hybrid Modern Authentication improves reliability

Mobile Devices

  • Autodiscover redirects to Exchange Online
  • Users may need to reauthenticate

Delegated Access

  • Permissions sync automatically
  • Best practice: migrate managers and delegates together
  • Verify permissions after the move

Third-Party Exchange Migration Tools

While Microsoft native hybrid migrations are the recommended approach, there are scenarios where third-party Exchange migration tools make sense—especially for complex or edge-case environments.

Common Use Cases

  • Very large mailboxes (hundreds of GBs)
  • Corrupt mailboxes or failed MRS moves
  • Cross-forest or non-hybrid migrations
  • Selective mailbox or item-level migrations
  • Tight timelines requiring parallel moves

Popular Tools

Stellar Migrator for Exchange

Stellar Exchange Migration tools are commonly used for:

  • Seamlessly migrates mailboxes across Exchange Servers and Microsoft 365, supports same and cross-domain without the need to run complex PowerShell scripts. 
  • Migrating large or problematic mailboxes
  • Extracting mailboxes from EDB files
  • Granular mailbox and item-level migration
  • Scenarios where native MRS moves repeatedly fail

Best suited for recovery-driven or complex migrations rather than standard hybrid moves.

SysTools Exchange Migration

SysTools Exchange Migration is often used for:

  • On-prem Exchange to Microsoft 365 migrations
  • Batch migrations with detailed reporting
  • Selective mailbox and folder migration
  • Environments without a full hybrid configuration

Final Thoughts

A properly planned Exchange hybrid mailbox migration can be completed with minimal downtime, no mail flow disruption, and almost zero user complaints.

The keys to success are:

  • Solid hybrid prerequisites
  • Controlled migration batches
  • Manual completion scheduling
  • Smart handling of large mailboxes
  • Using third-party tools only when necessary

When done right, Exchange hybrid migrations are predictable, stable, and scalable-even in large enterprise environments.

Leave a Comment