Exchange Server to Exchange Online: Cutover, Staged, Hybrid or Express? How to Pick the Migration Method for 25 to 500 Mailboxes

Cutover moves every mailbox, contact and distribution group in one batch over Outlook Anywhere. Microsoft's ceiling is 2,000 mailboxes; its recommendation is 150 or fewer, because creating and migrating more than that in one batch takes too long for a cutover window. It works against Exchange 2003 or later, so a 2013, 2016 or 2019 server qualifies. Nothing is synchronized from Active Directory: the migration creates the users, passwords are not carried over, and every Outlook profile is rebuilt after the switch.

Staged migration moves mailboxes in groups over time, but Microsoft supports it only from Exchange 2003 and 2007, and tells Exchange 2010 and 2013 customers to use cutover or hybrid instead. From a modern server, staged is not on the menu.

Minimal hybrid, labelled express migration in the Hybrid Configuration Wizard, is the middle path. The wizard runs a one-time synchronization of users and passwords, you move mailboxes in batches over a couple of weeks or less, and directory synchronization is then switched off. Microsoft's page names Exchange 2010, 2013 and 2016; if you run 2019 or Subscription Edition, confirm the option is offered in the current wizard before planning around it.

Full hybrid is the long coexistence model: Entra Connect keeps the directories in sync, both sides share an address book and calendar availability, mail routes between them under the same domain, and mailboxes move in any batch size, in either direction, for as long as you need. It is the only method that keeps a supported server for recipient management afterward, the subject of The Last Exchange Server.

Mailbox count sets the cutover window: the final delta pass and the Outlook rebuild are what have to fit a weekend.

• 25 to 75 mailboxes: cutover or express. The estate seeds over a few days, the final pass runs on Friday evening, and one person can walk the office through new Outlook profiles on Monday. Cutover wins when the server is fragile and nobody wants Entra Connect; express wins when passwords must carry over.
• 75 to 150: express by default. The password sync removes the largest source of Monday tickets, and batches of 25 to 50 let you move a department at a time.
• 150 to 500: full hybrid, or express only if mailboxes are small and the business accepts one cutover weekend. Above 150, departments will live on different systems for weeks, and calendar availability across both sides starts to matter.
• Over 500, a second site, a second domain, or a plan to keep a server: full hybrid.

Count mailboxes, not people: with shared and resource mailboxes, an estate of 120 users often has 180 mailboxes. Our migration estimator sizes the batch from the real inventory.

Cutover has no coexistence. Mail flows to the old server until you change MX, then to Exchange Online. The whole organization moves at once or not at all.

Express gives a short window with limited features. Mail routes between on-premises and cloud mailboxes during the batches, but minimal hybrid does not set up the cross-premises calendar availability and mailbox permissions that full hybrid does. Plan for a couple of weeks at most, and move teams that schedule together in the same batch.

Full hybrid is built for a long overlap. Calendar availability, mail tips, message tracking and same-domain routing work across both sides, so a mailbox can sit on either system for months. The price is the setup: a certificate from a public authority, Autodiscover and Exchange published to the internet, Entra Connect and the wizard's prerequisites, a week or two before the first mailbox moves.

Downtime tolerance decides between cutover and express more often than the count does. If an executive assistant cannot lose calendar delegation for a weekend, express or hybrid keeps it, because the mailbox moves intact with its permissions.

Outlook profiles. After a cutover, Autodiscover connects Outlook to the new mailbox only when the user creates a new profile, and every desktop downloads its mailbox again in cached mode; stagger the rebuilds on a modest link. After a hybrid move, the on-premises mailbox becomes a remote mailbox with a target address, Outlook picks up the change through Autodiscover and, after a restart, connects with the same profile.

Passwords. Cutover does not migrate them; the migration statistics report contains an auto-generated temporary password per mailbox, reset at first sign-in. Express and full hybrid synchronize password hashes, so users keep what they have.

Mobile devices. Cutover means every phone gets a new account; hybrid moves usually keep the existing account working.

Public folders. No method moves them with the mailboxes. Microsoft's public folder migration is a separate batch, run after the user mailboxes, in a single batch for the whole hierarchy, with a limit on public folder mailboxes and guidance to break up any folder over 25 GB first. For a small estate we often convert instead: calendars and contacts into shared mailboxes, documents into SharePoint, discussions into Microsoft 365 Groups. Decide before the mailbox migration, because it changes what needs to move.

