From e7d8584c7a00048012f3a518995fd85812ad5a95 Mon Sep 17 00:00:00 2001 From: "Richard Brynteson [MVP]" Date: Sat, 28 Dec 2024 09:02:24 -0600 Subject: [PATCH 1/3] Update migrate-slack-to-teams.md The free solution described in this article is no longer maintained. The updated link is a fork/rewrite of the previous solution but includes additional features including the ability to migrate messages into your channels. This solution is based on new Microsoft guidance and follows this article: https://devblogs.microsoft.com/microsoft365dev/migrate-messages-from-other-chat-platforms-to-microsoft-teams/ --- Teams/migrate-slack-to-teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/migrate-slack-to-teams.md b/Teams/migrate-slack-to-teams.md index 367dfa9a49..b9e95b3f9c 100644 --- a/Teams/migrate-slack-to-teams.md +++ b/Teams/migrate-slack-to-teams.md @@ -202,7 +202,7 @@ There are both free solutions on GitHub and paid solutions you can use, dependin Once you’ve set up your new team and channel structure in Teams, you can copy the exported files into the appropriate document libraries in your Teams channels. -To automate the importing of your content, there are several approaches you can consider. There are free solutions on GitHub ([ChannelSurf](https://github.com/tamhinsf/ChannelSurf) or [Slack Export Viewer](https://github.com/hfaran/slack-export-viewer)) and partner solutions. Choose a solution based on your organization’s needs. +To automate the importing of your content, there are several approaches you can consider. There are free solutions on GitHub ([ArgyleMigrator](https://github.com/rbrynteson/ArgyleMigrator) or [Slack Export Viewer](https://github.com/hfaran/slack-export-viewer)) and partner solutions. Choose a solution based on your organization’s needs. ### Channel Files From 328ba8b1e1bc2313bc595f881a68544d104879a7 Mon Sep 17 00:00:00 2001 From: Dani Smith Date: Mon, 30 Dec 2024 11:34:32 -0500 Subject: [PATCH 2/3] Fix typo in migration documentation --- Teams/migrate-slack-to-teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Teams/migrate-slack-to-teams.md b/Teams/migrate-slack-to-teams.md index b9e95b3f9c..da3a20336e 100644 --- a/Teams/migrate-slack-to-teams.md +++ b/Teams/migrate-slack-to-teams.md @@ -202,7 +202,7 @@ There are both free solutions on GitHub and paid solutions you can use, dependin Once you’ve set up your new team and channel structure in Teams, you can copy the exported files into the appropriate document libraries in your Teams channels. -To automate the importing of your content, there are several approaches you can consider. There are free solutions on GitHub ([ArgyleMigrator](https://github.com/rbrynteson/ArgyleMigrator) or [Slack Export Viewer](https://github.com/hfaran/slack-export-viewer)) and partner solutions. Choose a solution based on your organization’s needs. +To automate the importing of your content, there are several approaches you can consider. There are free solutions on GitHub ([ArgyleMigrator](https://github.com/rbrynteson/ArgyleMigrator) or [Slack Export Viewer](https://github.com/hfaran/slack-export-viewer)) and partner solutions. Choose a solution based on your organization’s needs. ### Channel Files From ddc56f810be1b1a7b77e18bdbcd8f4f6a9822fd7 Mon Sep 17 00:00:00 2001 From: Heidi Payne Date: Tue, 7 Jan 2025 09:42:20 -0800 Subject: [PATCH 3/3] Update author and ms.author fields --- Teams/migrate-slack-to-teams.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Teams/migrate-slack-to-teams.md b/Teams/migrate-slack-to-teams.md index da3a20336e..bd8f874ac2 100644 --- a/Teams/migrate-slack-to-teams.md +++ b/Teams/migrate-slack-to-teams.md @@ -1,7 +1,7 @@ --- title: Migrate from Slack to Microsoft Teams -author: DaniEASmith -ms.author: danismith +author: MicrosoftHeidi +ms.author: heidip manager: jtremper ms.reviewer: brandber ms.date: 10/14/2019