Tips and demo are probably my most favorite sections on any website, especially so for productivity tools. I’m glad to see that Slack Tips are now launched as well, with a collection of simple, yet powerful recipes on how to make everyone’s life easier.
HipChat to Slack migration
Back in July, Slack acquired Hipchat with the intent of migrating all the users and shutting down the service. For us at work, these were very sad news. We’ve been using HipChat for years, and relied on it heavily. We have also evaluated Slack in its early days and didn’t quite like it at the time.
Once it was clear that the HipChat is going away, we had a couple of options to consider. One was to move to Slack. Another – to migrate to a different solution, preferably to a self-hosted one, like Rocket.Chat.
So, first thing we did, was another test trial of Slack. We were glad to see that it matured and improved a lot over the last few years, and that it would be faster and easier for us to move to Slack rather than to roll out our own self-hosted solution.
Here are a few things that we had to keep in mind for this migration:
- We have a rather small team – about 15-20 people altogether, but with a very mixed backgrounds. Some are very technical, some are not. Some are on Windows, some on Linux, and some on MacOS. Mobile use is also heavy across the board.
- We are working with a lot of rooms/channels. We have a few generic ones, like Support, Sales, Management, etc. And we have a separate channel for every project. And those we have over a hundred of.
- We have a number of integrations connected – GitHub and BitBucket repositories, Zabbix monitoring system, RSS feeds, deployment automation, etc.
- HipChat would only be around for the next month. Not a tight deadline by our means, but the timeline is important here.
Since the time was limited from the beginning, we decided to start with the migration pretty much immediately, rather than waiting until the last moment. In case something wasn’t working, we’d have some space to maneuver.
Instead of a once off switch, we also decided to do a gradual migration, shifting from HipChat to Slack bit by bit, using both services in parallel.
Creating the new workspace and registering all the users was, as you can imagine, the easiest part. After all we do have only a small team, and that many accounts can be done manually, without any automation what so ever.
That was an option for the rooms/channels though, as we have hundreds of those. Gladly, both Slack and HipChat provide an API which helps with automation, and we have awesome DevOps who handle things like that.
Here comes the first issue that we came across. HipChat allows for much more when it comes to room names, than Slack. Slack channels are limited to 21 characters (which is not a lot), and the selection of the characters is much less also (dashes are in, but slashes and other special characters are out).
That meant that we had to come up with the new naming convention, which we did. We also used this opportunity to consolidate some of the HipChat rooms into fewer Slack channels. In HipChat, as I mentioned, we had a separate room for each project. Which was handy for busy projects, but somewhat confusing for smaller projects that belonged to the same client. For example, it’s not a rare occurrence for us to have two, three or more projects for a single client. And while they are all different, often they overlap a lot (websites for a group of company, or a website integrated with the CRM, etc).
Once we decided on the adjustments to the naming convention and consolidation of some rooms, the migration wasn’t too difficult, given the API of the both services.
Next came the integrations. This is where, I have to say, Slack shines. While HipChat integrates with both BitBucket and GitHub too, the functionality provided by Slack is a lot better and easier. Both GitHub and BitBucket are available out of the box, so we quickly connected all the project channels to their appropriate repositories.
RSS feeds weren’t a problem either. So the next one that we had to do was the Zabbix monitoring system. Again, Zabbix is pretty good with integrating to other systems, Slack API is flexible, and our DevOps are amazing. So that took no time at all. In fact, we even made it better, since Slack allows for richer and better notifications.
The last, but the most important one, was our deployment automation. It wasn’t painful, but it did require us to do some adjustments. Some of these we wanted to make for a while now anyway. The biggest change was that HipChat didn’t care about the long running tasks, while Slack expects an answer from your webhook within 5 seconds. Many of out deployments take longer than that (some are up to 20 minutes), so we had to do some changes.
When the chat webhook request for deployment is received, we couldn’t wait for the deployment to finish anymore to send the response back. We had to respond within 5 seconds. That meant that we had to disconnect the actual deployment run from the chat communications. As I said, we wanted to do that for a while anyway. A quick proof of concept with the Linux “at” command worked quite well, so stayed with that for the time being. Now when the request is received, the deployment is scheduled with the “at” command for the next minute, and the response is sent to the chat within a second.
That was about it. Since we didn’t care about migrating the actual chat histories or uploaded files or anything like that (we use Redmine for anything that needs persistence), the migration overall was smooth.
Once all the users were registered, channels created, and integrations configured, we started to phase out HipChat rooms one-by-one, archiving and disabling them on HipChat and pushing users more and more towards Slack.
Overall, the setup and configuration took us about three weeks. The rest of the migration with the users and phasing out of HipChat took approximately another two weeks.
So, now that we’ve been using Slack exclusively for about a month and a half, how do we find it? I think overall it’s a lot better now that it was with HipChat. Here are some of the benefits:
- The mobile app is amazing. It supports multiple workspaces (some of our clients are also using Slack and we need to be in multiple places at the same time), has a great user interface, and, most importantly, the push notifications are working A LOT BETTER. HipChat had a tendency of going offline after about 10 minutes and being completely silenced until the next manual check. Slack even provides a Snooze option for 20 minutes, 1 hours, etc, which makes it easy to silence it during a meeting.
- Slack desktop and web applications seem to be better enjoyed by non-technical users, than their HipChat alternatives were. For me personally, HipChat was easier on the eye, but Slack provides a lot of functionality which wasn’t in HipChat.
- Threads! I think this is one of the greatest features that HipChat was missing. Project rooms especially can get quite noisy. It’s often difficult to follow up with all the chatter. Threads make it a lot easier. With threads there can be multiple concurrent conversations in the same channel without any confusion or overlap.
- Reminders! Again, for those of us who are busy with a million things, reminders in Slack are a killer feature. They help to find that message that needs a response, half an our later, in a hundred rooms with dozens of conversations going on at the same time.
- Slash commands. While both HipChat and Slack have them, Slack allows to send the same slash command from any room (handy for deployments). With HipChat we were a lot more limited, which pushed us into a separate room for all deployments.
- Emojis. Usually, I’m the last person to use emojis. I’m the old school smiley guy. But in this particular context, I find emojis to be very useful. They often save a lot of typing and help keep the atmosphere nice and friendly. HipChat had a very weird approach to emojis. While they were there, they were very few, and very custom to the HipChat team. We did upload a lot of our own over time, but with Slack that wasn’t necessary.
- Stats and analytics. Slack provides a great insight into how the workspace is being used. Stats are available both as an admin menu item, and as a quick weekly email.
- Integrations and API. Slack provides a much more flexible API and integration options. While we were doing fine with HipChat, I think all of our integrations are much better now because of the move to Slack. (slash commands, updated messages, message replies, file attachments, rich messages, etc).
As I said, overall the migration went quite smooth and we are in a much better place now. This is quite surprising and refreshing, especially after us considering the news of HipChat acquisition as a sad story. In fact, I can’t remember, from the top of my head, when a sad story like this turned out to be such an improvement.
Thank you HipChat team for all the effort – you’ve been great for the last few years. Thank you Slack for making things even better!
Zulip – Open Source team chat with threads
Zulip is yet another Open Source team chat solution (much like Rocket.Chat). It has a number of cool features, including Markdown support for messages and drag-n-drop uploads, numerous integrations, and can be used as a self-hosted solution or as a SaaS.
Botman – framework agnostic PHP library to build chat bots
Botman is a framework agnostic library for building your own chat bots in PHP. With the same chat bot logic you can connect to a variety of chat services like HipChat, Slack, Telegram, Facebook Messenger, Google Hangouts and a variety of others (just search for “botman/driver” on Packagist). You can also build your own drivers for the services which are currently not supported (can’t think of one top of my head), or simply integrate it with your website.
I came across this library via this article.
Is group chat making you sweat?
Jason Fried has an excellent write-up on the pros and cons of using group chat for the team communications, and some of the ways to make it better. We use HipChat in the company and while it’s vital to our operations and I can’t even begin to think how we could do what we do without it, it does have some negative side effects – exactly as James describes them.
The most valuable advice out of that long article is this one (I’ve heard it before a few times, but it’s worth repeating):
Think about it like sleep. If someone was interrupted every 15 minutes while they were trying to sleep, you wouldn’t think they’d be getting a good night’s sleep. So how can getting interrupted all day long lead to a good day’s work?