Migrating a WhatsApp number between providers without losing the conversation

Every few weeks someone messages me asking how to move their WhatsApp number off their current provider. The reason is always the same one. The provider was fine at the start, then the bill grew, or support went quiet, or the team needed a feature the dashboard never had.

The number itself moves in about ten minutes. Everything around the number is where the work is, and that is the part nobody warns you about. I have watched a business move a number cleanly over a weekend, and I have watched one go dark for nine days because a template needed re-approval and nobody had the original copy.

This is the order I use, and the questions I insist on answering before the first click.

What moves, and what does not

Before the steps, get the mental model right. Three different things are involved, and they behave differently.

• The phone number. This is yours, and it can be attached to a different account. wa.me links, QR codes and click-to-WhatsApp ads all point at the number, so they keep working after the move. That alone kills the most common excuse for staying ("our ads would break").
• The WhatsApp Business Account (WABA) that the number sits inside. This is the container that holds your templates, your business verification and your sending history. Two very different migrations exist depending on whether the number stays in the same WABA or moves into a new one.
• Conversation history. Here you should assume nothing. The platform moves the number's identity, not your message archive. Whether any history can be carried over depends on the providers involved and is a question you ask in writing, not something you discover mid-migration.

If your number sits under your agency's or reseller's business account rather than your own, stop and read who actually owns your WhatsApp Business account first. You cannot migrate an account you cannot see, and this is the single most common reason a migration stalls for weeks.

Step one: inventory, before anyone clicks anything

Open the current dashboard and write all of this into one document. Every item here is something that either transfers or gets rebuilt, and you want to know which before the cutover night.

• Phone number ID and WABA ID, exactly as displayed.
• The verified display name, and the business verification status.
• Every approved template: name, language, category, and the body text. Export the copy, do not just note that it exists.
• Flows, catalog connections, and any commerce setup.
• The webhook URL and verify token your application listens on.
• API keys, system user tokens, and any app that posts to the API.
• Current messaging limit and quality rating.
• The payment method on file, and who owns it.

Two of these are quietly important. Templates get re-submitted for approval whenever you move into a new WABA, so the body copy is your asset and the approval decision belongs to Meta, not to you. And your opt-in records, meaning the proof that each contact agreed to be messaged, usually live in your own CRM. If they live only in the provider's dashboard, export them before you start. Losing opt-in evidence after a migration is a compliance problem you cannot fix retroactively.

Step two: choose the migration shape

There are two shapes, and they are not equally difficult.

Shape one: same WABA, new provider. The number stays in the business account you already control and the provider in front of it changes. Templates stay approved, verification stays intact, and the cutover is mostly about webhooks and credentials. This is the one you want, and it is available whenever you own the WABA.

Shape two: new WABA, number moved to you. This is the case where your number lives inside someone else's business account. The number has to be released from there and added to your own, which means going through number verification again, a display name review, and a fresh template approval round for everything you send. Plan for days, not hours, and do not schedule a campaign in that window.

Ask the receiving provider which shape applies to you in writing. Their answer tells you how long the project is.

Step three: build the cutover window

A number can only be connected to one provider at a time. That means there is no parallel run, and no way to send from both sides while you compare. The move is a hard switch, so treat it as one.

• Test your new webhook receiver against a test number first, so the only unknown on the night is the production number itself.
• Pick a low-traffic window. For most Indian and Gulf businesses that is a Sunday night, not a Monday morning.
• If you take a lot of inbound, send one holding template the day before telling customers the number stays the same.
• After the switch, send one real template and have someone send one real inbound message. Both directions must work before you tell anyone the migration is done.
• Leave the old subscription running until the new number is verified and tested. Cancelling first is how a two-hour job becomes a week offline.

The three questions to settle in writing

I ask these before every migration, and I get a written answer from both sides.

1. Does conversation history transfer? Yes or no, and in what format, and how long does the export take. If the answer is "we will see", assume no and plan to keep the old dashboard read-only for a month.
2. What happens to templates? If re-approval is needed, who owns that work, and what is the fallback if a template you depend on gets rejected in the new account. Rejections are common enough that I plan for them: see why WhatsApp templates get rejected for the usual causes.
3. When does the old provider release the number? There is usually a step on their side that frees it. Confirm it happens in the same window, in writing, with a name attached.

What breaks, and what people wrongly think breaks

Things that genuinely break and need to be redone:

• Saved phone_number_id values hardcoded in your application and in any automation you built on the old provider's flow builder.
• API tokens, webhook subscriptions and app-level permissions.
• Dashboards and saved segments that lived inside the old provider's interface.

Things that usually keep working, and get blamed for nothing:

• wa.me links on your website and in email signatures.
• QR codes on packaging and at reception.
• Click-to-WhatsApp ad campaigns.

The last one surprises people, and it is the reason I always start with the number rather than with the dashboard. Ads and links follow the number, not the provider.

If you are comparing a full migration against staying where you are, read what to check before you switch providers before you make the call. Half of that list is about data ownership, and it is the half that decides how painful any future move will be.

Where BNex fits

BNex runs on your own verified WhatsApp number and keeps conversations in a shared inbox, so the team sees one thread instead of four phones. If a migration ever became necessary, the export question is easier when the conversation record is yours from day one. The provider comparison guide covers the ownership questions to ask any provider before you commit, which is the cheapest place to spend an hour.

If you are staring at a migration and not sure which shape you are in, message me on WhatsApp at wa.me/917358722745 with the WABA ID and who owns the business manager. I will tell you whether you are looking at a two-hour job or a two-week one.

Related Reading