ShareGate Teams, OneDrive, and Mailbox Migrations: Fidelity Guide

Direct answer: Migrate Teams, OneDrive, and mailboxes through ShareGate's dedicated per-workload copy paths — never force them through a site-content operation — and validate each artifact against documented fidelity limits with owner sign-off per wave.

Vendor note (October 2026): Per-artifact coverage changes across releases. Confirm current limits in the ShareGate Migrate help collection (Copy Teams, OneDrive, mailboxes sections) before scoping.

Part of the ShareGate series: migration tutorial, incremental copy, mappings guide. Program context: tenant-to-tenant guide and Exchange migration guide.

Teams: structure first, extras verified

Inventory every Team as structure plus extras: channels, tabs, apps, Planner plans, meeting history, chats, and guest access. Move the structure through the Teams copy path, then verify each extra against current limits — channels, tabs, and Planner links commonly need partial recreation or separate handling. Recreate what the tool cannot carry, and tell owners upfront which artifacts fall in that bucket.

OneDrive: waves with owners attached

Sequence OneDrive accounts like any content wave: owner notified, change freeze at the end, counts and sharing validated per account. Watch for large personal archives, shared-with links that need business owners, and departed-user accounts that need an ownership decision before they move.

Mailboxes: compare paths before committing

Mailbox moves have their own copy behavior, Gmail sources have a separate path again, and tenant-scale Exchange programs may suit native Migration Orchestrator batches better for mail while ShareGate handles sites and Teams. Decide per workload in the plan — mixed tooling is normal — and validate item counts, folders, and coexistence mail flow per batch.

Coexistence checklist for mixed programs

When source and destination must both serve users during the move, set explicit coexistence: mail flow delivering in both tenants with a documented MX cutover moment, Teams meetings joinable on both sides until the switchover day, OneDrive sync paused or redirected per wave to avoid split edits, and a single status page owners can check instead of asking the migration team. Declare the end date of coexistence at the start — open-ended coexistence becomes permanent split-brain working.

Validation per artifact

Close each wave with artifact-specific evidence: Team membership and channel structure, OneDrive counts plus sharing samples, mailbox counts plus folder checks, Planner task sampling where in scope. Generic file-count validation does not prove a Teams migration.

Planning collaboration migration

If Teams, OneDrive, or mail scope is the hard part of your program: Book a SharePoint Migration Assessment.

Continue with ShareGate Migration Tutorial, Tenant-to-Tenant Guide, and Explore the Migration Hub.