GUIDE · April 2, 2026 · 6 min read

How to Migrate Microsoft Teams Channels Between Tenants

Cross-tenant Teams migration is one of the most complex challenges in M365 administration. Whether you're going through a merger, acquisition, or organizational restructuring, moving Teams channels with their full chat history requires specialized tools.

What Gets Migrated

• Teams and channels — team structure and channel names are recreated
• Messages — chat messages with original timestamps and sender attribution
• Files — files shared in channels are migrated to the destination team's SharePoint
• User mapping — map source users to destination users (different tenants, different UPNs)

Prerequisites

• Azure AD app registration with Teamwork.Migrate.All application permission
• Admin consent granted on both source and destination tenants
• Destination team can be created automatically or pre-provisioned

How It Works

MigrationFox uses Microsoft's Teams Migration API (beta) to import messages with their original metadata. The process:

1. Create destination team in migration mode (special flag preserves timestamps)
2. Create channels matching the source structure
3. Import messages with original sender, timestamp, and attachments
4. Complete migration mode — team becomes active for users

Any files shared in channels are automatically migrated as companion file jobs.

User Mapping

Since source and destination are different tenants, user UPNs differ. MigrationFox supports user mapping to attribute messages correctly. Map john@source-company.com to john@dest-company.com in the migration wizard.

Get Started

Sign up free to start your Teams migration. MigrationFox handles the complexity of the Teams Migration API so you don't have to.