Channel files
Every channel's files with version history, dates and the people behind them, mapped to the other tenant.
Copy a team into a different Microsoft 365 tenant, or duplicate it inside your own: channels, owners and members, every channel's files with their history, Planner and tabs, and the channel posts under their original authors and times if you want them.
Can you copy a Microsoft Team to another tenant?
Not with Microsoft's own tools. Creating a team from an existing team copies its settings, channel list, apps, tabs and members, but only inside your own tenant and without the files or the conversations, and Microsoft's cross-tenant migration add-on leaves teams and channels in the source tenant. ShareMaster's Copy a team copies a team into another tenant, or inside the same one, with its standard, private and shared channels, owners and members, each channel's files with their version history, Planner plans and tabs, and optionally the channel posts with their original authors and times.
Every channel's files with version history, dates and the people behind them, mapped to the other tenant.
Posts and replies under their original authors and times, with reactions, inline images and file links.
Copied with their own owners, members and files, not just the standard channels.
Plans with buckets, tasks, assignments and checklists; tabs re-pointed at the copied files and plans.
Teams has a built-in copy: create a new team and choose to base it on one you already belong to. It reproduces the shape of the team, meaning its settings, channel list, apps, tabs and optionally its members, and that is all. Microsoft's own documentation for the same operation says the channels arrive without their messages, files are missing from the list of parts it can copy, and tabs arrive unconfigured. It also only offers teams in your own tenant.
For moves between tenants, Microsoft's paid migration service moves mailboxes, OneDrive and people's chats, but its overview states that teams, channels and SharePoint sites are not migrated and stay in the source tenant.
| Teams: create from an existing team | ShareMaster Copy a team | |
|---|---|---|
| Into another tenant | No | Yes, or inside the same tenant |
| Channels | Structure | Standard, private and shared, with their people |
| Channel files | No | Yes, with version history, dates and authors |
| Posts and replies | No | Optional, with original author and time |
| Planner | No | Plans, buckets, tasks, assignments, checklists |
| Tabs | Unconfigured | Website, Office, PDF and library tabs re-pointed; others named in the report |
| Owners and members | Optional | Yes, mapped to the destination's accounts |
| Proof it matches | No | A compare of settings, people, files, posts, Planner and tabs |
A team's files live in a SharePoint site, and Copy a team takes care of those. If the move is part of a bigger tenant migration, with communication sites, project sites and OneDrives as well, the SharePoint tenant to tenant migration page covers that side. Inside one tenant, Move channels moves channels from one team into another and Merge teams folds one team into another. The Copy a team documentation has every option in detail.
Start a 14-day free trial, no credit card. Copy a small team into a test tenant and read the compare before you plan the rest.
Last updated