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.
The feature team is still considering this item. No confirmation yet.
Not needed. If you really want to preserve your past chats, save them and archive them inside a file in Teams.
Igor B commented
this should be an option in mover.io :)
John Smith commented
Don't swap, you won't like it
teams feels like its way behind in actual use, it tempts with practical integrations without any real value, they just sound nice
in practice you end up using a lot more time to solve the same tasks or to communicate the same information, its simply not efficient in use
I suspect many people that started with teams will move to slack if they ever get their chance to try it out.
As others have pointed out, the best bet is to stay with slack.
Taylor M commented
This is a must for capturing the customers looking for more reasons to move off of a fragmented setup like GSuite, Slack, Dropbox, and consolidating down to Microsoft 365. We need more migration tools (or more APIs to build our own)
finding difficult time to migrate history form Slack to teams without any tools. if Microsoft provide tool it will be helpful.
Sameep Mishra commented
Guys, please confirm if Microsoft is working on it.
use AvePoint's FLY.
Lots of Office 365 Users would greatly benefit if a feature like this would be available so we can migrate to Teams from other messaging platform.
Being able to transfer chat history from Slack to MS Teams would be great. My team is not willing to move platforms without the history.
Slack to Teams, please. This will gain you more customer!
Any new Updates???
Lukas Schmölz commented
think about import option from Ryver as well!
Finally we've added file attachment import support for our HipChat to Teams Migration Utility, check out the new release here: https://github.com/Lombiq/HipChat-to-Microsoft-Teams-Migration-Utility/releases/tag/v0.4.0-beta
Working with company moving to Teams from HipChat, in fact this is the sole reason for the implementation. Would love to see help!
Now we've released a new version of our HipChat to Teams Migration Utility with which it now has a decent amount of features: https://github.com/Lombiq/HipChat-to-Microsoft-Teams-Migration-Utility/releases/tag/0.2.0-alpha Most of the remaining tasks are however issues we can't resolve because the Graph API lacks respective support: https://github.com/Lombiq/HipChat-to-Microsoft-Teams-Migration-Utility/issues So again it would be great if Microsoft could chime in Warren!
If you need assistance with the app you can open issues on GitHub or let me know: zoltan dot lehoczky curything lombiq dot com.
Glenn Mckenna commented
Could we please have an update ?
We couldn't wait, so now we're releasing a free and open source utility to migrate from HipChat! Check out the blog post with the details: https://lombiq.com/blog/introducing-our-hipchat-to-microsoft-teams-migration-utility
It's not yet complete but nevertheless something you can already try. All feedback and contributions are warmly welcome!
Also, Microsoft, Warren! Why the tool doesn't do everything that we've already implemented is because the Teams API doesn't allow everything it needs. So you could help greatly by improving the API (and feel free to contribute to the app as well :)).
Robert Downey commented
Zero chance we can move to Teams while there is no ability to import data from Slack. We're ready and waiting. I'm sure many, many others are in this same situation.
Eagerly waiting to migrate to Teams, please provide necessary tools. Thanks.
Esam El-Olemy commented
We are using Hipchat and considering Slack and MS Teams for a replacement. We need to take a decision by end of December to be able to implement during January 2019.
chat History and contents are critical.
Slack provides the migration path. MS Teams still no word on it.