Moving your WhatsApp number to another provider
It is a migration, not a settings change. What you need to own before you start, and the one question that decides whether it is even possible.
Changing WhatsApp providers is not a settings change. It is a migration of a number your customers already have, and how painful it is was decided when you signed up with the first one.
The question that decides everything
Is the WhatsApp Business Account in your own Meta Business Manager, or in your provider's?
If it is yours, migration is a supported process: you disconnect from one platform and connect to another, keeping the number, the display name and the verification.
If it sits inside your provider's Business Manager, you are dependent on them to release it. Most will. Some are slow about it. Either way you are asking permission to leave, which is a bad position to negotiate from.
Check this today, whether or not you plan to move. If it is wrong, fixing it while everyone is happy is far easier than fixing it during a divorce.
What travels and what does not
- Travels
- The number. The display name and its verification. Your green tick, if you have one. Your quality rating and messaging tier — these belong to the number, so you do not restart at the bottom.
- Usually has to be recreated
- Message templates. They live against the WABA, but in practice most migrations involve re-submitting them, and re-submission means re-approval.
- Almost never travels
- Conversation history. Contacts, notes, assignments, tags and reporting are the platform's, not Meta's. If you want them, you export them.
That last row is the one that surprises people. Your two years of customer conversations are in the old vendor's database, and the only version you will keep is the one you exported.
Before you start
- Export everything. Contacts, conversations, notes. Do it before you give notice, not after.
- Confirm you can access the WABA. Log into your own Business Manager and see it.
- Write down every template with its category and its variables, so you can recreate them.
- List everything that sends messages — your website, your CRM, that Zapier someone built in 2024, the billing system. Each one has an API key that is about to stop working.
- Check the contract. Notice periods and annual commitments are common.
Doing it with the least downtime
There is a window during which the number is moving and messages will not send. It is usually short, but plan for it:
- Pick a genuinely quiet hour. For most Indian businesses that is early morning, not late evening.
- Have the new platform fully configured first — templates submitted and approved, team invited, routing decided — so the cutover is a connection, not a build.
- Do not cancel the old contract until the new one has sent and received real messages.
- Tell your team the day before. The cutover is not the moment to explain a new inbox.
The first week on the new platform
- Watch quality rating daily. A migration plus a big campaign in the same week is how numbers get restricted — limits and quality explained.
- Re-check every integration you listed. Something will have been missed; it is usually the one nobody remembered owning.
- Verify template categories carried over correctly. A utility template that came back as marketing is a silent cost increase.
The lesson for next time
Whichever platform you end up on, insist on two things in writing: the WABA lives in your Business Manager, and you can export every contact and conversation yourself, at any time, without asking. Those two sentences are the difference between a provider you chose and a provider you are stuck with. The rest of the due-diligence list.