← Back to blog

25 to 50 Mailbox Pilot: MSP Proven Exchange Hybrid Migration

September 14, 2026
25 to 50 Mailbox Pilot: MSP Proven Exchange Hybrid Migration

Most organizations with an on-premises Exchange server should run a hybrid migration rather than a full cloud cutover, especially if mailboxes need to move in batches over weeks or months. Use minimal hybrid for a fast, one-time migration to Office 365 with no long-term coexistence; use full hybrid when you need staged moves, cross-premises permissions, or delegated access during the transition. Either path requires directory sync and a supported Exchange cumulative update before you touch the Hybrid Configuration Wizard.


TL;DR:

  • Use minimal hybrid for quick, one-time migrations if you have fewer than 150 mailboxes and no ongoing coexistence needs.
  • Ensure all prerequisites, including supported Exchange CU, directory sync, and correct firewall and certificate configurations, are verified before starting.
  • Hybrid setup requires manual configuration for inbound mail routing, with Microsoft recommending pointing MX directly to Microsoft 365 for most organizations.
  • Mailbox moves depend on proper setup of MRSProxy, a tested migration endpoint, and performing pilot batches to identify issues early.
  • Managed service providers can handle complex hybrid migrations, especially for organizations with strict compliance needs, reducing operational risk.

Securetechie
securetechie.com
Plan Your Exchange Migration
Secure Techies provides managed IT, Microsoft 365 email migration, proactive management, and cybersecurity for growing businesses.
Explore Secure Techies

Table of Contents

What Are the Prerequisites for Exchange Hybrid Migration?

Skipping prerequisite checks is the fastest way to turn a weekend migration into a two week outage. Before opening the Hybrid Configuration Wizard (HCW), confirm the environment actually qualifies.

  • Run a supported Exchange version with the latest Cumulative Update or Update Rollup installed. Exchange 2016 and newer need at least one on-premises Mailbox server role.
  • Deploy Microsoft Entra Connect (or Cloud Sync) and decide your sync cadence and writeback settings before HCW runs, not after.
  • Verify that whoever runs HCW holds Global Administrator rights in Microsoft 365 and Organization Management in Exchange, since the wizard creates connectors on both sides.
  • Confirm Autodiscover and MX records resolve correctly, and check that your certificate's Subject Alternative Names (SANs) cover the FQDNs used for EWS and Autodiscover.
  • Open outbound ports for hybrid transport and whitelist Microsoft 365 migration endpoints in your firewall and intrusion detection system, so legitimate mail flow and mailbox move traffic don't get flagged.

Pro Tip: Patch Exchange to the current CU before scheduling anything with end users. A hybrid deployment built on an outdated CU is a common reason HCW fails halfway through, and rerunning it after a mid-project patch cycle costs more time than doing it right the first time.

Should You Use Minimal Hybrid or Full Hybrid?

The decision comes down to timeline and how long you need on-premises and cloud mailboxes to coexist. Minimal hybrid, sometimes called express migration, performs a one-time directory sync and moves everyone to the cloud in a short window without maintaining long-term dir sync afterward. It works well for Exchange 2010, 2013, and 2016 environments where the goal is simply to get to Office 365 migration completed, not to run mixed on-prem and cloud mailboxes for months.

Full hybrid is the right call when you need staged mailbox moves, delegated permissions across premises, or the ability to move mailboxes back on-premises later. It also keeps directory sync running indefinitely, which matters for organizations with compliance obligations tied to identity governance.

  • Choose minimal hybrid if: you have a small mailbox count, a short migration window, and no plan for ongoing coexistence.
  • Choose full hybrid if: you need phased batches, shared calendars and free/busy across environments during the transition, or a hybrid exchange setup that could persist for years.

Pro Tip: If your organization is under 150 mailboxes and has no compliance driver for keeping an on-premises presence, minimal hybrid usually gets you to Office 365 with far less configuration overhead than full hybrid.

How Does the Hybrid Configuration Wizard Set Up Mail Flow?

HCW does most of the heavy lifting, but it doesn't do everything, and knowing the gap matters more than knowing the wizard's screen flow.

  1. HCW creates a HybridConfiguration Active Directory object, builds the send and receive connectors between your Exchange server and Exchange Online, and may provision a dedicated hybrid app registration in Microsoft Entra ID for OAuth authentication.
  2. It establishes a coexistence domain and configures secure mail flow, using TLS-encrypted transport between the on-premises organization and Exchange Online.
  3. It does not automatically repoint your MX record, tune anti-spam policies, or decide your inbound routing strategy. Those remain manual decisions.

