The whole route in one page, with the exact buttons: connect, assess, match, pilot, verify, everyone, cut over. Each step links to the article that goes deeper. A small tenant can do this in a week; the source stays live until the last step.
- Connect both tenantsProject Overview → Connect source tenant, sign in as its Global Administrator, accept, and sign in once more to confirm. Then the target. Both nodes show Connected with every permission granted. → Connect a Microsoft 365 tenant / Google Workspace
- Run the assessmentAssessment tab → Run assessment. It reads both tenants (read-only), scores readiness and lists blockers and warnings with what to do — typically people without a target account, unlicensed target accounts, very large mailboxes. Fix what it flags and run it again; it is free. → Reading the assessment
- Match usersUsers tab. Most people are paired automatically; for the rest, Pair with the suggested target address, Exclude leavers, or import a two-column CSV. Shared mailboxes appear in the same list. Done when nobody is left unmatched. → Matching users
- Pilot two or three peopleMigration tab → tick a large mailbox, someone with many shared files and one shared mailbox → Migrate selected. One license per person, half per shared mailbox, used once. Rows go copying → in sync. → Migrating mailboxes, OneDrive and Drive
- Verify the pilotMigration tab → Verify: per-folder source / target / missing counts, read-only on both sides; Copy missing if anything is listed. Then open a pilot account in the target and look: folders, dates, read state, a recurring meeting, a shared file. Read Items that need a look — failures have Retry, notes explain what cannot move. → Verification and retries
- Migrate everyoneSelect the rest → Migrate selected, in waves if you like. Then the Shared & groups and Sites & Teams tabs. Large tenants take longer, not more effort: the queue honours Microsoft's throttling and never copies an item twice. → Shared mailboxes and groups, Sites and Teams
- Keep in syncDelta pass whenever you like — nightly, weekly, the morning of cutover. Only new and changed items travel, and it costs nothing.
- Cut over, one eveningCutover tab (owners): forwarding on → final delta → Teams made available → release the domain from the source → add and verify it in the target → claim the addresses → change MX / SPF / Autodiscover → send the notice → next-morning delta → sign-off report. Only the two domain steps are irreversible, and both ask you to type the domain. → Cutover
Where you are is always on the Overview.The step bar at the top of the project shows the current stage and one obvious next action, and the dashboard lists what needs you across all projects.
How long each part takes
| Step | Typical | What decides it |
|---|---|---|
| Connect + assess | 15 minutes | Consent propagation; tenant size for the assessment |
| Match users | Minutes to an hour | How many people lack a target account |
| Pilot | An hour or two | Mailbox sizes — Microsoft throttles reads per mailbox |
| Everyone | A day per few hundred people | Total data; runs in the background |
| Cutover | One evening, 1–3 hours | Mostly waiting on DNS |