How to Migrate Your WhatsApp Business Number to a New BSP Without Downtime

Switching WhatsApp providers sounds risky and mostly isn't. The number is yours, Meta supports moving it between Business Solution Providers, and the pause during verification is measured in minutes. Treat it as a contract change with a scheduled cut-over, not a data-recovery project, and the whole thing is unremarkable.

What a migration actually consists of

• Number and WABA migration. The phone number and WhatsApp Business Account move to the destination provider, keeping the display name and quality rating. Meta runs a verification step; the sender is briefly unavailable during it.
• Template re-submission. Templates are approved per WhatsApp Business Account, so every template you use is re-submitted on the destination side. This is the step with variable timing, which is why it goes first.
• Contact and consent import. Contacts move into the destination CDP with opt-in state, source and timestamp preserved, along with suppression lists.
• Automations and routing rebuilt once. Chatbot flows, assignment rules and campaign schedules are recreated. This is the bulk of the effort — and on an instance you own, it is the last time you have to do it.

Step by step

1. 1. Pre-approve your templates on the destination

   Re-submit every template you actually use to the destination WhatsApp Business Account and wait for approval before touching the number. Templates do not travel with a migration, and approval is the only step with an unpredictable waiting time — getting it out of the way first removes the risk from the cut-over itself.

2. 2. Import contacts and consent records

   Load contacts into the destination CDP together with their opt-in state, source and timestamp. Consent is a legal record, not a convenience field: import it with its provenance intact rather than re-deriving it, and reconcile suppression lists at the same time.

3. 3. Schedule the verification window outside peak hours

   Pick a low-traffic window, tell the support team, and pause outbound campaigns for the duration. Meta requires a verification step during which the sender is briefly unavailable, so the goal is to make that window boring rather than to avoid it.

4. 4. Move the number and WhatsApp Business Account

   Trigger the migration from the destination provider, complete Meta's verification for the number, and confirm the WhatsApp Business Account, display name and quality rating have carried across. The number itself does not change.

5. 5. Verify inbound and outbound traffic

   Send a template message out, reply in from a real handset, and confirm the conversation lands in the destination inbox with webhooks firing and delivery receipts arriving. Only then re-enable campaigns.

6. 6. Rebuild automations and routing

   Recreate chatbot flows, routing rules, assignment logic and campaign schedules on the destination. This is the largest chunk of effort and the one that only has to be done once — on an owned instance it is yours afterwards.

For the mechanics of registering and verifying the sender on the destination side, see register a WhatsApp sender.

Keeping the pause small

• Pre-approve templates days ahead, not on the morning of the move.
• Pick a genuinely low-traffic window and confirm it with support.
• Pause outbound campaigns before the window opens.
• Have someone with a real handset ready to test inbound immediately.
• Keep the outgoing account open until you have exported history.

Why this is easier on an owned instance

When the WhatsApp Business Account is registered in your own name and the platform is a single-tenant instance you control, a provider change is a commercial decision rather than a negotiation. Contacts, consent history and conversation records already live in your database, so nothing has to be extracted from a shared platform first — and the automations you rebuild during the migration stay yours the next time the question comes up.