Exchange Online Postfach-Migrationen ohne unerwartete Hindernisse

ShareGate migrates users, security groups, Microsoft 365 groups, and group memberships between cloud Microsoft 365 tenants. License assignment is included as part of the migration flow.

ShareGate doesn’t migrate device objects, workstation profiles, or on-premises Active Directory. It's purpose-built for cloud-to-cloud tenant migrations.

Entra ID should be the first thing you migrate in a tenant-to-tenant project. Identities need to exist in the destination tenant before mailbox migration can begin. If they don't, mailboxes can't map correctly and permissions won't follow.

ShareGate is built around this sequence: migrate Entra ID users and groups first, then mailboxes, then content, all with the same tool. Getting the order right is what prevents the cleanup work that happens when identity is treated as an afterthought.

The most important thing is resolving how users in the source tenant correspond to accounts in the destination before execution. ShareGate surfaces conflicts—cases where automatic matching is ambiguous or incorrect—so you can review and override them before anything moves.

For M&A scenarios with multiple source tenants or complex domain structures, manual identity mapping is available to handle cases where automatic matching isn't enough. The goal is to start the migration with every mapping confirmed, so permissions follow the way they’re supposed to and users can work on day one.

Re-running is safe and included inShareGate’sflat annual license at no extra cost.

If a user's record hasn't changed in the source tenant since the last run, they'll appear as "Match found" and receive an update. Nothing disruptive happens.

If their record changed at the source before the re-run, ShareGate re-maps them and shows the relevant status: "Will be created" if no matching record exists in the destination, or "Needs Review" if a conflicting match is found.

You stay in control throughout. And manual override is available regardless of match status, so you can correct any mapping before anything executes.

No, ShareGate's Entra ID migration covers cloud identity objects: users, groups, and security groups between Microsoft 365 tenants. It doesn’t migrate device objects, Intune enrollments, or workstation profiles—documents, favorites, and desktop settings stay out of scope.

One thing worth flagging: 'user profile migration' is an ambiguous term in the Microsoft ecosystem. Microsoft uses it to mean Entra ID directory attributes and many IT teams and partners use it to mean workstation state. If it comes up in your project planning conversations, it's worth confirming which definition everyone is working from before scoping the migration.