"WhatsApp migration" means four different moves, and most guides answer the wrong one. Moving from the consumer app to the Business app is a settings screen. Moving from the Business app onto the API is a registration. Moving a WhatsApp Business Platform account between providers is Meta’s formal account-migration process. And moving from On-Premises to Cloud API is a hosting change. This guide covers all four, what survives each move, and where data actually gets lost.
The four migrations, and which one you mean
App to Business app
Same phone, in-app transfer, chats and media come along. Free, ten minutes, reversible with a backup.
Business app to the API
The number registers on the WhatsApp Business Platform and the app stops working on it. Contacts import into the platform; export the app’s chat backup first.
Provider to provider (BSP migration)
Meta’s account-migration flow. The number, tick, rating and tier move; templates resubmit; lists and flows rebuild. This is the move most businesses searching "WhatsApp API migration" need.
On-Premises to Cloud API
Meta retired On-Premises hosting, so remaining installations must move to Cloud API. Same account, new hosting, webhooks re-pointed.
What survives, what is rebuilt, what is lost
Three categories decide whether a migration feels safe. Survives automatically: the phone number, display name, official business account status, verified badge, quality rating and messaging tier, all properties of the number and the WhatsApp Business Account in Meta’s systems. Rebuilt during migration: approved templates (resubmitted, usually re-approved quickly because Meta has already approved the identical content), chatbot flows, integrations and webhooks, and contact lists with their tags. Lost if unplanned: chat history held only inside the old provider’s dashboard, which must be exported before access ends. The one-week window after cancelling a provider is the wrong time to discover their export button produces a PDF.
The provider-to-provider process, step by step
Where migrations actually go wrong
- Ownership surprise: the WhatsApp Business Account sits in the provider’s Business Manager, not yours, and they are slow to release it. Check ownership before you resign.
- Verification code access: the migrating number cannot receive the SMS or call, because it is a landline extension or the SIM is in a drawer.
- History not exported before dashboard access ended.
- New number instead of migration: starting fresh resets the messaging tier to 1,000 a day and abandons the quality rating you built.
The longer versions of these are catalogued in top 20 WhatsApp API migration mistakes and the 10-point migration checklist.
Who to migrate with
Any destination provider can technically receive an account migration; the difference is who does the rebuilding work and what it costs. WappBlaster includes the full migration, audit, template resubmission, flow and integration rebuild, list import and the number move, in the flat ₹7,999 / $200 a year licence, done with you on a call rather than left to documentation. The comparison of migration-capable providers is in top 5 WhatsApp API migration providers in India, and switching BSPs without downtime covers the zero-downtime sequencing in more depth.
Next step
Ask for a written migration plan for your account from the WhatsApp marketing API page. It lists what you have today, what carries over, and the exact maintenance window, before you commit to anything.