Guide
Staged migration, cutover, hybrid or IMAP: choosing the route
Updated
The route decides the effort, and the effort decides the quote. Microsoft publishes the constraints, so this is one part of the scoping conversation you can check for yourself.
Get migration quotes Two minutes of questions; up to three IT support and cloud migration providers scope your environment and quote you directly. Free, no obligation.
The routes from an on-premises Exchange Server
Microsoft documents three types of email migration from an existing Exchange Server: cutover, staged and hybrid (Microsoft Learn). Which one applies depends on your Exchange version and your mailbox count.
- Cutover migration (and Express migration)
- Everything moves at once. Microsoft's guidance applies it to Exchange 2003, 2007, 2010 and 2013 with fewer than 2,000 mailboxes, and adds that although up to 2,000 mailboxes can be moved this way, it is more reasonable to migrate 150 users or fewer because of how long creating and migrating that many users takes.
- Staged migration
- Mailboxes move in batches. Microsoft's guidance applies it to Exchange 2003 or Exchange 2007 with more than 2,000 mailboxes.
- Hybrid migration
- On-premises and online mailboxes coexist and users move gradually. Microsoft's guidance applies it to Exchange 2010 with more than 150 mailboxes and up to 2,000, to Exchange 2010 where you want small batches over time, and to Exchange 2013 or later.
What is a staged migration?
Microsoft defines it plainly: when you move mailbox contents to Microsoft 365 over time, "it's called a staged migration". It recommends one when the source is Exchange Server 2003 or 2007, or you have more than 2,000 mailboxes.
Exchange 2010 and Exchange 2013 mailboxes cannot use a staged migration; they go by cutover or hybrid. Source: Microsoft Learn, what you need to know about a staged email migration, read 2 November 2026.
- Directory sync is required. Accounts must be synchronised between the on-premises Active Directory and Microsoft 365, and the primary domain must be verified in the Microsoft 365 organisation.
- Batches of users. An administrator lists each batch in a CSV file and runs it from the Exchange admin centre; by default Exchange Online syncs 20 mailboxes at a time.
- Only mailboxes move. User and resource mailboxes migrate; distribution groups, contacts and mail-enabled users come across through directory sync, and Out of Office messages arrive blank.
- Users rebuild Outlook. After each batch, users create a new Outlook profile to connect to Microsoft 365.
In cost terms, each batch is a small cutover with its own preparation, user communication and support. A staged migration trades a single weekend for several shorter windows and a longer project.
The other routes
- IMAP migration
- Used for Gmail, Outlook.com and other IMAP-capable systems. Microsoft states that only the items in the user's inbox and other mail folders are migrated: contacts, calendar items and tasks cannot be migrated with IMAP, and it does not create the mailboxes, so each target mailbox must exist first. Mail sent to the source after the migration completes is not brought across.
- PST import service
- For organisations with many large PST files, Microsoft's Import Service uploads them over the network or by shipping a prepared drive. Often a distinct workstream with its own effort and its own line in a quote.
- Cross-tenant migration
- Moving mailboxes from one Microsoft 365 tenant to another, the merger and divestment case. See tenant-to-tenant migration.
- Working with a partner
- Microsoft's own guidance points to working with a partner where none of the standard routes fits the organisation. That is exactly the case where scoping quality matters more than headline price.
How the route shows up in the price
- Cutover concentrates effort into a short window, often a weekend, so more of the labour lands at out-of-hours rates. It is simple, and simple usually means cheaper overall for a small organisation.
- Staged and hybrid spread work across normal hours but run for longer and require coexistence to work correctly throughout. More elapsed time, more configuration, more consultancy.
- IMAP looks cheap and is, for the mail transfer itself. The cost lands in what it does not move: calendars, contacts, tasks and mailbox permissions have to be handled another way or accepted as a loss.
- PST and archive ingestion is often the single most underestimated line, because the data volume is discovered rather than known at quoting time.
Ask any prospective partner which route they intend to use and why, before comparing prices. Two quotes proposing different routes are quotes for different projects.