O365 Migration: what Teams & Groups migration copies
Groups, teams, channels, conversations, members and files – and what Microsoft Graph doesn't allow to migrate.
Migrated
| Item | Details |
|---|---|
| Microsoft 365 group | Display name, mail nickname, description, privacy (or the privacy you choose) |
| Owners and members | Through the user mapping |
| Team and standard channels | Including the General channel; names and descriptions |
| Conversations | Posts and replies in standard channels, with their original authors and dates, subjects and importance. @mentions become bold names |
| Private channels | Created with their owners and members, and their files |
| Files | The group's document library, including every channel's folder, with created and modified dates. Large files are copied in parts |
Not migrated
- Shared channels: they belong to the host team, so create them again. They are listed in the report.
- Private channel conversations: Microsoft only supports importing into standard channels.
- Images pasted into messages: replaced by a note. Files attached to messages are copied with the channel's files, and the message names them.
- Tabs and apps, Planner plans, meeting recordings, wikis, and 1:1 or group chats.
Conversations need a new team
Microsoft Graph only accepts imported messages with their original dates while a team is being created in migration mode. So conversations are imported when O365 Migration creates the team. If the team already exists in the destination, its conversations are skipped, and the report says so. Members are added after the migration completes, so users see the team only when it's complete.
Running again
Running the same list again is safe:
- existing groups are merged (or skipped, if you choose);
- owners and members already present are skipped;
- with Copy if newer, only changed files are copied again.
Was this article helpful?
Updated 2026-10-17