What is the difference between a staged migration and a single cutover?
The difference is how many switchover dates you have. In a single cutover, everyone moves to Google Workspace at once: one MX change, one delta pass, one first day. In a staged migration, you move people in planned batches, often by department or location, and the old and new systems run side by side until the last batch moves.
Both approaches copy the same data. What changes is the amount of coordination around it. A single cutover concentrates the effort into one short period. A staged migration spreads it out, which lowers the risk on any one day but means the project stays open longer and your team lives with two systems for a while.
When is a single cutover the right choice?
A single cutover is the right choice when your team is small enough to support on one day and works closely together. It avoids a period where colleagues are on different systems, which is where most confusion comes from. Training happens once. Mail routing changes once. Your employee communication plan points to a single date everyone can remember.
Single cutovers work well for most small businesses, professional practices, and single-office nonprofits. The bulk copy still happens ahead of time, so the switch itself stays short, and a delta migration picks up anything that changed during the switch.
When does a staged migration make sense?
A staged migration makes sense when moving everyone at once would put too much at risk. Common reasons include:
- A large team, where supporting everyone on day one would overwhelm your help desk.
- Several offices or time zones with different working hours.
- A merger or acquisition, where two organizations combine on a set timeline. Our mergers and acquisitions migrations page covers those projects.
- Departments with critical deadlines that cannot change systems during a busy period.
- A wish to prove the new setup with one real department before everyone else moves.
What does coexistence involve during a staged migration?
Coexistence means making the old and new systems work together until everyone has moved. It is the main cost of staging. While some people are in Gmail and others are still in Outlook, you need a plan for:
- Mail routing. Mail for your domain has to reach each person on whichever system they use. This usually means keeping MX records on one system and forwarding mail for moved users to the other.
- Calendars. People on different systems may not see each other's free and busy time without extra setup, and that view may still be limited.
- Groups and shared mailboxes. Membership that spans both systems needs a clear owner and a date when it moves.
- Directory. Each system should show everyone in the address book, not just the people who have already moved.
Each of these is solvable, but each adds work and testing.
How do you choose between them?
Choose based on size, risk, and how much coordination you can manage. This table summarizes the tradeoffs:
| Factor | Single cutover | Staged migration |
|---|---|---|
| Switchover dates | One | One per batch |
| Coexistence setup | Not needed | Required |
| Training | One push | Repeated per batch |
| Best fit | Small, single-site teams | Larger, multi-site, or merging teams |
| Risk on switch day | Concentrated | Spread out |
Our Standard plan uses a single weekday switchover. Our Premium plan adds staged batches and a weekend switchover. For timing, see how long a Google Workspace migration takes, and for the full process, read how to plan a Google Workspace migration.
Next step
Compare Standard and Premium on our migration plans and process page, or contact us to decide which approach fits your team.
Frequently asked questions
Can we use a pilot group with a single cutover?
Yes, and we recommend it. A few users check their migrated mail, calendars, and files in Google Workspace before everyone switches and report anything missing. A pilot is not a staged migration, because pilot users usually keep receiving mail in the old system until the main cutover.
Does a staged migration take longer overall?
Usually, yes. Each batch needs its own switchover, delta pass, and support window, and coexistence has to be set up and tested first. The tradeoff is lower risk on any single day. For many larger organizations, that tradeoff is worth the extra calendar time.
