PLATFORM
Microsoft Teams Migration Tool
MigrationFox migrates Microsoft Teams between tenants, brings Slack workspaces into Teams, and moves Teams to Google Chat. Channel messages and replies keep their original dates and, in Teams, their real authors. Team members and owners are added, and the files in each channel come along.
Connect Teams
Teams import uses Microsoft’s Teams migration API, which only works with app permissions. Connect each tenant in one of two ways:
- Connect with admin consent: a Global Admin approves the MigrationFox Teams app for the tenant in one step.
- Bring your own Azure app: register an app in your tenant, grant the listed permissions, and paste its details.
What Gets Migrated
- Teams and channels: destination teams and channels (standard and private) are created for you, or messages go into a team you already have
- Channel messages and threaded replies: reply chains stay under their parent message
- Original dates: each message keeps the time it was originally sent
- Real authors: in a new team, each imported message is authored by the mapped person’s account at the destination, so Teams shows the real person. If someone can’t be matched, the message carries their name and email instead.
- Members and owners: after the import, everyone in the source team is added to the destination team with their role, through your user mapping (or the same email when there is no mapping). Guests and people without a match are listed in the job log. For a team that already exists, only missing people are added; nobody is removed.
- Channel files: the files in each channel (stored in SharePoint) are copied by a companion file migration that starts automatically
User Mapping
Moving between tenants usually means addresses change. Auto-match pairs people by exact email, then by the same username before the @, then by the same display name, reading the whole destination directory. Review the matches, fix any by hand, or upload a CSV of source and destination emails.
How Tenant-to-Tenant Migration Works
- Discovery: pick the source teams and channels
- Provisioning: destination teams and channels are created in Teams migration mode
- Import: messages and replies are written with their original dates and authors
- Finish: channels and the team leave migration mode, members and owners are added, and the channel files copy runs
Slack to Teams
MigrationFox reads Slack channel history and imports it into Teams channels using migration mode. Slack threads become Teams reply chains, files shared in Slack are copied into the Teams channel’s Files, and workspace members are added to the team through your user mapping. See the Slack migration page for details.
What Doesn’t Migrate Yet
- Reactions on Teams-to-Teams messages
- Inline attachment cards inside messages (the files themselves come across with the channel’s files)
- Tabs, apps and connectors
- Private channel membership (private channels are created; add their members in Teams)
- One-to-one and group chats
Key Features
- Teams migration mode: Microsoft’s supported way to import history with original dates and authors
- Full history: every message in the channels you pick, not only recent posts
- Progress tracking: real-time message counts and channel completion in the dashboard
- Error recovery: a message that fails is logged and the rest of the channel keeps going
- On MigrationFox web: runs in our cloud with nothing to install; chat migrations use pay-as-you-go credit
Migrating Teams to Google Chat
Switching from Microsoft 365 to Google Workspace? Teams channels migrate to Google Chat spaces, message-attached files land in a dedicated Shared Drive, and the channel’s files migrate alongside through a companion SharePoint to Google Drive job. See the Teams to Google Chat migration guide.