MIGRATION GUIDE
Migrate Slack to Microsoft Teams
MigrationFox moves Slack channels, messages, threaded replies, file attachments, and member lists directly into Microsoft Teams, preserving author attribution, timestamps, and conversation structure.
What Gets Migrated
- Public channels: created as standard channels in the target Team
- Private channels: created as private channels in the target Team. They are listed during discovery when the Slack app has the private-channel scopes and has been added to those channels
- Messages: text content with the original timestamp, posted as the mapped person’s account when MigrationFox creates the destination team (otherwise the original author’s name and email are shown on the message). Message text is carried as plain text, and join and leave notices are left out
- Threaded replies: mapped to Teams threaded replies, preserving conversation structure
- File attachments: re-uploaded to the channel's SharePoint library (the channel’s Files tab). The imported messages don’t link to the copied files yet. A file that can’t be copied doesn’t stop the rest, and the job log shows how many files were copied
- Channel members: added to the Team through your user mapping, with Slack admins and owners becoming team owners. Auto-match pairs people by exact email, then by the same username before the @, then by the exact same display name, the last two only when exactly one Microsoft 365 person fits. You see every match before the migration starts and can fix it by hand or upload a CSV. People without a Microsoft 365 match are listed in the job log
What Doesn't Get Migrated
A few Slack features don't have direct equivalents in Teams and are intentionally skipped:
- Direct messages (DMs): private user-to-user conversations are not moved
- Group DMs: Slack's multi-person direct messages don't map to Teams
- Emoji reactions: Teams has a limited reaction set; reactions are dropped
- Pinned messages: migrated as normal messages, not re-pinned on the Teams side
- Slack apps and bots: third-party integrations need to be reconfigured in Teams
Step-by-Step: How to Migrate
Step 1: Sign up for MigrationFox
Create an account at app.migrationfox.com. The first 2 GB of file attachments are free with no credit card required.
Step 2: Connect Slack
Go to Connections → New → Slack and paste the Bot User OAuth Token (xoxb-) of a Slack app you create in your workspace. The setup steps in MigrationFox list the bot scopes to add: channels:history, channels:read, groups:history, groups:read (private channels), users:read, users:read.email (user mapping) and files:read (attachments). The bot token is encrypted at rest, and you can revoke it in Slack as soon as the job completes. Channel history is read page by page with automatic back-off when Slack rate-limits, so large workspaces don’t stall.
Step 3: Connect Microsoft Teams
Go to Connections → New → Microsoft Teams and choose Connect with admin consent. A Microsoft 365 admin approves the MigrationFox Teams app once for the tenant, which lets MigrationFox create the team and channels, import messages under the right authors and add members. (You can bring your own Azure app instead.)
Step 4: Create a migration job
Create a new job, pick your Slack workspace as the source, and select the channels you want to move. Then pick an existing Team or let MigrationFox create a new Team to host them. You can map multiple Slack channels into the same Team or split them across Teams.
Step 5: Scan
Run a discovery scan. MigrationFox enumerates every selected channel and reports message count, file count, total file size, and any members that can't be matched to Entra ID. Scans are free and unlimited.
Step 6: Run the migration
Start the job. Channels are created first, then messages are imported in chronological order with their original timestamps, then file attachments are uploaded, and finally members and owners are added to the team. Live progress appears in the dashboard.
Pricing
Slack to Teams migrations are billed by the gigabytes of file attachments transferred (see pricing). Messages themselves don't count against your quota. Every account starts with 2 GB free, no credit card required. Discovery scans are always free.
Frequently Asked Questions
Are direct messages migrated?
No. DMs and group DMs are private and are intentionally skipped. Only public and private channels are moved.
Are message threads preserved?
Yes. Slack threaded replies map directly to Teams threaded replies, with the original timestamp, posted as the mapped person when MigrationFox creates the destination team.
What about reactions and pins?
Reactions are dropped because Teams has a limited reaction set. Pinned messages are migrated as normal messages but not re-pinned on the Teams side.
Are files migrated?
Yes. Files uploaded to Slack channels are re-uploaded to the matching Teams channel's SharePoint library (the channel’s Files tab).