Migrating Microsoft Teams from one tenant to another is one of the most technically demanding scenarios in the Microsoft 365 ecosystem. Unlike a standard email migration, Teams is deeply woven into SharePoint, Exchange, and Azure AD — and Microsoft provides no native tenant-to-tenant migration tool. This guide walks you through exactly what to expect, what gets migrated, how to preserve chat history, and how to avoid the most common costly mistakes.
When Do You Need to Migrate Teams to a New Tenant?
Mergers & Acquisitions
Consolidating two companies' Teams environments into a single unified tenant after acquisition or merger.
Business Divestitures
Spinning off a business unit or subsidiary that needs its own independent Microsoft 365 tenant.
Tenant Consolidation
Merging multiple regional or departmental Teams tenants into a single global environment.
Microsoft Teams Tenant Migration Service
Rather than attempting this yourself with Microsoft's limited native tooling, our Teams tenant migration service handles everything — channels, chat history, files, apps, and cutover — in 5-10 business days with a zero data loss guarantee.
What Gets Migrated When You Move Teams Between Tenants?
A comprehensive Teams tenant migration moves far more than just channels and messages. Here's a complete breakdown of everything that transfers — and what requires extra attention:
Teams & Channels
Full PreservationAll team structures, public and private channels, channel tabs, settings, and custom configurations
Chat History
Requires Specialist ToolsChannel messages, private chats, group conversations, threaded replies, and reactions with original timestamps
Files & Documents
Full PreservationAll SharePoint-backed files, folder hierarchies, version histories, and shared documents
Members & Permissions
Full PreservationTeam owner/member roles, channel-level permissions, guest access settings
Apps & Integrations
Reconfiguration NeededMicrosoft apps auto-reconnected. Third-party apps, bots, and connectors require re-authorization in new tenant
Meeting Recordings
Mostly PreservedRecordings stored in SharePoint/OneDrive migrate with files. Classic Stream recordings require special handling
Planner Tasks
Full PreservationPlanner boards associated with Teams channels migrated with structure and assignments
Team Settings & Policies
Full PreservationMessaging policies, moderation settings, @mention settings, and fun/GIF toggles
What Microsoft's Native Tools Don't Move
Microsoft provides no built-in tenant-to-tenant migration tool. Without specialist platforms, you'll lose: all chat history, app configurations, channel tabs, and version histories. You'd essentially be starting over in the new tenant. Specialist tools like BitTitan MigrationWiz, AvePoint FLY, and Quest On Demand Migration bridge this gap.
Have questions about this topic?
Our migration specialists can help. Chat live or request a free consultation.
Why Teams Tenant Migration Is Uniquely Complex
Teams isn't a standalone messaging app. It's a collaboration layer built on top of four other Microsoft 365 services — and each one must be carefully handled during a tenant move:
SharePoint Backing for Files
Every Teams channel has a corresponding SharePoint document library. Files in Teams are actually stored in SharePoint, not in Teams itself. During migration, SharePoint must be migrated in tandem with Teams — and user permissions must be re-mapped using a source-to-target user mapping file.
Exchange for Calendar & Compliance
Teams chat history is stored in users' Exchange Online compliance mailboxes (hidden folder). This is why IMAP migration doesn't move Teams chats — you need a tool that can access and export from the compliance mailbox store.
Azure AD for Identity & Permissions
All Teams memberships, app registrations, bots, and connectors are tied to the source tenant's Azure Active Directory. Moving to a new tenant means new object IDs for every user and group — all permissions and app authorizations must be rebuilt.
No Native Migration Tool
Unlike Exchange Online (which has the Exchange Admin Center migration tools) or SharePoint (which has the SharePoint Migration Tool), Teams has no Microsoft-provided tenant-to-tenant migration capability. Every Teams migration requires a third-party platform.
Step-by-Step: How to Migrate Teams Between Tenants
Discovery & Inventory
1-2 daysBefore any data moves, get a complete picture of your Teams environment.
- Export a full inventory of all teams, channels (public & private), and member lists
- Document all connected apps, bots, connectors, and custom integrations
- Calculate total chat volume and data size (affects migration duration)
- Identify meeting recordings in Stream vs SharePoint
- Map all users between source and target tenants
- Document Teams policies: messaging, meeting, calling, permission policies
Destination Tenant Preparation
1 daySet up and configure the new tenant before migration begins.
- Create user accounts matching source tenant UPNs
- Assign Microsoft 365 licenses including Teams
- Configure Teams policies to match source tenant settings
- Set up Azure AD groups needed for Teams membership
- Enable coexistence mode if running both tenants during migration
- Install and authorize the migration tooling (BitTitan / AvePoint / Quest)
Pilot Migration
1-2 daysTest with 2-3 non-critical teams before committing to a full migration.
- Select pilot teams — ideally a cross-section of small, medium, and app-heavy teams
- Run full migration including channels, files, and chat history for pilot teams
- Verify channel structure, file access, and permissions in destination
- Test all app integrations and bots in the new tenant environment
- Collect pilot user feedback before proceeding to full migration
- Adjust migration configuration based on pilot findings
Full Migration Execution
3-6 daysMigrate all remaining teams in waves, managing the process carefully.
- Migrate teams in priority batches — typically by department
- Run continuous delta sync to capture new messages during migration
- Migrate SharePoint document libraries in sync with Teams files
- Reconnect Microsoft apps (Planner, Forms, Lists) in destination
- Re-authorize third-party apps and bots in new Azure AD tenant
- Monitor migration logs and resolve any errors in real-time
Cutover & Post-Migration
1-2 daysFinal user transition and validation of the completed migration.
- Communicate sign-in instructions to all users (sign out, sign back in with new credentials)
- Verify all teams, channels, and chat history in destination tenant
- Test all connected app integrations end-to-end
- Update mobile devices and external clients with new tenant credentials
- Post-migration support period begins (60 days for most plans)
- Decommission source tenant Teams environment after validation period
The Chat History Problem — And How to Solve It
Chat history is the most asked-about issue in Teams migrations — and for good reason. Many organizations discover mid-migration that native tools don't move it, leading to panic and data loss. Here's the definitive explanation:
Why Chat History Doesn't Move by Default
Teams chat messages are stored in two places: the Teams backend service (for display) and each user's Exchange Online compliance mailbox (for search and eDiscovery). Standard migration tools only move mailbox data — they don't have access to the Teams backend storage, so chat history disappears unless you use a specialist tool.
Microsoft Native Tools
Cannot move Teams chat history. Will appear blank in new tenant.
Manual Export
Possible via eDiscovery but not importable — read-only archive only.
Specialist Tools
BitTitan, AvePoint, Quest — export and re-ingest into new tenant.
The Two Approaches to Chat History
Option A: Full Migration (Recommended)
Use AvePoint FLY or Quest On Demand to export all chat history and re-ingest into the destination tenant. Users see their full chat history in the new tenant.
- Full conversation continuity
- Searchable in new tenant
- Adds 1-3 days to migration timeline
- Higher cost due to specialist tooling
Option B: Archive & Start Fresh
Archive old chat history as read-only files and start fresh conversations in the new tenant. Simpler and faster, but history is not live in Teams.
- Faster and simpler migration
- Lower overall cost
- History not searchable in Teams
- Suitable for organizations with short-term retention needs
Not sure which approach is right? Talk to one of our specialists — we'll assess your chat volume, compliance requirements, and budget to recommend the right path.
Teams is Part of a Full Microsoft 365 Tenant Migration
If you're migrating an entire organization, Teams is typically one workload alongside Exchange Online, SharePoint, OneDrive, and Azure AD. Read our comprehensive guide to Microsoft 365 tenant-to-tenant migration for the complete picture.
Read the Full Tenant Migration GuideTeams Migration Timeline & Cost
Typical Timeline by Org Size
Pricing
Want an exact quote? View the full service page or use our pricing calculator to estimate your specific project.
Planning a Teams Tenant Migration?
134+ Teams migrations completed with zero data loss. Get a free assessment and exact timeline for your project.
Get a Free Migration Quote
No spam, just expert advice.
Frequently Asked Questions
Yes. Microsoft Teams can be fully migrated between Microsoft 365 tenants — including channels, chat history, files, member permissions, tabs, and app integrations. The process requires specialist tooling because Microsoft does not provide a native tenant-to-tenant migration tool. Third-party platforms like BitTitan, AvePoint FLY, and Quest On Demand Migration are used to complete the migration.
A complete Teams tenant migration preserves: all team structures and channel configurations, conversation history (channel messages and private chats), SharePoint-backed files and folder hierarchies with version histories, team member lists and owner/member roles, custom tabs and pinned applications, meeting recordings stored in SharePoint/OneDrive, and Planner tasks associated with teams.
No — chat history does not have to be lost, but it requires specialist tooling. Microsoft's native tools do not move Teams chat history, but third-party migration platforms can export all message history and re-ingest it into the destination tenant. Some organizations choose to archive old chat data and start fresh; our team helps you decide which approach is right for your business.
A typical Teams migration takes 5-10 business days. Small organizations under 50 users can be completed in 3-5 days. Mid-size organizations (50-200 users) typically need 7-10 days. Large enterprises with complex app integrations and 200+ users may require 2-3 weeks using a phased approach.
With a properly planned migration, users experience no productive-hour downtime. We use parallel migration — users continue working in the source tenant while we build and populate the destination. The final cutover is 2-4 hours, scheduled during off-peak hours.
Standard Microsoft apps (Planner, Forms, Lists) are automatically reconnected in the destination tenant. Custom apps, bots, connectors, and third-party integrations are registered per Azure AD tenant, so they must be re-authorized and configured in the new environment. We document all integrations during the discovery phase and provide a complete reconnection runbook.
Yes. Selective team migration is one of the most common scenarios — ideal for M&A carve-outs, partial tenant consolidations, and pilot migrations. Our per-team pricing is designed for this exact use case. You choose which teams to migrate and we move only those.
Yes. Teams migration is typically one workload in a coordinated full M365 tenant migration alongside Exchange Online (email), SharePoint, OneDrive, and Azure AD. We offer Teams-only migrations for organizations that only need to move their Teams environment, or as part of a comprehensive full tenant migration project.
Related Articles
Ready to Migrate Your Microsoft Teams?
WorkspaceMigration specializes in Teams tenant migrations for M&A, divestitures, and consolidations. 134+ Teams migrations completed with zero data loss — chat history, channels, files, and apps all preserved.