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.
Charles Ulrich commented
Trying to convince my HipChat users to come to Teams instead of moving to Slack. They have already imported HipChat history into Slack and I need this functionality to convince them to come to Teams. Now is the time to release this feature if ever.
Is there anyway to import from Hipchat into Teams?
Slack just bought HipChat and we are trying to decide between Slack and Teams. Microsoft if you don’t put all hands on deck to make an import from HipChat into Teams, you are going to miss the opportunity of the century. Please build this ASAP!!!
Bradley Bristow-Stagg commented
Yes it's certainly something that we are looking into again since Slack bought HipChat. We have a choice to either migrate to Slack or to Teams and I need to find the right tool for us to use. Slack already supports imports so that's a big tick in their favour if we decide that we want to retain our history.
Hipchat just sold to Slack (https://www.atlassian.com/blog/announcements/new-atlassian-slack-partnership). This would be a great time to provide a Hipchat -> Teams migration tool....
peter lwin commented
same problem here. currently using Asana. want to migrate to teams.
Ravindar Mettu commented
We are planning to move from Slack to MS Team. We want all users and channels data and chat history to be migrated to MS Teams.
We are using O365, Salesforce CRM and Chatter, considering to move to D365 and Team. Pls make importing from Salesforce Chatter possible for stealing customers from Salesforce not just for Team but also for D365!
Need same for Facebook workplace to Teams.
It would be massively helpful to import the channel structure and archived messages into Teams from Slack. We have ~500 users that are waiting for a way to do this before they jump on
Making the switch over from Slack as seamless as possible would almost certainly cause us to switch to Teams.
Ari Shinozaki commented
I'd really like our company to use Teams if we can have some cross integration or channel migration with slack. But for now we are on Slack as has extensive channels on topics we need to maintain.
Going to look at trying this out. If anyone has any success please post feedback!
Adam Stephan commented
We used Slack for internal support communication. There were useful threads started in slack that we used to help solve technical issues and it became an answer repository for other technicians. We migrated to Microsoft products and adopted Teams, but we lost the history we had created in Slack and it would be nice if we could keep all that information in the new (Teams) messaging app to make the transition easier.
Great to hear that you're reviewing this. It'd be great to be able to import our Slack conversations into Teams, it's been one of the main things keeping us from switching.
Howard Weinstein commented
Any progress on this? We have a client who wants to migrate from Symphony to Teams but without the import feature I am not sure if they will make the move
Angelo Lakra commented
After six months of checking this thread, I was hoping someone had a solution, but this doesn't seem to have happened yet.
We were using Slack and a company came along and bought us. They use Skype and Teams for all group chat communication.
We though that we had to switch over to Teams, but we were told several months later that we would remain on Slack.
Today, I work across two different services, Slack and Teams, to communicate to different parts of the company. I don't know if this will continue as our teams get more integrated, but we'll see.
Regardless, in those few short months, I was racking my brain on how to import our historic chat data into the threaded format that Teams uses. This seems possible by reformatting each channel's history for it to make sense in a threaded context.
The first obstacle I ran into is that I don't have the time to do that. As a realistic example, if four people are having two different conversations in the same channel in Slack, how should that look in Teams? I can create two threads with the correct context so that each thread has the correct participants, right? What if one of the users decides to answer both users across the conversations on the same message? I can solve this by creating a single thread, but I cannot come to that conclusion without grasping the context of the conversation. Manual refinement doesn't scale well for large archives of chat.
If you make every message you want to import into it's own thread, then it could work, but this doesn't look right in Teams because you end up with a ton of single message threads that are linked or not linked by conversation. You won't know unless you read each one because they aren't grouped.
The second obstacle I came across were the missing import features of the current API. I cannot import messages with backdated time stamps. I cannot easily assign authorship of past messages to current users without some type of credentials from that user. And the most problematic, I cannot create more messages within a thread other than the first one from the API.
According to the API documentation (as of Jan 2, 2018), none of this is straight-foward or even possible with the Microsoft Graph Beta API for Teams. See https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/resources/chatmessage and https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/api/channel_post_chatthreads
So, even if you are a good programmer and you have all the historical chat data structured in a threaded way, you're blocked until they add support for these needed features. If I'm wrong about this, please do post about it and correct me.
Having assessed the import situation, it might be useful to think through a few questions for creating alternative solutions:
1) Why do you want to preserve your old chat data? This might be seem obvious, but asking it will actually pinpoint the value you want to retain for your organization.
2) Do you have a business requirement that requires that this data be readily available? Is not having this chat data available causing your business to suffer in some way? This can help your prioritize how badly you need this functionality.
3) When you do finally get your data imported, what minimal viable functionality do you need to get the value from your historic chat data? Is search and retrieve enough? Do you need some sort of heuristic process to get deeper knowledge out of your data?
4) Are there other ways that you can utilize your historic chat data out-of-band from your previous chat provider and Teams? Can your organization provide an in-house solution for querying your historic chat data? Or would you be willing to work with a third-party who can build a solution for you?
I think if you can at least answer these questions, it will at least be clear if pursuing an import strategy is worth it or not. For me, it turns out that I didn't need to, but that could change as the company I work for integrates its tooling more tightly.
Now, not all is lost, there are some other handy features of Teams that can be utilized to get your historical chat data into usable places. Tabs seems to be the most viable because you can build a custom web service somewhere on the internet and serve your content contextually to a tab tied to each channel.
This content could be as simple as a flat plain text log of all the historical data for the slack-equivalent channel or you can add search features. It's up to you. I really believe this is the correct way to solve the migration problem because you aren't beholden to the constraints of Teams.
I would love to hear further thoughts on this.
We are using Flowdock and have been asked to migrate to Teams. When do you expect to have your migration tool available for general use? For beta? Thanks
Private channels and content migration is absolutely important for a smooth transition from Slack to Teams. However, I was told it is slack who doesn't open up APIs for import data out. We are planning to minimise our Slack presence to only engineering and wait until there is a plan for them
Hi Suphatra, in response to you request for ideas of work-arounds - we don't necessarily need to have a tool that will create Teams and channels automatically based off existing Slack channels. If we could do this on a channel by channel basis, that would be fine in the interim - e.g. I create a Team, then create a new channel in the Team, and from there select a Slack channel to import from.