JVO
How JVO moved 200 employees from Telegram to Pachca in 2 weeks. A story about migrating a fast-growing IT team and automating workflows through the API
About the company
I'm Igor, CTO and co-founder of JVO. We build end-to-end analytics for e-commerce sellers on marketplaces like Ozon and Wildberries. We import as much seller data as possible, automatically spot growth opportunities and give clear recommendations, from out-of-stock forecasts to specific tasks on assortment and pricing. We also have an AI agent that helps manage prices flexibly based on a set strategy, helps respond to reviews and automates routine operations work.
Life before Pachca
We worked in Telegram for a long time. We started thinking about moving last year, when our team grew past 30 people. We were growing very fast and knew headcount would be close to 200 by the end of 2024, so we had to make a call on a new team chat app quickly. At that scale, controlling who gets added to and removed from chats became a critical risk. You can't rely on memory and manual work. In Telegram, the problem was the lack of centralized management tools. Every offboarding or onboarding turned into a run through all the groups. On top of that, part of the team asked to separate personal and work conversations, so we specifically needed a team chat app built for work.
The moment we knew Pachca was the one
We quickly tested about five team chat apps. We were looking for a solid mobile app and a pleasant user experience. Pachca pulled ahead of the rest right away: we liked the UI and the overall experience. It mattered that you don't get tired of an app you spend your whole day in. So we made the decision fast. Automations sealed the deal: the open API and webhooks helped us move all our processes over and improve them along the way.
How Pachca changed the way we communicate
Most importantly, we brought order to our processes and sped them up. We now have all our discussions in threads, and that's a must-have for a team chat app. Access control stopped being a pain: we set up a chat structure, and now it's clear who posts where and who owns what. Tags also turned out to be a great fit for us: new employees are now added to the right chats automatically.
At the same time, we moved all our automations over from Telegram: bots, webhooks and API integrations. Alerts from external systems and incident monitoring now land right in our work chats, and the team handles them there without switching apps.
Tips for making the switch
We set up SSO right away and built the "skeleton" of the workspace in advance. We created chats for each department, set up shared channels like "Team News" and planned out tags so employees would automatically land in the right chats. A "Chat rules" channel also helped at the start. It briefly explained which channels exist and what they're for, and how to use tags and threads. We duplicated the same info in our wiki: a couple of screenshots, minimal text, only what you really need on day one.
In the end, the migration went fast and painlessly. When the structure and rules are ready in advance, people don't have to "reinvent" anything. They just open Pachca and get to work.
