How to migrate from Wati to Wando without losing conversations or your number

If you're reading this, you've probably already made the decision: you want to leave Wati. Whether it's because of the price, the English-only support, or because the entry-level plan became too small for you, the next step is to make the switch without losing a single conversation or your WhatsApp number.

The good news: migrating to Wando doesn't mean starting from scratch. Here we walk you through how it's done, step by step, what you need to prepare, and what limits exist so you don't get any surprises.

First things first: your WhatsApp number stays untouched

Wati and Wando use Meta's official WhatsApp API. That means your number isn't 'trapped' in Wati: the number is yours and you can move it to another provider whenever you want.

The typical process is: in Wati, you release the number (disconnect the integration). In Wando, you connect it with the same number using the QR code or the steps the platform gives you. You don't lose your number or your chat history on your phone.

Keep in mind: what doesn't migrate automatically is the conversation history inside the platform. The chats you have in Wati are not exported to Wando. But since the WhatsApp API stores conversations on Meta's side, your customers still see the same chat as always.

Prices, verified one by one

• Wati Growth: US$45/month paying annually — 3 users and 500 active contacts, with no option to add more.
• Wati Pro: US$95/month — US$24 for each extra user.

• Wando Starter: US$12.99/month — 500 contacts, 1 user.
• Wando Pro: US$26.99/month — 5,000 contacts, 3 users.
• Wando Enterprise: US$66.99/month — 25,000 contacts, unlimited users.
• Wando free trial: 14 days without a card.

What you'll need before migrating

To make the switch fast, have these on hand: admin access in Wati, your verified number in Meta Business Manager (or access to the Meta account you were using), and a list of your contacts exported in CSV.

In Wati, export your contacts with tags if you use them. You import that CSV into Wando and that's it: they keep their data and you can reorganize them with Wando's tags.

It's also a good time to review your message templates approved in Meta. If you have them approved, you can use them again in Wando: submitting templates in Meta can take up to 48 hours, but if they're already approved, there's no need to wait.

• Export your contacts from Wati in CSV.
• Disconnect the WhatsApp number in Wati.
• Connect the same number in Wando with the official API.
• Import the contacts CSV into Wando.
• Review your approved templates in Meta.

What changes in your day to day

The biggest difference you'll notice is in how conversations are handled. In Wati, the strength is the no-code flow builder: you build automations with logical steps. In Wando, there are no flows to program: the AI suggests responses based on what your team has already answered before.

In practice: when a message comes in, Wando shows you a suggested response. Your team approves it with one click or edits it. Over time, the AI learns from those real responses and becomes more accurate. You don't have to maintain a flow diagram.

Additionally, Wando adds channels that Wati doesn't cover: Instagram and Messenger from the same inbox. If you provide support there, it helps to have everything in one place.

What Wati does best (and why sometimes it's better to stay)

Let's be honest: Wati has a very mature flow builder. If your business depends on complex automations with branches, conditions, and a huge number of integrations, Wati can be the right tool.

It also has a huge number of integrations with third-party tools. If you use a very specific CRM or tools that aren't on Wando's list, take a close look before migrating.

Wando integrates with Make, Zapier, n8n, Slack, Google Sheets, and Mercado Pago. If your stack runs through those, you're covered. If not, consider whether Wati is still more useful for you.

The cost of switching

Wati is paid in dollars or euros and the entry plan does not allow adding users or contacts: if you grow, you jump straight to the highest tier. Wando starts with a more affordable plan and has a free 14-day trial with no card.

Plus, Wando is designed for Latin American SMBs: support is local and in Spanish. If you've spent afternoons translating Wati documentation, that's over.

For updated prices, check the plans at wando.online/pricing. We won't overwhelm you with numbers here because they change, but the entry-level difference is clear.

Migrating from Wati to Wando is a change of philosophy: you leave behind programmed flows for an AI that learns from your team. It's not for everyone, and that's fine. If your case is complex automations, Wati remains a valid option. If you want something simpler, in Spanish and with an eye on your wallet, Wando is waiting for you with a free trial.

What happens to active conversations during migration?

The most delicate moment of a migration is the cutover: while you disconnect Wati and connect Wando, incoming messages may go unanswered. The window is short, but it exists.

To minimize the risk, make the switch during a low-traffic time. If your business receives messages in the morning, migrate in the afternoon. If you have a team, give them advance notice so no one is caught off guard.

Once you connect the number in Wando, the messages that arrived during the cutover appear in the inbox. They are not lost: they stay pending until your team responds to them. The only thing you won't have is the full conversation history inside the platform, but the customer sees the same chat as always.

A concrete example: a coffee shop that migrated in one afternoon

Imagine a coffee shop with two locations that used Wati to answer orders on WhatsApp. They had 300 contacts, three users and a basic flow for hours and location.

The owner exported the contacts CSV, disconnected the number on Wati and connected it on Wando with the QR code. He imported the CSV, created tags per location and activated the auto-replies by schedule: outside business hours, an automatic message let people know they opened at 8.

The first week, the team answered messages by hand. The AI started suggesting replies based on those real answers. After ten days, 70% of replies were approved with one click. The number never went down and customers didn't notice the change.

The most common mistake: not disconnecting the number on Wati before connecting on Wando

If you try to connect a number that is already active on another Meta API provider, the connection fails or creates conflicts. Meta does not allow the same number to be registered on two platforms at the same time.

The solution is simple: on Wati, go to the WhatsApp settings and disconnect the number. Only then connect it on Wando. If the error persists, check that no other platform is using the number (for example, a phone with regular WhatsApp Business).

Another common mistake is migrating without exporting the contacts. The CSV is your backup: if something goes wrong, you don't lose the database. Always export it before touching any settings.

How to avoid the template configuration error

Message templates (HSM) are messages approved by Meta that are used to start conversations or send campaigns. If you have them approved in Wati, you can reuse them in Wando: there is no need to request them again.

The typical error is taking them for granted and discovering that they are not approved. Check the status of each template in Meta Business Manager before migrating. If any were rejected, correct them and resubmit them: approval can take up to 48 hours.

Also check that the templates use the correct format for Wando. If you have doubts, Wando's local support helps you configure them without hassle.

What to do if your team doesn't adapt to AI

Switching from scheduled flows to AI suggestions can create resistance. Some team members prefer to have everything under control and don't trust a machine that tells them what to reply.

The key is configuration: Wando doesn't reply on its own by default. The AI suggests, the human approves. Start with 100% manual approval and, as the team gains confidence, enable auto-reply only for repetitive messages (hours, location, prices).

Also help the team understand that the AI learns from them: every reply they approve or edit improves future suggestions. It is not a replacement, it is an assistance. If any member still feels uncomfortable, suggest they use the audio transcription feature: it listens to voice messages and converts them to text, which makes it easier to reply faster.