Microsoft has launched a native Slack-to-Teams migration tool in the Microsoft 365 admin center, simplifying the transition for organizations migrating collaboration workloads.
This feature supports transferring public and private channel content directly into Teams equivalents, preserving messages and continuity.
The tool enters public preview via Targeted Release in early December 2025, with rollout completion by late January 2026. General Availability follows worldwide from late January to early March 2026.
No opt-in is required, and it appears by default under Migration and imports. Microsoft 365 administrators handling Teams see it without disrupting existing functionality.
How the Migration Works
Administrators access the Slack-to-Teams migration section in the Microsoft 365 admin center. First, export Slack workspace data as a ZIP file, then upload it to an Azure Blob Storage container and generate a shared access signature (SAS) URL. Paste this URL into the tool to proceed. The interface prompts for selecting the blob path for Slack exports.
Eligible Slack channels are displayed for review, with a mapping to Teams shared, public, or private channels. User mapping occurs via web UI or CSV for scale, requiring roles like Microsoft 365 Migration Administrator or Global Administrator for consent.
The tool transforms Slack data, threaded conversations, reactions, and attachments into Teams format without deleting originals. Initial support covers channels; expansions target direct messages and more.
This native option eliminates reliance on third-party tools like CloudFuze or Kernel, cutting costs and complexity. Organizations retain conversation history during transitions, aiding compliance and productivity.
No pre-rollout actions needed, but planning migrations involves auditing Slack readiness and notifying IT teams. Future updates promise broader content types, enhancing Teams’ ecosystem.
Global Administrators grant one-time consent for the Microsoft 365 Teams Migration app. Permitted roles ensure controlled access, aligning with enterprise security. Data stays in customer-controlled Azure storage until import, minimizing exposure.
For cybersecurity-focused teams, this reduces manual export risks during migrations. No reported vulnerabilities tied to the preview, but monitoring CISA or NVD remains standard.
Microsoft positions this as a continuity booster amid Teams’ dominance, with over 320 million users. Early adopters in Targeted Release report smooth pilots, per community feedback. As GA nears, expect wider uptake for hybrid Slack-Teams environments.
Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.
