Number migration to the API
Number migration to the WhatsApp API (also known as 'number migration to the WhatsApp Business Platform' or 'cloud migration') is the process of transferring a phone number that is already registered in WhatsApp Business (the app or the web version) to Meta's official WhatsApp Business API. In plain terms: it means moving your number from the standard app to the platform designed for businesses, so you can use advanced features like sending bulk messages, managing teams, and connecting automation tools.
Why does it matter to an SME?
If your business already uses WhatsApp Business on your phone, you've likely run into limitations: you can't have more than one agent on the same account, there are no statistics, and message templates are limited. Migrating to the API enables you to use a shared inbox with multiple people, send campaigns, and connect tools like Wando, which learns from your real responses to suggest faster replies. Additionally, by using Meta's official API, you reduce the risk of your number being blocked for using unofficial apps.
How is it done? (general steps)
- 1Check that your number meets Meta's requirements: it cannot be registered in the WhatsApp Business app, and it must be a number you can verify (via SMS or call).
- 2Create a Meta Business account and set up the solution provider (e.g., Wando) that will give you access to the API.
- 3Request the number migration from the Meta Business panel. The process can take a few minutes or up to a few hours, depending on the number's status.
- 4Verify the number with the code you receive via SMS or call.
- 5Once migrated, configure your provider (Wando, for example) to start receiving and responding to messages from the AI-powered inbox.
The exact steps and requirements may vary depending on the provider and region. Always check Meta's official documentation to avoid outdated information.
Common errors
- Not verifying the number before migrating: if the number is verified in the WhatsApp app, the migration fails or gets temporarily blocked.
- Migrating a number that isn't yours or is in use by another WhatsApp account.
- Not having the API provider ready before migrating: you end up unable to use the number until you set everything up.
- Thinking the migration is automatic: it requires manual steps and can take up to 48 hours in cases of template review, although the migration itself is usually faster.
In short, migrating your number to the API is the logical step if you want to scale customer support. Tools like Wando leverage that API to give you response suggestions that learn from your own style, without you having to program anything. That said, migration requires a bit of patience and following Meta's steps to the letter.
How it's used in practice: a real example
Imagine a real estate agency in Buenos Aires with three agents. They have a single WhatsApp Business on a phone, and when one is attending, the others can't see anything. They migrate the number to the API and connect it with Wando.
Now, when a message arrives, the AI suggests a response based on the ones they've given before. The agent approves it with a click and that's it. If it's a query about a listing, Wando learns from the tone and data they always use. Also, all three see the same inbox, so no one steps on anyone's toes.
For campaigns: they load contacts into Google Sheets, Wando syncs them, and they send a mass message with a template approved by Meta. The statistics show how many responded, and audios are transcribed automatically to avoid wasting time listening.
What it's confused with and how it differs
Migration to the API is confused with two things: changing your number (portability) and using unofficial apps like WhatsApp Plus or modified versions.
Portability is changing your number to another phone provider, nothing to do with it. Here the number stays the same, only the platform that manages it changes.
Unofficial apps are a risk: Meta can block them, and they don't have access to the official API. Migrating to the API, on the other hand, gives you legal and stable access to features like templates, campaigns, and multi-agent. The key difference is that migration puts you into Meta's official ecosystem, with support and updates.
It is also confused with 'registering a new number on the API'. Migrating is when it's already on the app; registering is when you start from scratch. The steps are different, and it's best not to mix them up.
What happens if you don't migrate: the concrete consequence
If you don't migrate, you're stuck with the WhatsApp Business app and its limits. The most painful one: a single agent per account. If your business grows, customer service becomes a bottleneck.
You also can't connect tools like Wando, which need the official API. Without migration, there are no AI suggestions, no mass campaigns, no statistics.
And the risk of blocking: if you use unofficial apps to make up for those features, Meta can ban your number. That means losing contact with your customers overnight.
In short: not migrating leaves you stuck in a model that doesn't scale, and pushes you toward risky solutions. Migration is the step to operate as a business, not as an individual.
Relationship with Meta's official API
Migration is the bridge between the common app and Meta's official WhatsApp Business API. Without migration, there is no API.
The official API (WhatsApp Cloud API) is what enables everything the app doesn't: templates, campaigns, multi-agent, integrations. Meta offers it through solution providers (BSPs), such as Wando.
When you migrate, your number is registered on Meta's platform, and the tools you use (Wando, for example) connect to that API to manage messages and contacts.
One detail: Meta's conversation prices vary by country and are not controlled by Wando. It's always a good idea to check the official documentation to stay up to date.
Wando uses the official API, so your number is within Meta's ecosystem, with support and updates.
When NOT to migrate
Migration is not for everyone. If your business is small and you handle few messages per day, the WhatsApp Business app may be perfectly sufficient for you.
It's also not advisable if your number is heavily tied to a manual process you don't want to touch, or if you don't have time to set up the API and the provider.
Another case: if you use the number for personal and business use mixed together, migrating separates things and can be a mess.
And if you don't have a budget for a provider like Wando, the free app is still a valid option. The API has Meta conversation costs that vary by country, so you need to calculate.
In those cases, staying with the app is not a mistake. Migrating is for businesses that need to scale support and are willing to invest time and money.
Common mistakes of those who just understand it
The biggest mistake: thinking that the migration is automatic. It is a manual process that requires following Meta steps and having the provider ready.
Another one: migrating without verifying the number first. If it is verified in the app, the migration fails or is temporarily blocked.
Migrating a number that is not yours or that is in use by another WhatsApp account is a legal and reputational problem.
There is also the one who migrates and does not configure the provider: they end up without being able to use the number until everything is ready.
And the one who expects chats to transfer on their own. That's not the case: you have to export them beforehand if you want to keep the history.
Finally, not reading Meta's documentation. Requirements change, and outdated info can make you waste time.
Frequently asked questions
How long does number migration to the WhatsApp API take?+
The migration itself usually takes between a few minutes and a few hours, but it can take longer if Meta needs to review the account or templates. The typical timeline for template approval is up to 48 hours, according to Meta's official documentation.
Can I migrate a number I already use in WhatsApp Business on my phone?+
Yes, but you have to stop using the WhatsApp Business app on that number before migrating. Meta allows migrating numbers that are registered in the app, but the process requires that the number is not active in the app at the time of migration.
Do I lose my chats or contacts when migrating to the API?+
No, chats are not lost, but they are not automatically transferred to the API. When migrating, the number is linked to the API platform and you can continue seeing messages from your provider (like Wando). To keep the history, it is recommended to export the chats before migrating.
Is migrating to the API mandatory to use tools like Wando?+
Yes, to use the official WhatsApp API (and tools that connect to it, like Wando), you need to migrate your number to Meta's platform. You cannot access the API using a number from a regular app.
How much does it cost to migrate a number to the API?+
The migration itself has no cost, but Meta's API charges per conversation and prices vary by country. Additionally, a provider like Wando has its own plans. Check current plans at wando.online/pricing and Meta's official documentation for conversation costs.
Can I go back to the app after migrating?+
Yes, but it is not an instant process. You have to unlink the number from the API and register it again in the app. That can take time and is not always straightforward. Better think it through before migrating.
Does migration affect my saved contacts?+
No, contacts are not lost. They remain on your phone or in your CRM. What is not automatically transferred is the chat history. Export them beforehand if you need them.
Do I need a provider to migrate?+
Yes, Meta requires you to use a Business Solution Provider (BSP) to access the API. Wando is one of them. Without a provider, you cannot connect your number to the API.
What happens if my number is in the regular WhatsApp app?+
You can migrate it, but you have to stop using it in the app before starting the process. If it is active, the migration fails or is temporarily blocked.