# Albato

> How the remote team behind the largest automation platform moved to Pachca. Read the full Pachca customer story.

Источник: https://pachca.com/en/blog/customers/albato

## How the remote team behind the largest automation platform moved to Pachca

Industry IT

Switched from Slack

![Albato](https://pachca.com/assets/cases/albato-header.avif)

### **About the company**

Hi! I'm Alexander, CEO and co-founder of Albato. We build a no-code automation platform that helps businesses connect different services without programming. Our team is fully distributed, with people working from different cities and countries.

### **Life before Pachca**

Before Pachca, we used [Slack](https://pachca.com/en/help-center/administration/import-slack) for all internal communication. For a distributed team, the chat app is the main way people talk to each other, so we were very picky about the alternative. Once it became clear that Slack might become unavailable, we started looking for a replacement ahead of time.

The main challenge was finding a service that matched Slack on features and ease of use. We tested several Russian products, but many were either too basic or overloaded with features we didn't need.

### The moment we knew Pachca was the one

When we saw that Pachca had everything we needed: [threads](https://pachca.com/en/help-center/features/kak-ustroeny-tredy-v-pachke), integrations via the [API](https://dev.pachca.com) and easy [video calls](https://pachca.com/en/help-center/features/videochat). But most importantly, the Pachca team was really responsive to feedback. As an automation company, we know how much a solid API and flexible integrations matter, and Pachca delivered.

### **How Pachca changed the way we communicate**

For a distributed team, it's critical that all communication stays structured and transparent. In Pachca, we kept every workflow we had in Slack and even improved some of them.

[Cross-chat threads](https://pachca.com/en/help-center/features/kak-ustroeny-tredy-v-pachke) turned out to be really handy for working across teams. Now you can bring a specialist from another department right into the discussion without creating a new chat or losing context.

We also rely heavily on [tags](https://pachca.com/en/help-center/administration/tags-team-members) to manage access, which made onboarding new employees much simpler. People automatically land in the right chats based on their role.

### **Tips for switching**

The key is to take your time and test everything in advance. We created a test [workspace](https://pachca.com/en/help-center/features/rabochie-prostranstva-v-pachke), invited part of the team and worked in both apps side by side for a few weeks. That helped us catch every detail and get the team ready for the switch.

Be sure to plan your chat and [tag](https://pachca.com/en/help-center/administration/tags-team-members) structure before the migration. When everything is ready, the move goes much more smoothly. And don't forget about [data import](https://pachca.com/en/help-center/administration/import-slack): being able to keep our message history made life a lot easier.