For inbound mail, you have three routing choices, but Microsoft recommends pointing MX directly at Microsoft 365 for most hybrid organizations, since it lets cloud-based filtering protect mailboxes that have already moved without extra hops through on-premises servers.

Centralized Mail Transport (CMT) routes Exchange Online outbound mail back through your on-premises servers. Microsoft advises against enabling CMT unless you have a documented compliance requirement, because it adds latency and keeps you dependent on infrastructure you're otherwise trying to retire. Once hybrid transport is configured, cross-premises mail is treated as internal mail, which changes how transport rules, journaling, and anti-spam scanning apply, so review those policies before cutover, not after.

What Is the Mailbox Move Process in a Hybrid Deployment?

Moving mailboxes is where most of the operational risk lives, and getting the sequence right avoids the majority of failed batches.

  1. Enable and verify MRSProxy on your on-premises EWS virtual directory. This is the service that actually shuttles mailbox content between Exchange and Exchange Online, and IIS handler mappings need to be correct or the moves will fail silently.
  2. Create a migration endpoint in Exchange Online and test it against your Autodiscover and coexistence domain before scheduling any real batches.
  3. Initiate remote move migrations from the Exchange admin center (EAC) in Exchange Online, or use PowerShell for more control: New-MoveRequest -Identity "user@domain.com" -Remote -RemoteHostName "mail.domain.com" -TargetDeliveryDomain "domain.mail.onmicrosoft.com".
  4. Run a pilot batch of a handful of mailboxes first, verify mail flow and calendar behavior, then scale to full production batches.

A few operational habits make the difference between a smooth rollout and a support queue full of tickets:

  • Batch by department or office location rather than alphabetically, so you can isolate issues to a specific team if something goes wrong.
  • Budget migration time based on mailbox size and network throughput, not headcount alone; a handful of 50 GB mailboxes can take longer than fifty small ones.
  • After each batch completes, remove the finished move requests, confirm the target delivery domain resolved correctly, and update DNS only when you're ready for full cutover.

How Do You Troubleshoot a Failed Exchange Hybrid Migration?

Initiating move requests from Exchange Online usually produces clearer, more specific error messages than starting from the on-premises console, and it tends to handle mailbox GUID matching more reliably. Start troubleshooting there.

  • Check whether MRSProxyEnabled is actually set to true on the EWS virtual directory. It's a surprisingly common oversight.
  • Review WSSecurityAuthentication settings and IIS handler mappings. Administrators often overlook a misconfigured handler mapping that silently blocks EWS traffic, which looks like a network problem but isn't.
  • Confirm your firewall or intrusion detection system isn't misclassifying migration traffic as suspicious and dropping it.
  • Remove stale or stuck move requests before retrying. PowerShell (Get-MoveRequest | Get-MoveRequestStatistics) gives more actionable detail than the EAC.

Pro Tip: Run a test move with a single disposable mailbox before every new batch type (different OU, different mailbox size tier, different office). It surfaces configuration drift before it affects real users.

Once a batch completes, verify mail flow both directions, confirm Autodiscover redirects properly, test Free/Busy lookups between cloud and on-premises calendars, check that delegated permissions carried over, and have at least one migrated user sign into Outlook and mobile mail to confirm client connectivity.

Hybrid migration verification paths

How Do Mailbox Permissions and Directory Sync Work in Hybrid?

Cross-premises permissions don't always survive a mailbox move the way admins expect. Explicit Full Access, Send As, and Send on Behalf permissions generally migrate with the mailbox, but inherited permissions and permissions tied to non-mail-enabled objects typically don't carry over automatically.

  • Send As across premises sometimes needs extra manual configuration, and behavior varies depending on your Exchange version, so test it on a pilot mailbox rather than assuming it works.
  • Global Address List (GAL) visibility depends on your Microsoft Entra Connect sync cadence. If a new hire shows up in the cloud but not on-premises (or vice versa), check the sync schedule before assuming a configuration error.
  • Coexistence domains created during hybrid setup need to stay synchronized; missing or misconfigured proxy addresses are a frequent, underappreciated cause of Autodiscover and routing failures during coexistence.
  • If you ever need to move a mailbox back on-premises for offboarding or a reversal, plan for the same permission gaps in reverse, and document delegated access before you start.

What Certificate and Network Settings Does Hybrid Require?

