Which path fits: two tests before any tooling
Every Exchange Online migration EPC Group scopes begins with the same two questions. How many mailboxes are moving, and must the old and new systems behave as one organization while they move? The first question is answered by a count. The second is answered by the business: if a payroll team moves in March and the legal team in May, and the two must still see each other's calendars and share one email domain in between, coexistence is required and the path is hybrid. If the whole organization can switch over in a single window, coexistence is not required and a simpler path is available. Microsoft documents cutover, staged and hybrid for Exchange Server sources, plus IMAP and a dedicated Google Workspace path for other systems (Microsoft Learn, Decide on a migration path in Exchange Online, accessed 2026-10-20). EPC Group's Microsoft 365 consulting practice applies the two tests before any tool is installed.
Cutover, staged and hybrid: what each one actually does
- Cutover. Microsoft 365 reads the on-premises directory, creates recipients, then copies the contents of every mailbox; users receive new credentials and reconfigure Outlook afterward. Microsoft lists it for Exchange 2003, 2007, 2010 and 2013 with fewer than 2,000 mailboxes, and notes that although 2,000 is the ceiling, 150 or fewer is more reasonable given how long it takes to create and migrate that many users (Microsoft Learn, Ways to migrate multiple email accounts to Microsoft 365 or Office 365, accessed 2026-10-20). For later Exchange versions Microsoft strongly recommends the Express (minimal hybrid) option instead of cutover (Microsoft Learn, Use the Microsoft 365 and Office 365 mail migration advisor, accessed 2026-10-20).
- Staged. A one-time directory synchronization creates recipients, then batches of mailboxes move over a couple of weeks; Microsoft lists it for Exchange 2003 or 2007 with more than 2,000 mailboxes (same two sources). Staged and hybrid both require directory synchronization (Microsoft Learn, Decide on a migration path in Exchange Online, accessed 2026-10-20).
- Hybrid. The on-premises organization and Exchange Online are configured as one, and mailboxes move with remote move requests in either direction. Microsoft lists hybrid for Exchange 2010 or later with more than 2,000 mailboxes, and notes that some smaller organizations may want hybrid for its features while strongly recommending that organizations under 2,000 consider cutover or staged because of hybrid's complexity (Microsoft Learn, How and when to decommission your on-premises Exchange servers in a hybrid deployment, accessed 2026-10-20).
When a hybrid deployment is required
Hybrid is required whenever coexistence is required, and the feature list explains why. Microsoft describes a hybrid deployment as providing secure mail routing between the two organizations, mail routing with a shared SMTP domain, a unified global address list, free/busy and calendar sharing across premises, optional centralized control of inbound and outbound mail, a single Outlook on the web URL, mailbox moves to Exchange Online and back, and management from the on-premises Exchange admin center (Microsoft Learn, Exchange Server hybrid deployments, accessed 2026-10-20). The price is prerequisites: at least one on-premises Exchange server on a current cumulative update, a federation trust with the Microsoft Entra authentication system, certificates from a trusted authority, and a license for each mailbox created in or moved to Exchange Online (same source). EPC Group recommends hybrid when a move will span more than one business cycle, when regulated departments must be moved on different dates, or when some mailboxes will stay on-premises for an application dependency. Otherwise it recommends the simpler path and a single cutover weekend.
Staging mail flow and the MX record
Mail flow is the part of a migration users notice first when it goes wrong, so EPC Group stages it in three moves. Before the migration, the MX record's time-to-live is reduced; Microsoft recommends 3,600 seconds or less so that sending systems refresh the location of the mail system at least hourly (Microsoft Learn, Migrate other types of IMAP mailboxes to Microsoft 365 or Office 365, accessed 2026-10-20). During a cutover or staged migration the MX record keeps pointing at the source, and Microsoft notes that mail to already-migrated users is delivered to their on-premises mailboxes until the MX record changes (Microsoft Learn, What you need to know about a cutover email migration in Exchange Online, accessed 2026-10-20). After the final sync the MX record moves to Microsoft 365; Microsoft states it can take up to 72 hours for customers' and partners' systems to recognize the change and that the batch should not be deleted before then (Microsoft Learn, Migrate email to Exchange Online using the Exchange cutover method, accessed 2026-10-20). In hybrid, the Hybrid Configuration wizard adds a coexistence domain of the form domain.mail.onmicrosoft.com for routing between the organizations, and centralized mail transport can route all Exchange Online internet mail through on-premises servers when compliance requires it (Microsoft Learn, Exchange Server hybrid deployments, accessed 2026-10-20).
Migrating Zimbra, Google Workspace and other third-party mail
Third-party systems divide into two groups. Systems that expose IMAP, Zimbra among them, take the IMAP path: Microsoft states that IMAP migrates items in the inbox and other mail folders only, that contacts, calendar items and tasks cannot be migrated this way, and that mailboxes must be created in Microsoft 365 before the migration runs (Microsoft Learn, Ways to migrate multiple email accounts to Microsoft 365 or Office 365, accessed 2026-10-20). EPC Group therefore plans a user-side export of contacts and calendars alongside any IMAP move. Google Workspace has its own path. Microsoft states it migrates mail and rules, calendar and contacts, runs in batches so a project can be staged, requires every user to be provisioned as a mail-enabled user beforehand, and is not available for GCC High or DoD (Microsoft Learn, Perform a Google Workspace (formerly G Suite) migration to Microsoft 365 or Office 365, accessed 2026-10-20). Its documented limitations include a default 35 MB maximum message size based on tenant transport configuration, no migration of room bookings, shared calendars or event colors, a maximum of three email addresses per contact, and migrated rules arriving turned off; Microsoft also strongly recommends disabling messaging records management and archival policies before migrating so that policy-moved items are not flagged as missing (same source).
Coexistence during a multi-wave move
In a hybrid deployment, a user whose mailbox has moved and a colleague whose mailbox has not still sign in with the same credentials, use the same email domain, see one address list, share free/busy information and reach their mailbox through the same URL (Microsoft Learn, Exchange Server hybrid deployments, accessed 2026-10-20). Two details decide whether a wave feels smooth. First, permissions: explicitly granted Send As, Full Access and Send on Behalf permissions migrate, inherited ones do not, Full Access and Send on Behalf work across premises, and Send As needs additional steps (same source). EPC Group moves delegates with the mailboxes they serve for that reason. Second, devices: Microsoft notes that most Exchange ActiveSync clients reconfigure automatically after a move but some older devices might not (same source), so each wave carries a device checklist. For organizations moving between two Exchange Online tenants rather than from on-premises, EPC Group's M&A tenant migration practice applies the cross-tenant equivalent of these controls.
Documented work
ANON-CASES: EPC Group engagement data for Exchange migration covers mid-size commercial organizations moving from on-premises Exchange and from hosted third-party mail to Exchange Online, delivered by the firm's Microsoft 365 consulting practice. Client names are not published here. Engagements are described by sector and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.
Primary sources
- Ways to migrate multiple email accounts to Microsoft 365 or Office 365 — Microsoft Learn, accessed 2026-10-20
- Exchange Server hybrid deployments — Microsoft Learn, accessed 2026-10-20
- How and when to decommission your on-premises Exchange servers in a hybrid deployment — Microsoft Learn, accessed 2026-10-20
- Migrate email to Exchange Online using the Exchange cutover method — Microsoft Learn, accessed 2026-10-20
- Decide on a migration path in Exchange Online — Microsoft Learn, accessed 2026-10-20
- Use the Microsoft 365 and Office 365 mail migration advisor — Microsoft Learn, accessed 2026-10-20
Frequently Asked Questions
What is the difference between cutover, staged and hybrid migration?
Cutover moves every mailbox at once from Exchange 2003 through 2013 when there are fewer than 2,000 mailboxes, with 150 or fewer described as the reasonable number. Staged moves mailboxes in batches from Exchange 2003 or 2007 when there are more than 2,000. Hybrid integrates the on-premises organization with Exchange Online and moves mailboxes with remote move requests, which is the path Microsoft lists for Exchange 2010 or later above 2,000 mailboxes (Microsoft Learn, Ways to migrate multiple email accounts to Microsoft 365 or Office 365, accessed 2026-10-20).
When is a hybrid deployment required?
Hybrid is required when mailboxes will live in both places for a period and users need one address book, free/busy visibility, a shared SMTP domain and the ability to move mailboxes in either direction (Microsoft Learn, Exchange Server hybrid deployments, accessed 2026-10-20). Microsoft notes that hybrid carries real complexity and strongly recommends considering cutover or staged for organizations with fewer than 2,000 mailboxes (Microsoft Learn, How and when to decommission your on-premises Exchange servers in a hybrid deployment, accessed 2026-10-20).
How are mail flow and MX changes staged?
In cutover, staged and IMAP migrations the MX record stays on the source until migration is complete, then moves to Microsoft 365, and Microsoft advises waiting at least 72 hours for other systems to recognize the change before deleting the batch (Microsoft Learn, Migrate email to Exchange Online using the Exchange cutover method, accessed 2026-10-20). In hybrid, a coexistence domain of the form domain.mail.onmicrosoft.com routes mail between the two organizations, and centralized mail transport can send all internet mail through on-premises servers (Microsoft Learn, Exchange Server hybrid deployments, accessed 2026-10-20).
How are third-party systems (Zimbra, Google) migrated?
Zimbra and similar systems use the IMAP path, which copies mail folders only; contacts, calendar items and tasks do not migrate, and mailboxes must exist in Microsoft 365 first (Microsoft Learn, Ways to migrate multiple email accounts to Microsoft 365 or Office 365, accessed 2026-10-20). Google Workspace has its own path that migrates mail, rules, calendar and contacts in batches, requires users to be provisioned as mail-enabled users, and is not available for GCC High or DoD (Microsoft Learn, Perform a Google Workspace (formerly G Suite) migration to Microsoft 365 or Office 365, accessed 2026-10-20).
What does coexistence look like during a multi-wave move?
In a hybrid deployment users on both sides keep the same sign-in, the same email domain, a unified global address list, free/busy sharing and a single Outlook on the web URL, and the on-premises servers handle routing between the two organizations (Microsoft Learn, Exchange Server hybrid deployments, accessed 2026-10-20). Mailbox permissions that were explicitly granted migrate, Full Access and Send on Behalf work across premises, and Send As needs additional configuration (same source). EPC Group moves delegates and the mailboxes they serve in the same wave.
Talk to a senior architect
If your organization is weighing cutover, staged or hybrid, a 30-minute discovery call with a senior EPC Group architect will apply the two tests to your mailbox count and coexistence needs. See the Microsoft 365 consulting service hub for engagement structures.
Email contact@epcgroup.net or call 888-381-9725.
a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.
Documented engagements
Each record publishes a redacted primary-source document — a client purchase order, executed agreement or payment record — with a SHA-256 hash you can recompute, and states what the document does not establish.
- Amador County Superior Court — Delivered — payment-corroborated (client payment records published)Case study: Amador Superior Court: Exchange Online Migration (2026)
- Amador County Superior Court — ContractedCase study: Amador Superior Court: Exchange 2019 Migration (2024)
- Office of the Texas State Chemist — Contracted — countersignedCase study: Texas State Chemist: Exchange 2019 Migration (2021)