Tauri Migration

Migrate Microsoft Teams channel files

The files of a Microsoft Teams team live in SharePoint: a folder of the Documents library for a standard channel, a separate site for a private or shared channel. You pick the team and the channel; the tool finds where the files are and migrates them with their history.

Short answer

Tauri Migration migrates the files of Teams channels, standard, private and shared, with their versions, authors, dates and permissions, into a channel of a team that already exists. Conversations, tabs, apps and team creation are out of scope.

What is migrated

ItemMigratedDetails
Files and folders of a channelYesWith version history, authors, dates and metadata
Standard channelsYesThe channel folder in the Documents library of the team site
Private and shared channelsYesThe channel’s own SharePoint site, found automatically
Unique permissions on folders and filesYesTeam site groups are matched; those of private channel sites are not
Conversations and repliesNoThey stay in the source team
Tabs, apps, Planner, wikiNo
Creating the team and channelsNoThe target team and channels must exist
Team members and ownersNoManaged in Teams or Entra ID

Every combination

A Teams channel is one side of a pair like any other: it combines with a site, a OneDrive, a file share or another channel.

  • Channel to channel, to another tenant, or within one tenant to merge teams.
  • OneDrive to channel: a colleague’s project folders join the team taking them over.
  • File share to channel: a department’s folder on the file server becomes its channel’s folder.
  • SharePoint site to channel, and back: a library of an old team site joins the channel that replaces it.
  • Channel to site, OneDrive or file share: archiving a team that closes.

How it works

  1. Allow reading teamsOn top of the SharePoint permissions, an admin consents to reading teams and channels through Microsoft Graph. Teams is only used to choose: the tool writes nothing to Teams.
  2. Prepare the targetThe team and its channels exist, and so do the accounts. The migration account can access the sites of private and shared channels.
  3. Pick the team, then the channelsSearch the team by name. By default, “Copy everything” migrates the files of every standard channel; for a private or shared channel, or a specific subfolder, each folder pair picks its channel.
  4. Or plan in ExcelIn the template, a cell accepts the channel link copied from Teams (“Get link to channel”). The tool resolves it on import and checks every row.
  5. Passes and cutoverAs for a site: a first pass, incremental passes while the source team keeps working, then a last pass on cutover day.

Good to know

  • Links to files posted in conversations still point to the source.
  • If the tool reports that the site of a private or shared channel does not exist yet, open that channel’s Files tab in Teams, then run again.
  • To also move conversations, tabs and the teams themselves, you need a full Teams migration tool. See our ShareGate comparison.

Frequently asked questions

Are channel conversations migrated?

No. Only channel files are migrated. Conversations stay in the source team.

Must the target team be created beforehand?

Yes. The team and its channels must exist in the target: the tool creates neither teams nor channels.

Are private and shared channels supported?

Yes. Their files live in a SharePoint site of their own, which the tool finds from the chosen channel.

Can a OneDrive folder or a file share go into a channel?

Yes. Every combination works between site, OneDrive, file share and Teams channel.

Test it on your own tenant

The 14-day trial migrates 10% of every library, with versions, metadata and permissions. After you subscribe, an incremental run migrates the rest.