We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

Cutover vs Staged Migration: Choosing the Method for Each Mailbox

For IT heads moving Exchange mailboxes to Microsoft 365, this article puts cutover and staged side by side in one table: source versions, mailbox count, how long both systems run, what users notice, calendars and contacts, and the rollback point. It adds a rule for each mailbox group and a short note on when a hybrid setup or IMAP fits instead. No tools and no figures beyond Microsoft's own.

Cutover vs staged migration is the choice between moving every mailbox in one batch and moving them in batches over time. The choice turns on the Exchange version you run and the number of mailboxes.


Last reviewed 2026-11-16 by Manish Sharma.

An IT head decides this per mailbox group, not once for the firm, as a head office on Exchange 2007 and a branch on Exchange 2013 may not share a route. The way Signisys runs a full mail and file move starts from this choice, and the sections below give the rules for it.

Cutover vs Staged Migration Compared in One Table

The two methods differ on six points, set out here with the wording Microsoft Learn uses.

Point Cutover Staged
Source versions Exchange 2003, 2007, 2010 and 2013; confirm your version on the current Learn page Exchange 2003 or 2007 only, both out of support
Mailbox count Up to 2,000; 150 or fewer is more practical Suited to more than 2,000 mailboxes
How long both systems run Over a weekend or a few days Slowly, a few users at a time
What users notice All users move together; mail reaches the old server until the MX record change Each batch gets a new Outlook profile; mail to the old mailbox is forwarded
Calendars and contacts Carried over with the mail Carried over with the mail; Out of Office message is blank after the move
Rollback point Until the batch is deleted Per batch

Advantages
Cutover suits a firm that wants one move and one end date.


Limitations
Staged takes Exchange 2003 or 2007 only, and needs directory synchronization running.

Read the table down a method, then across to the other, before choosing.

Cutover and staged side by side: one batch for up to 2,000 mailboxes versus batches over time for more than 2,000
Two methods, compared on source version and count.

How Cutover vs Staged Migration Move Mailboxes

Both methods copy mail to Exchange Online; they differ in how many mailboxes move at once and what runs beside them.

Cutover: Every Mailbox in One Batch

An Exchange cutover migration moves all mailboxes in a single batch. Switch directory synchronization off before it starts. Microsoft’s page on the Exchange cutover method says to turn it off before you begin.

Mail keeps reaching the old server until you change the MX record to point at Microsoft 365. After that change, new mail goes to Exchange Online, so the order of steps matters more than speed.

Cutover suits a firm that wants one move and one end date. However, it asks for a short, planned window instead of a long period of two systems side by side.

Plan the Window

A cutover needs a short planned window. Fix the weekend before the first mailbox moves.

Staged Batches While Both Systems Run

A staged move works in batches, so some users are on Exchange Online while the rest stay on the old server. A staged move requires directory synchronization from Active Directory. The Microsoft Learn page on staged email migration states this.

A CSV file lists each batch, with one row per user. While a batch moves, the old mailbox forwards mail to the matching Exchange Online mailbox. Mail sent to the old address therefore still reaches the user.

Teams searching for a staged migration office 365 route will find that source version limits the method. The next section covers that.

Cutover vs Staged Migration by Source Version and Mailbox Count

Version and count settle the question for many groups before anything else comes into play. The readiness list to clear before any batch starts covers what must be in place first, and this section covers which method then fits.

Exchange Versions Each Method Accepts

The Microsoft Learn overview of ways to migrate multiple email accounts lists the cutover sources as Exchange 2003, 2007, 2010 and 2013. Confirm your version on the current Learn page, as the list can change, and make no assumption about newer releases.

Staged accepts Exchange 2003 or 2007 only. Both are out of support, so a firm still on them is also facing a platform retirement, not only a mailbox move.

Check Your Version

Confirm your Exchange version on the current Learn page. The lists can change, and no assumption applies to newer releases.

If your version is on neither list, the route is hybrid or IMAP, covered below.

The 2,000 Ceiling and the 150 Advice

Cutover has a maximum of 2,000 mailboxes. The same Learn overview adds that 150 or fewer is more reasonable, because of the time it takes to create and migrate that many users in one batch.

Above 150, Microsoft’s decision page points Exchange 2003 and 2007 firms to staged, and newer versions to hybrid. Count mailboxes per site or business unit, not for the whole company, as a group can move on its own.

