Well, yes, some of that social ‘cost of leaving’ plays a role. Yet:

It’s part of my company’s journey to better information security and data protection. Leaving silo’s, and Slack is just as much one as is Facebook, although with a different business model, is part of that. Similarly we’re starting to use our own cloud, in order to not use Google docs, Onedrive and the like. Our clients have different (and contradictory) rules against some of those silos, and we want to offer our own environment in which we can collaborate with clients as well. So our cloud and our Slack replacement run on our own server in a Dutch data center. This makes it easier to show GDPR compliance as well.

Within the company I’m the only heavy Slack user, taking part in about half a dozen Slack spaces. Still 90% of my Slack interaction is within my company.

Importing our Slack history into Rocket.chat, as well as that the URL of our Rocket.chat space is called Slack, help make a soft landing. Similarly Rocket.chat’s interface is similar to Slack’s.

Our cloud integrates well with Rocket, better than with Slack.

For mobile having another app on it is hardly an issue, given we all have half a dozen chat apps on it already.
For desktop it will be less automatic to make the switch, but adding Rocketchat to the dock will help.

So, there will be an adaption cost, but I’m optimistic it will be low, given our starting point. Over time I’ll reflect on how it went.

Screenshot of Rocketchat with previous Slack historty loaded

Replied to a post by Frank Meeuwsen

Wat me bij deze diensten toch erg interesseert is de kosten van overstap voor de overige gebruikers. Met name de mentale overstap. Ik kan me voorstellen dat je huidige conversatiepartners in Slack zelf ook meer Slack-koppelingen hebben. Dan is het handig om alles bij elkaar in één Slack app te hebben. Rocketchat voelt dan als “weer een extra app” wat transitie en acceptatie lastiger kan maken. Ik ben benieuwd hoe je daar mee om gaat!