Does MigrationFox migrate direct messages (DMs)?

No. DMs and group DMs are private conversations and are not migrated. Microsoft Teams has a separate private chat model that doesn't map cleanly to Slack DMs. Only public and private channels are moved.

Are message threads and replies preserved?

Yes. Slack threaded replies become Teams threaded replies, so conversation structure is maintained. Parent messages and child replies retain their original author and timestamp.

Are files shared in Slack channels migrated?

Yes. Files uploaded to Slack channels are downloaded and re-uploaded to the corresponding Teams channel's SharePoint library, with inline references in the message body rewritten to the new file URL.

MIGRATION GUIDE

Migrate Slack to Microsoft Teams

Q: What about emoji reactions and pins?

Emoji reactions are not migrated because Teams has a limited reaction set. Pinned messages are noted in the manifest but not automatically re-pinned on the Teams side.

Consolidating collaboration on Microsoft 365? MigrationFox moves Slack channels, messages, threaded replies, file attachments, and member lists directly into Microsoft Teams — preserving author attribution, timestamps, and conversation structure.

Why Migrate Slack to Teams?

Organizations on Microsoft 365 often retire Slack to consolidate on Teams for cost and integration reasons. Teams is included with every M365 business license and integrates natively with Outlook, SharePoint, OneDrive, and every other app in the tenant.

Included with existing Microsoft 365 licenses — no separate Slack bill
Native integration with Outlook, SharePoint, and OneDrive
Unified compliance, retention, and eDiscovery
One directory, one set of credentials, one admin console

What Gets Migrated

Public channels — created as standard channels in the target Team
Private channels — created as private channels in the target Team
Messages — text content with original author name and timestamp
Threaded replies — mapped to Teams threaded replies, preserving conversation structure
File attachments — re-uploaded to the channel's SharePoint library, with inline links rewritten
Channel members — matched to Entra ID by email address and added to the Team
Code blocks and formatting — converted from Slack markdown to Teams rich text

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 — noted in the manifest but not auto-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 install the MigrationFox Slack app as a workspace owner. The app requests the channels:history, channels:read, files:read, and users:read scopes so it can enumerate channels, messages, and members.

Step 3 — Connect Microsoft Teams

Go to Connections → New → Microsoft Teams and sign in as a Global Admin. Grant the Graph API permissions for Group.ReadWrite.All, ChannelMessage.Send, and related scopes so MigrationFox can create channels and import messages.

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 original author attribution, then file attachments are uploaded. Live progress appears in the dashboard.

Pricing

Slack to Teams migrations are billed at $0.50 per GB of file attachments transferred. 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 original author and timestamp preserved.

What about reactions and pins?

Reactions are dropped because Teams has a limited reaction set. Pinned messages are noted in the manifest but not auto-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, and inline links in messages are rewritten to the new file URLs.