How to Migrate a WhatsApp Business Number to a New Provider

This guide is for operations, CX and IT leads who already send messages through the WhatsApp Business API and want to change provider without losing the number, the green tick or months of template work. By the end you will know exactly what Meta carries across, what you must move yourself, and how to plan a cutover with minimal disruption.

Can you move a WhatsApp Business number to another provider?

Yes. Meta supports migrating a business phone number from one Solution Partner and WhatsApp Business Account (WABA) to another. The number stays the same, so customers keep messaging the chat they already know.

Meta describes two routes in its developer documentation:

• Migration via Embedded Signup. The client starts the flow from the new provider's onboarding screen. Meta creates the destination WABA, links it to the client's Meta business portfolio and grants the provider's app access. Meta calls this the preferred option.
• Programmatic migration. The destination provider performs the API calls. Meta recommends this mainly when the provider will own the WABA on the client's behalf (the "On-Behalf-Of" model).

Technically, a new WABA is created and the number is re-associated with it. That detail matters, because anything tied to the old WABA but not to the number has to be rebuilt.

What transfers and what does not?

The number's reputation transfers; your operational data does not. The table summarises Meta's documentation and the practical reality of switching platforms.

Two limits are worth highlighting. First, migrated numbers can only be registered on Cloud API. Second, test numbers issued by WhatsApp cannot be migrated at all.

What do you need before you start?

Migration fails most often because a prerequisite was missed. Meta lists these requirements for the business that owns the number:

• The Meta business portfolio has verified status.
• The existing WABA has approved status.
• The existing WABA has a valid payment method attached.
• The number has an approved display name and no pending display name change.
• Two-step verification is disabled on the number.

Two-step verification is the six-digit PIN that protects number registration. There is no API endpoint to disable it, so if your current provider owns the WABA, you have to ask them to turn it off in WhatsApp Manager. Request this early, in writing.

On the destination side, at least one app must be subscribed to webhooks on the new WABA before the number moves.

How do you migrate step by step?

The sequence below follows Meta's Embedded Signup migration path, with preparation steps added at the start and end.

Before migration day

1. Inventory your assets. List templates (name, language, category, status, quality), webhooks, integrations, chatbot flows and saved replies.
2. Export your data. Request conversation history, contacts, tags and opt-in records from your current provider in CSV or JSON. Do not rely on Meta for history: Cloud API keeps message data for a maximum of 30 days.
3. Clean up templates. Delete unused ones and fix low-quality ones. Only approved, green templates copy across.
4. Rebuild integrations on the new platform against a test number, including CRM webhooks and order or booking triggers.
5. Agree a cutover window with both providers, ideally a low-traffic period with no campaigns scheduled.

On migration day

1. Disable two-step verification on the number in WhatsApp Manager, or confirm your old provider has done it.
2. Start template migration first if the destination provider supports it. Meta notes that template duplication takes time, and starting it before number registration avoids template downtime.
3. Complete Embedded Signup with the new provider, entering the same number and display name.
4. New provider shares its credit line (or your billing is set up), subscribes webhooks and registers the number on Cloud API. Registration is the step that moves the number.
5. Re-enable two-step verification with a new PIN stored in your own password manager.

After cutover

1. Send a test template and a session reply, and confirm status webhooks arrive.
2. Check which templates failed to duplicate and resubmit them.
3. Watch template quality for the first days, since ratings start as unknown.
4. Confirm agents can see and answer new chats.

What causes downtime or disruption?

Number registration is instant, so the risk is rarely that WhatsApp "goes down". The risk is that pieces around it are not ready.

• Template gaps. Until duplication finishes, affected templates cannot be sent. OTP and order-update templates are the most sensitive.
• Webhook gaps. Inbound messages that arrive before your new platform's webhook is live may not reach agents.
• Billing. Meta states that messages delivered before migration completes are charged to the old Solution Partner, and messages delivered afterwards are charged to the business. Agree with both providers how the final invoice and any prepaid balance are handled.
• Category rechecks. Duplicated templates are rechecked for category. If one is reclassified, for example from utility to marketing, costs and opt-in rules change. See our guide to template categories.

Worked example: a Dubai clinic group switches provider

A synthetic example. "Marina Health" runs three clinics in Dubai on one WhatsApp number with a green tick. It sends appointment reminders, lab-result notifications and occasional marketing.

The team inventories 42 templates. Nine are paused or rejected, so they delete six and rewrite three. They export 12 months of conversation history and opt-in logs from the old inbox for their own records.

The new provider builds the booking-system webhook on a test number. On a Friday afternoon, when reminder volume is lowest, the old provider disables two-step verification. Template migration starts first; the clinic then completes Embedded Signup and the number is registered. Two templates fail the category recheck and are resubmitted. Reminders resume the same afternoon, the green tick remains, and agents work from the new inbox on Saturday morning.

Common mistakes to avoid

• Changing the display name during the project. A pending change blocks migration.
• Forgetting two-step verification. It is the single most common blocker, and only the WABA owner can disable it.
• Assuming history moves. It does not. Export it first.
• Migrating with poor templates. Low-quality templates do not transfer, and you lose their approval.
• No rollback plan. Keep old integrations available until the new setup is verified.
• Losing the PIN. Set a new two-step PIN after migration and store it where your team, not a vendor, controls it.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, an official Meta Business Solution Provider, onboards numbers to the WhatsApp Business API through Meta Embedded Signup, the same flow Meta prefers for migrations. Once connected, you can rebuild templates with variables, media and buttons, check them in a phone preview and track approval status. Conversations land in the Omni Inbox alongside Instagram, Telegram and Email, with Arabic and English support. Delivery reports with CSV export help you confirm templates are flowing after cutover, and the REST API and webhooks are publicly documented. Contact us to plan a migration.