Certificate and connectivity issues cause a disproportionate share of failed HCW runs, and they're almost entirely preventable with a short checklist.

  • Certificates used for EWS and Autodiscover need the correct FQDNs listed in the SAN field. Forced TLS between Exchange and Exchange Online fails outright if the FQDN doesn't match.
  • Confirm the specific ports and endpoints Microsoft documents for hybrid transport and migration are open, and add them to your firewall and IDS allow lists.
  • Avoid placing any device that modifies SMTP traffic between your Exchange server and Exchange Online. If you need an internet-facing buffer, use an Edge Transport server instead, which requires EdgeSync configuration but keeps domain-joined servers off the public internet.
  • Run the Microsoft Remote Connectivity Analyzer and confirm MRSProxy responds correctly from an external endpoint before you run HCW or schedule your first batch.

Multi-factor authentication for admin and end-user accounts is also worth locking down before migration starts, since hybrid setups often widen the number of authentication endpoints in play; a resource like this MFA overview is a useful reference when planning identity settings alongside Entra Connect.

What Does a Pilot-and-Cutover Playbook Look Like?

A structured pilot beats a big-bang cutover almost every time. Secure Techies typically runs pilots with a moderate number of mailboxes, large enough to surface real-world issues across different mailbox sizes and device types, small enough that a bad batch doesn't take down half the company.

  • Select pilot users across departments and device types (desktop Outlook, mobile, shared mailboxes) rather than just IT staff, who tend to tolerate rough edges that regular users won't.
  • Define success criteria up front: mail flow both directions, calendar and Free/Busy accuracy, and confirmed client sign-in before declaring the pilot complete.
  • Document a rollback plan and identify who gets looped in if a batch fails midway, before you start, not during the incident.
  • Templates from Secure Techies' tenant migration cutover playbook and its Microsoft 365 migration case study are worth reviewing before you build your own runbook.

MSP priorities: what actually matters in hybrid migration

Test mail flow and Autodiscover before you touch mailboxes, not after. Skip Centralized Mail Transport unless compliance genuinely demands it. Minimal hybrid wins on speed; full hybrid wins on control. Document every directory sync and permissions decision, since nobody remembers the reasoning six months later.

— Alex

How Secure Techies Handles Your Hybrid Migration

Running a hybrid migration in-house works fine for teams with dedicated Exchange experience and time to spare for pilot testing, batch monitoring, and the inevitable certificate or Autodiscover fire drill. Most IT teams don't have that time to spare on top of daily ticket volume.

Securetechie

A managed service provider can manage the entire hybrid exchange setup process for businesses. That includes pilot planning with the 25 to 50 user methodology, running the Hybrid Configuration Wizard, executing mailbox moves in coordinated batches, and validating mail flow, calendar sharing, and client connectivity before declaring the project done. If an organization runs healthcare, financial, or legal workloads where HIPAA or compliance requirements shape how mail routing and permissions get configured, having a specialized team handle those audits removes a layer of guesswork most in-house admins don't need to carry alone. Visit the managed infrastructure services page to scope your migration and get a project timeline built around your mailbox count and compliance requirements.

FAQ

Do I still need an Exchange hybrid server?

Not permanently in every case. Minimal hybrid supports a one-time migration without maintaining a long-term on-premises server, while full hybrid keeps at least one Exchange server role active for ongoing coexistence and directory sync.

How do I perform a hybrid migration from Exchange to Office 365?

Verify prerequisites (supported CU, Entra Connect, certificates), run the Hybrid Configuration Wizard to establish connectors and the coexistence domain, then move mailboxes in batches using the Exchange Online EAC or PowerShell's New-MoveRequest. Test mail flow and client connectivity after each batch before scaling to the next.

What are the different types of Exchange migrations?

The main options are cutover migration (all mailboxes at once, small organizations), staged migration, minimal or express hybrid (fast, one-time sync), and full hybrid (staged, long-term coexistence with delegated permissions). Full hybrid is generally recommended for organizations needing extended coexistence or compliance-driven identity control.

Should I enable Centralized Mail Transport during hybrid migration?

Only if you have a documented compliance requirement. Microsoft advises against it otherwise, since CMT adds latency and keeps outbound cloud mail dependent on on-premises infrastructure.

How many mailboxes should a hybrid migration pilot include?

A pilot batch of 25 to 50 mailboxes across different departments and device types typically surfaces most configuration issues before they affect the full organization.