A team moves its active Slack channels to Microsoft Teams and discovers that an important reply is missing from an old thread. The first migration pass succeeded. The second also succeeded. The problem is the assumption that another pass synchronizes everything that changed. Microsoft's native tool has narrower incremental behavior, so the cutover plan needs to account for how people actually use threads.
Start with the supported content and then map the operating workflow. This guide covers Microsoft's Slack to Teams Migration Tool in the Microsoft 365 admin center. Other migration approaches may differ. The inventories, acceptance checks and cutover controls below are engineering recommendations, not promises that the native tool automatically verifies every business requirement.
1. Define what moves and what needs another route
The tool supports public and private Slack channels, channel messages with threading and standard reactions, file attachments, and channel owners and members. Channel canvas content becomes HTML file attachments. Slack lists become JSON file attachments. Those files should not be mistaken for equivalent editable features in the destination.
| Source content | Native tool boundary | Planning action |
|---|---|---|
| Public and private channels | Supported within exported and eligible scope | Inventory and map each channel |
| Direct messages and group chats | Not migrated by this tool | Choose a separately approved approach |
| Workflows and custom app integrations | Not migrated | Rebuild and test required behavior |
| Canvas and lists | HTML and JSON file attachments | Review usability and replacement needs |
| Slack Connect and archived channels | Not supported in their current state | Resolve scope before exporting |
An archived channel can be unarchived before export to make it available for migration. Treat that as a deliberate owner-approved change, not a reason to revive every dormant channel. The tool also does not support channel links such as #channel_name or custom reaction emojis. Record these differences so users know what to expect when following historical conversations.
2. Confirm exports and administrative access
The tool uses Slack export packages and online access to the workspace. An administrator generates an authorized export, uploads the ZIP to Azure Blob Storage in the customer's tenant and grants the migration app access to read it. Private-channel export steps can differ from public-channel steps, and Slack export options vary by plan. Inspect the actual package rather than inferring coverage from a successful download.
On Microsoft 365, the documented migration roles include Migration Administrator, SharePoint Administrator and Global Administrator. One-time consent for the migration app requires a Global Administrator. Azure storage permissions are a separate requirement. Have the relevant owners review both the import permissions and storage access before starting. Do not assume a Microsoft 365 role grants the required Azure authority.
3. Scan first and preserve the scope record
In the Microsoft 365 admin center, open Setup > Migration and imports > Slack to Teams and supply the export file URL. Select channels on the Conversations tab and run Scan messages. Review completed scan results before sending channels to migration. Save an inventory of source channel identity, intended destination, date range, responsible owner and exclusions.
Date filtering works on root messages and uses UTC. When a root falls within the selected range, its replies migrate even if their dates fall outside that range. A reply inside the range does not migrate if its root is outside it. Test a thread spanning the proposed boundary before approving a partial-history migration. A date range is not simply a filter on every visible message timestamp.
4. Review identity mapping, including former employees
All Slack users must be mapped before migration can proceed, including deactivated users. Auto-map can match email addresses, the username portion of an email address or display names. Those broader matching options make manual review important. Two people sharing a name should not silently become the same historical author.
Use the mapping interface or export and import the identity CSV. Where no equivalent Microsoft 365 user exists, the tool supports Unknown user. Make that an explicit mapping choice. Keep the reviewed mapping file and exceptions with the migration record. Reimported identity mappings overwrite previous mappings, so review the complete replacement rather than treating an upload as an additive patch.
5. Map destinations and test real access
The tool can migrate into existing teams or teams created by the migration tool. Destination channels, however, must be created by the tool. Each Slack channel needs its own independent Teams channel. The tool does not combine multiple source channels into one destination. Agree this structure with owners before users create a competing set of channels manually.
Check public, private and shared destination choices against the intended audience. For shared channels, Microsoft documents that the tool may add migrated members to the parent team and share the channel with that team. Validate the resulting team and channel access rather than checking names alone. Include an ordinary member and someone who should not have access in your test plan.
6. Plan incremental migration around root messages
Microsoft recommends a single channel migration pass where possible. Incremental migration tracks the most recently migrated root message. Additional passes use the same channel migration task, a new export from the same Slack tenant and a date range that permits the future messages you intend to copy. Creating a different task is not the documented incremental path.
For cutover, recommend a clearly communicated point when users stop writing in the source channels. Account separately for replies, edits and deletions made during migration. Decide how exceptions will be preserved or resolved before removing source access. Do not promise that a final export alone captures every outstanding change.
7. Validate messages, files and working processes
Generate the completed scan and migration CSV reports and review warnings, failures, task IDs and destination information. Message totals can differ for documented reasons. A reply also broadcast to the Slack channel can become both a thread reply and a root message in Teams. Investigate differences with representative records instead of declaring every count mismatch a failure or accepting every difference without explanation.
Open selected attachments as destination users. Restricted filename characters can become underscores, and the tool does not migrate attachment system metadata such as created and last-edited authors or dates. Check threads, author attribution, timestamps and access alongside file contents. For wider file moves, coordinate this work with your data migration plan.
8. Close the migration deliberately
The migration process does not delete Slack data. Keep the source available under an agreed access and retention plan until owners accept the result. Rebuild required notifications, bots and workflows separately and test their end-to-end behavior. Once migration and verification are complete, review the optional cleanup of the import project, Azure export files and migration app permissions with administrators.
How Remqa helps with Slack to Teams migrations
Remqa can help define scope, review identity and channel mappings, build validation checks and reconnect the workflows that the native transfer does not move. Our migration work treats accepted user behavior as part of the move, not just successful imports. Bring your channel inventory, export constraints and critical integrations to a conversation about forward deployed engineering support.