Everything else. Distribution groups and contacts come across in a cutover batch; security groups and system mailboxes do not. Anything calling Exchange Online over EWS must be allow-listed before the block that starts on 1 October 2026, covered in Exchange Server SE and the EWS block.

Cutover, 25 to 150 mailboxes: a week of preparation, three to five days of seeding, one weekend for the final pass, the MX change and the profile rebuilds. Our Cutover Exchange Online Migration from your own Exchange Server is scoped at one week.

Express, 50 to 300 mailboxes: a week for the wizard and the one-time sync, then one to two weeks of batches.

Full hybrid, any count: one to two weeks to build, then batches at the pace the business sets. Our Hybrid Microsoft 365 Migration from your own Exchange Server is scoped at two weeks for the build and the first wave.

What you prepare, whichever method:

1. Domains verified in the tenant and licenses assigned before the batch; a user with no license has no mailbox to land in.
2. A certificate from a public authority on Outlook Anywhere and Autodiscover; self-signed certificates fail the endpoint test.
3. A mailbox report: size, item count, last logon and largest item.
4. An inventory of everything that sends mail through the server: printers, scanners, applications, backup jobs.
5. The public folder decision.
6. For hybrid: Entra Connect healthy, user principal names matching primary SMTP addresses, and a plan for the server that remains.

Every migrated mailbox needs a license from the day the batch completes. Microsoft list price, September 2026 price list, annual commitment: Exchange Online (Plan 1) is $48.00 per user per year ($4.00 per month); Exchange Online (Plan 2), with the larger mailbox, archiving and litigation hold, $96.00 ($8.00 per month); Microsoft 365 Business Basic, adding Teams, SharePoint and OneDrive, $84.00 ($7.00 per month); Business Standard with the desktop apps, $168.00 ($14.00 per month); Business Premium with Intune, Defender for Business and Entra ID P1, $264.00 ($22.00 per month). Exchange Online Plan 1 vs Plan 2 vs Kiosk vs Business Basic covers the mailbox-only choices and when shared mailboxes need no license. We sell all of them at Microsoft's list price. A server kept only for hybrid recipient management may qualify for Microsoft's hybrid server license; the last-server article covers the eligibility wording.

Can I do a cutover migration from Exchange 2016 or 2019?

Yes. Microsoft's requirement is Exchange 2003 or later with Outlook Anywhere reachable on a certificate from a trusted authority; it is enabled by default on 2013, 2016 and 2019. The ceiling is 2,000 mailboxes, the recommendation 150 or fewer.

Do users have to recreate Outlook profiles after an Exchange to Office 365 migration?

After a cutover, yes, and the mailbox downloads again. After an express or full hybrid move, the existing profile follows the mailbox through Autodiscover after a restart.

How long does an Exchange Server to Exchange Online migration take?

Cutover for up to about 150 mailboxes: one to two weeks including a weekend switch. Express: two to three weeks. Full hybrid: one to two weeks to build, then batches.

Does Microsoft pay for an Exchange to Exchange Online migration?

Sometimes. Our cutover, express and hybrid migrations from your own server are Microsoft-sponsored for eligible customers, subject to Microsoft's eligibility rules; Microsoft-Funded Migration: What to Check Before You Buy explains them. Licenses and anything Microsoft meters are always yours.

• Microsoft Learn: the cutover migration and migration path pages (2,000 maximum, 150 recommended, Exchange 2003 or later, new Outlook profile, groups and contacts migrated, temporary passwords in the statistics report); the staged migration page (Exchange 2003 and 2007 only); the minimal hybrid page (a couple of weeks or less, one-time sync, Exchange 2010, 2013 and 2016 named); hybrid mailbox moves (Outlook follows the mailbox through Autodiscover); public folder batch migration (users first, single batch, 100 public folder mailboxes, 25 GB guidance). Not opened from this environment; as reported by office365concepts.com, infrasos.com, dzone.com, medhacloud.com and search excerpts on 27 September 2026; verify on Microsoft Learn.
• IT Partner blog articles linked above: Exchange Server SE and the EWS block (support end 14 October 2025, block from 1 October 2026), the last Exchange server, mailbox-only licensing, funded migration eligibility
• IT Partner price sheet, Commercial segment, September 2026 US price list; IT Partner service pages and engineering notes, September 2026