Importing from Slack, Hipchat, Flowdock, Basecamp, etc.
We are using Slack for a long time and now we are thinking to transition to MS Teams. In Slack it is possible to export all channel content's in JSON with links to files uploaded to slack.
It could be very useful to have the ability to import the slack history into MS teams.
We have added this feature to our backlog. Please keep sending your comments and votes, and we’ll update you here with our progress.
Joseph Doyle commented
Until we can migrate years of history from HipChat Server to Teams, we can't use teams.
Without a migration tool to go from Slack to Teams my company will continue using Slack.
Hi, same here, we're migrating everything from several system to microsoft suite (Google drive to One Drive, Slack to teams, etc..) and a the lack of a tool to migrate from slack to teams will most probably make us keep working with slack.
GIRAUD Alexandre commented
while don't have a migration tool from Slack, it's clearly not possible to plan using MS Teams at this time. It's really a have-to feature.
I've created a command line tool that lets you quickly re-create your Slack channel structure, and bulk create new channels in Microsoft Teams. The code is written in .NET Core and will run on Windows, macOS, and Linux. Functionality is limited by the available APIs (described above) and, hopefully to a lesser extent, my skillset. For the willing and able, my code is up on GitHub for you to try:
Not a nice solution, but as we needed to complete the migration and the only showstopper was channel history. (Compliance dump was backed up for all other purposes) what we've done is a one time export of the slack history of each channel into HTML format. Then rename it to .doc, which MS accepts as valid transition, and post it as a file on the new Teams channel Files folder. So at least there's a way to view and search for history for anyone who needs it.
Scott Hammer commented
Since the only solution up until this point seemed to create a document of your chats (from a previous platform) and attach them to a room as a word document, pdf, etc. I created 2 methods that will enable you to get your chats directly into MS teams and have them searchable. It's certainly a little hacky and will require development experience.
You know, you could require that the Team be already created before importing (if it's easier for you). I think it's a better UX if I don't need to check a "Slack archive" Team for historical information. If you don't remember where the latest information is, you'd need to search twice.
Assuming the Team is already created.
Here are a few potential workflows:
- Start importing Slack channel content
- Get Slack usernames/ids and ask the user to match Slack info to Teams info.
- Ask how to deal with Slack users that are not in the Teams channel: add to the channel (provide the interface to do so at some point), keep name without linking (for example: past employees, or people that are not in the new team structure), do not add to chat history. Bonus points: create a secondary export with the selected, unmatched usernames so they can be imported to another channel.
- Provide a specific format for an import file.
- Let people do their ETL to match.
All I want is the history somewhere in the Team space. If it's easier to import to a read-only "Slack archive" channel(s), it works for me. In this case, it may be possible to skip the "match Slack usernames to Teams users" step. Depends on what usernames people had on Slack (i.e. could you match it to a person without a lookup table?).
Scott Hammer commented
I have 2 solutions for importing hipchat into MS teams. I am going to create a blog entry today and will post the link to share with everyone.
Honestly, just getting the information/conversations into Teams in a format that can be accessed and searched is the most important to me. It doesn't need to be a true Teams chat/conversation, rather just the text with date and time information. Right now we are exporting out of Skype using a 3rd party tool and into excel. From there we importing into the FIles tab in Teams. This is not an ideal situation.
We can certainly do this by using CURL and using WebHooks. So, we can export using JSON and then using CURL.exe. we can push those messages as WebHooks into Teams Channels
We can certainly do this by using CURL and using WebHooks. So, we can export using JSON and then using CURL.exe. we can push those messages as WebHooks into Teams Channels.
Same for our company. Too much collaboration content would be lost without the ability to migrate.
Without a feature to migrate channels from Slack, it would be a very slim chance for a migration to Teams within our company.
This is a big one for our office as well. We can't migrate without our slack history.
Alan Miller commented
This would be very useful for us in the near future. It gives us the option to migrate from Slack. Otherwise it could be a deal-killer.
Dave Jackson commented
This will be great, would be good to include Skype Consumer in this group to consider for those that are using it within work
I would also like to be able to import from basecamp and excel into MS Teams. Has there been any further development in that regard?
We would migrate if this were an option.
The Teams adoption would be much easier if we didn't have to worry about losing chat history from Slack.