Move Teams shared channels in 6 steps. List, set access, map, create, test and copy in that order. Access settings come before any copy. Microsoft says a shared channel cannot move to another team. Only team owners can create shared channels. Guests cannot join shared channels. RecoveryTools Teams Migrator copies shared channels with authors. Test one small shared channel first.
Your team moved to the new tenant and the standard channels look right. Then someone asks where the partner channel went. It had people from another company in it and none of them can find it now.
Partner channels get missed in most Teams projects I handle. This guide explains how to move Teams shared channels, how they differ from private channels and the steps I follow, using facts from Microsoft's own page.
Why are Shared Channels Harder to Move Than Standard Channels?
Microsoft's page on shared channels in Microsoft Teams says they create spaces that can include people who are not in the team. Only owners or members of the shared channel can open it. Other members of the parent team cannot see it unless they are added.
Microsoft also says shared channels can include people outside your organization through Microsoft Entra B2B direct connect. Guests with Entra guest accounts cannot be added. So a shared channel depends on the trust between two tenants, not only on the files and messages inside it.
In my experience, that is the part migrations omit. Files and messages can be copied. The cross tenant link has to be rebuilt by hand.
How do Shared Channels Compare With Other Channel Types?
Both have their own SharePoint site. The big difference is who can join.
| Part | Private channel | Shared channel |
|---|---|---|
| Who can join | Team members, including guests | People in your org and external people through B2B direct connect. No guests |
| Files | Own SharePoint site | Own SharePoint site |
| Move to another team | Not possible | Not possible |
| Convert to standard | Not possible | Not possible |
| Team owner access | Sees it under Manage team and can delete it | Sees the name and can delete it but not the files or members |
| Who creates it | Team owners and members by default | Team owners only |
What Differs for Shared Channels in a Tenant Move?
Who it suits. Technical user in a Microsoft Entra admin role Extra application. None, because a browser is enough
Microsoft says sharing with people outside your organization needs cross tenant access settings in Microsoft Entra ID. Every organization you share with must finish this setup too. Guest access in Teams must also be on, even though these people do not use guest accounts.
Two more points matter for a move. External participants must be added by UPN if the UPN and email address do not match. Also, Microsoft says cloning a team does not clone its shared channels so the clone shortcut omits them.
So after you move the Teams shared channels, set up the cross tenant access settings for your partners first. Then add the external people back. In my experience, people who were internal before can become external after a merger and the reverse. Check who is who before you add anyone.
How do You Move Shared Channels Step by Step?
Who it suits. Technical user in a Teams owner or admin role Extra application. A Teams copy tool for the final copy
Here are the steps I follow to move the Teams shared channels. They add extra care for the partner access that shared channels carry.
- List every shared channel. Record the owners, members and external participants. Team owners can see shared channel names but not the files or members.
- Set up cross tenant access. In Microsoft Entra ID, configure access for every partner organization. Ask every partner to do the same.
- Map users and external people. Match internal accounts to the destination. Note the UPN for every external participant.
- Create the destination team. Only team owners can create shared channels so set owners first.
- Test one shared channel. Copy a small shared channel. Open it as an owner and as a member.
- Copy the rest and add people back. Move the remaining channels, then add the external participants to every shared channel.
For private channels in detail, see how to migrate Teams private channels.
Move Shared Channels With Their Team
Move teams together with their shared channels using RecoveryTools Teams Migrator. Every message arrives with its author, date and reactions. Try one small shared channel first and then copy the rest.
Teams Migrator has a graphical interface that is Easy to Use. The software is capable of copying shared channels and allows you to validate the selection before anything moves. Messages remain accessible with authors, dates and reactions maintained.
The free trial opens every option with a cap of 25 items for a channel and for a chat. Teams Migrator installs on Windows 11, 10 and Windows Server 2022.
What should You Check After a Shared Channel Move?
Open every shared channel as an owner and as a member. Check the member list first, because external participants are the people most likely to be missing. Then check the Files tab and a few messages for author and date.
Microsoft says the shared channel site inherits the parent team's sensitivity label. So confirm the label on the destination team before you copy files. Moving the team around these channels too? Start with how to migrate Microsoft Teams to another tenant and what does not migrate in Microsoft Teams.
Files sit in SharePoint, so see how to migrate a SharePoint site to another tenant. Moving just one channel? See how to move a Teams channel to another team.
Which Practices Protect Shared Channels During a Move?
- Inventory every shared channel first. Shared channels hide from people who are not members.
- Agree with partners early. Cross tenant access needs setup on both sides.
- Record every UPN. External people must be added by UPN when it differs from the email address.
- Have two owners. Microsoft recommends more than one owner for shared channels.
- Do not rely on a team clone. It omits shared channels.
Which Mistakes Break Shared Channels After a Move?
Four mistakes show up again and again. First, forgetting external participants and leaving partners without access. Second, copying files without setting cross tenant access first. Third, trying to add guests, who cannot join shared channels. Fourth, using a team clone and thinking every channel came along.
My Verdict on Moving Teams Shared Channels
Move the Teams shared channels with their own plan, because partner access has to be rebuilt between tenants.
List every shared channel, set up cross tenant access, copy the data and then add the external people back. Test one channel before the full move.
Frequently Asked Questions
Can You Move a Shared Channel to Another Team?
No. Microsoft says a shared channel cannot move to a different team or become a standard channel. You create it again at the destination or copy it with a migration tool.
Can Guests Join a Shared Channel?
No. Microsoft says guests with Entra guest accounts cannot be added. People outside your organization join through Microsoft Entra B2B direct connect.
Do You Need Entra Settings to Share a Channel Across Tenants?
Yes. Microsoft says you configure the access settings in Microsoft Entra ID and the other organization must configure them too. Guest access in Teams must also be on.
Does Cloning a Team Copy Its Shared Channels?
No. Microsoft says cloning a team does not clone its shared channels. You must copy them another way.
Can a Team Owner Open Shared Channel Files After the Move?
No. A team owner sees the channel name and can delete the channel but cannot open the files or members. Only owners or members of the shared channel can open them.
Can You Add External People Back by UPN?
Yes. Microsoft says external participants must be added by UPN if the UPN and email address do not match. Record every UPN before the move.
Does RecoveryTools Teams Migrator Copy Shared Channels With Messages?
Yes. RecoveryTools Teams Migrator handles standard, private and shared channels and carries over the original author, date and reactions on every message. Check the external participants after the copy.
Published 17 October 2026. Shared channel facts come from Microsoft's page on shared channels in Microsoft Teams. Product behavior comes from the RecoveryTools Teams Migrator page. Microsoft can change these limits so check them before you plan.