Shared and private channels both have their own SharePoint site, but they handle people very differently. Shared channels can include people from other teams and other tenants. Microsoft says neither type can move to another team. List both types first, set up cross-tenant access, then copy members, messages and files.
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.
I see this in almost every Teams project. This guide explains Teams shared channels migration, how it differs from private channels and the steps I follow, using facts from Microsoft's own page.
Why are Shared Channels Harder to Migrate 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.
It 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 miss. Files and messages can be copied. The cross-tenant link has to be rebuilt by hand.
How do Shared and Private Channels Compare?
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 Changes for Shared Channels in a Tenant Move?
Microsoft says sharing with people outside your organization needs cross-tenant access settings in Microsoft Entra ID. Every organization you share with must complete 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 leaves them behind.
So after a tenant move, 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 Migrate Shared and Private Channels Step by Step?
These are the steps I follow. They work for both types and add extra care for shared channels.
- List every private and 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 of both types. Copy a small private channel and a small shared channel. Open both 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.
RecoveryTools Teams Migrator handles standard, private and shared channels, posts messages with the original author, date and reactions and validates your selection before it writes. For private channels in detail, read how to migrate Teams private channels.
Move Shared and Private Channels Together
RecoveryTools Teams Migrator copies teams and channels between Microsoft 365 tenants with the author, date and reactions on every message. It handles standard, private and shared channels. Test one of both types first, then move the rest.
The trial unlocks every option and caps volume at 25 items per channel and per chat. Works on Windows 11, 10 and Windows Server.
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. For the wider move, read how to migrate Microsoft Teams to another tenant and what does not migrate in Microsoft Teams.
For the files behind a channel, see how to migrate a SharePoint site to another tenant. For one channel only, read how to move a Teams channel to another team.
What are the Best Practices for Shared Channel Migration?
- Inventory both channel types first. Shared and private 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.
- Keep two owners. Microsoft recommends more than one owner for shared channels.
- Do not rely on a team clone. It leaves shared channels behind.
Which Mistakes Break Shared Channels After a Move?
Four come up often. First, forgetting external participants and leaving partners locked out. 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 Teams Shared Channels Migration
Private and shared channels both need their own plan. Shared channels need more, because partner access has to be rebuilt between tenants.
List both types, set up cross-tenant access, copy the data and then add the external people back. Test one channel of both types before the full move.
Frequently Asked Questions
What is a Shared Channel in Microsoft Teams?
It is a channel that can include people who are not in the parent team. Microsoft says only owners or members of the shared channel can access it.
Can You Move a Shared Channel to Another Team?
No. Microsoft says a shared channel cannot be moved to a different team and cannot be converted to a standard channel.
Where are Shared Channel Files Stored?
Microsoft says every shared channel has its own SharePoint site with a document library. Team members and admins do not get access unless they are also channel members.
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.
Does Cloning a Team Copy Its Shared Channels?
No. Microsoft says cloning a team does not clone its shared channels, so you must copy them another way.
What do You Need to Share a Channel Across Tenants?
Microsoft says cross-tenant access settings must be configured in Microsoft Entra ID, and the other organization must configure them too. Guest access in Teams must also be enabled.
Does RecoveryTools Teams Migrator Copy Shared Channels?
Yes. It handles standard, private and shared channels and posts messages with the original author, date and reactions. Check the external participants after the copy.
Jamie blends strategic marketing insight with technical writing, turning migration and recovery topics into guidance that works for technical and general readers alike.
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.