Unisender
How the Unisender team moved from Slack to Pachca and kept all their processes and chat history
About the company
Hi, I'm Zhenya, Head of HR at Unisender. It's a Russian email marketing service that helps businesses stay in touch with their customers, automate processes and grow sales. Our customers send more than 1.5 billion emails every month.
Life before Pachca
News that Slack was leaving Russia and deleting workspaces without warning kept coming up in both 2022 and 2023. We had no illusions: sooner or later we'd have to part ways with the platform we were used to. So by spring 2024, we were actively looking for somewhere to move.
First we tested one of the popular Russian business management services, but it didn't have the features we needed, and fitting it into our workflows would have been expensive. Top management and team leads turned it down and decided to look for a more specialized solution.
We didn't want to put up with a ton of inconvenience or get used to a service that isn't really a Slack alternative and works in a completely different way. So our requirements included threads, public and private chats, integrations and more.
The moment we knew Pachca was the one
Pachca feels a lot like Slack, so it didn't take long to get used to. We started moving just a couple of days after testing, and the whole process was as smooth as it gets. We also like that our feedback can shape the product roadmap.
How Pachca changed the way we communicate
Most importantly, we kept all our processes and chats. Our people moved into a convenient, feature-rich workspace that feels a lot like Slack.
As for differences, Pachca has tags. They make it easy to add people to new chats.
We also like that there are two types of chats: public and private. We create them for specific tasks or for casual chats with colleagues, like learning together or team building.
Tips for making the switch
If your company has 150 employees (like ours) or more, be sure to bring the leads of every department into testing. Every department has its own processes, and their feedback may differ.
It's best to involve your tech team in the move itself. If you're migrating from Slack, you need to bring over all your data so nothing gets lost.
Even if you can't import your message history, it's important to recreate all the familiar chats in your new workspace. That way, the move feels comfortable for every team.