What Users Notice in a Cutover vs Staged Migration

Users notice three things. They set up Outlook again, they see where mail arrives on the first day, and they redo a few settings.

New Outlook Profiles and Day One Mail

After a staged move, users must create a new Microsoft 365 profile in Outlook. Tell each batch before its move date. Then the profile step is not a surprise.

Where mail arrives on day one depends on the MX record. Until it changes, mail still reaches the old server. In a staged move, forwarding sends mail on to the Exchange Online mailbox in the meantime.

Calendars, Contacts, Groups and Out of Office

Both methods carry calendars and contacts with the mail. Also, groups follow the batch in a cutover and directory synchronization in a staged move.

After a staged move, the Out of Office setting stays on but the message is blank, and users write it again. Add a reminder to the user note for each batch.

Key Takeaway Both methods carry calendars and contacts, and only a staged move leaves a blank Out of Office message.

Rollback Points in a Cutover vs Staged Migration

The rollback point is the moment the old mailboxes stop being a fallback. For cutover, the old server still has the mail until the batch is deleted. After deletion, the service does not copy mail sent to the old server, so a late rollback loses new messages.

Microsoft Learn sets a minimum of 72 hours between the MX change and the batch deletion. Use that gap to check that mail flows, that calendars show correctly and that no user still reaches the old server.

Rollback Point

For cutover, the rollback point is the day the batch is deleted. For staged, it is per batch.

A staged move keeps each old mailbox until the administrator checks the batch and converts those mailboxes to mail-enabled users, so the fallback ends per batch. A batch with a problem can wait while the others carry on. What goes wrong when a move ends too early lists the signs of closing the old system before this review ends.

When Neither Fits: Hybrid or IMAP

Hybrid is the route for Exchange 2013 or later where mailboxes are many, or where both systems must coexist for a long time. Microsoft describes hybrid as keeping on-premises and online mailboxes side by side while users move gradually. It needs its own plan, but this article does not cover how to build one.

IMAP is the route for Exchange 2000 or earlier, or for another mail platform. It moves mail folders only. Calendars and contacts need another route, and each mailbox must exist in Microsoft 365 first.

Matching Each Mailbox Group to Cutover vs Staged Migration

Write the rule for each mailbox group as a series of questions, in this order.

  1. Which Exchange version does the group run? Check the Learn list for cutover and staged.
  2. How many mailboxes are in it? Up to 150 suits cutover; above that, staged for Exchange 2003 and 2007, and hybrid for newer.
  3. How long may both systems run? A weekend or a few days points to cutover; a few users at a time points to staged.
  4. How soon must the old server be safe to retire? A need to go back per batch points to staged.

Key Takeaway Let the Exchange version answer come before the count, and decide per mailbox group.

Signisys’s working view is to decide per mailbox group, not once for the firm, and to let the version answer come before the count. A firm with one site on Exchange 2007 and another on Exchange 2013 may well end with two methods. The run order for carrying out either method takes over once you make the choice.

Cutover vs staged migration by mailbox group: version first, then count, then how long both systems run, then rollback
Ask the four questions per mailbox group.

Signisys provides end user computing and device services and a workplace and device solution, and is also a Microsoft partner. In a working session, we sort your mailbox groups by version, count and how long both systems may run. The output is a sorted list, not a plan to sign. No charge, with a fixed scope.

Book a consultation
Choose the method with us

Cutover vs Staged Migration: FAQ

Does directory synchronization rule one method out?

It rules one in and one out. Cutover needs directory synchronization switched off, and staged needs it running from Active Directory. A firm that already runs it for other reasons points toward staged or hybrid, as the two Learn pages state.

Is staged still an option on Exchange 2010 or 2013?

No. Microsoft Learn says a staged migration does not support Exchange 2010 or 2013 mailboxes. Those firms use cutover or hybrid instead. Confirm your version on the current Learn page, as Microsoft updates the lists from time to time.

Should a firm with 100 mailboxes on Exchange 2007 pick cutover or staged?

Either fits under the 150 advice, so the deciding input is how long both systems may run. Cutover finishes over a weekend or a few days. Staged moves a few users at a time, so a firm that wants a calm pace picks staged.

What happens to Out of Office replies after a staged move?

The Out of Office setting stays on, but the message is blank, and users write it again. Ask each batch to set the text on day one. Then senders still get a reply while a user is away.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.