WhatsApp Number Migration: How to Switch Your WhatsApp Business API Provider

Short answer: yes, you can move a WhatsApp business number from one API provider to another, and Meta's documented migration keeps your display name, your phone number's quality rating, your messaging limits and your Official Business Account status. Approved templates with a green quality score are duplicated into the new account and auto-approved. What you do not get back is your chat history, your rejected or pending templates, and your template quality history. The number keeps working during the switch.

The thing almost nobody tells you before you sign a contract is that one setting decides whether you can leave: who owns the WhatsApp Business Account. Get that wrong and migrating stops being a technical task and becomes a support ticket you cannot escalate. That is the part worth reading twice.

What actually carries over, and what you rebuild

Meta's own migration documentation is specific about this, and a lot of provider blog posts get it wrong in both directions. Some claim templates transfer untouched. Others claim you have to recreate every template from scratch. Neither is right.

The template rule is narrower than it sounds. Only templates that are both APPROVED in status and GREEN in quality score get duplicated. A template sitting at yellow quality, or one still in review, is left behind. So the honest expectation is that most of your template library moves and a tail of it does not, and the size of that tail depends on how clean your library already was. Duplicated templates are also re-checked on arrival and can be rejected if they look miscategorized, which is the usual reason a template that worked for a year suddenly needs attention on the other side.

On quality: the number's rating carries over, but each duplicated template starts at UNKNOWN for the first 24 hours, after which Meta generates a fresh rating once it has enough delivery data. That is a reporting gap, not a penalty. If you want the background on how that scoring works and what pushes a number from green to yellow, the WhatsApp quality rating page covers the signals Meta uses.

The setting that decides whether you can leave

Before any of the steps below matter, find out who owns the WhatsApp Business Account your number sits in. There are two situations, and they are not equally comfortable.

If the WABA lives in your own Meta Business Portfolio and your provider is connected to it, you can disable two-step verification on the number yourself, in your own Meta account, and start the migration whenever you want. If the WABA lives in your provider's portfolio, you have to ask them to disable it, and some providers restrict the account so that you cannot do it yourself. Then your exit runs at the speed of their support queue.

Two-step verification matters because Meta requires it to be off before a number can be migrated. If it was ever enabled, the current account owner has to disable it first. There is no way around that step, and it is the single most common place migrations stall. Note that a false success is possible here: the toggle appears to turn off but the number still will not release, which usually means the current provider has to release it from their side.

So the practical advice is uncomfortable but simple. Ask any provider, before you sign, whether the WABA will be in your Meta Business Portfolio or theirs. It is a one-line question and it is the difference between a migration you control and one you request. It is also worth understanding the difference between the two kinds of partner Meta recognizes, because it changes who holds what: our guide to Solution Partner versus Tech Provider breaks that down, and the WhatsApp Business Solution Provider page explains where a provider sits in Meta's structure.

What you need in place before you start

Meta gates migration behind a checklist on both ends. Working through it first turns a multi-day back-and-forth into an afternoon.

• The source account must have Business Verification completed and an approved review status.
• The destination account needs Business Verification and its own account review approved.
• The destination account needs a valid payment method attached.
• The number must currently be registered to the source account.
• The display name must be approved, with no pending name-change request sitting in review.
• Two-step verification must be disabled on the number by whoever owns the source account.
• The destination needs a webhook subscription so it starts receiving messages and status callbacks.

One provider-side item that is easy to miss: some providers turn on local data storage for a number. If yours did, that has to be unwound before the number will move, so ask them directly rather than discovering it halfway through.

The two migration paths

There are two routes, and which one you get depends on your new provider rather than on you.

Embedded Signup. Most platforms use this. You disable two-step verification, then click through Meta's own signup dialog inside the new provider's dashboard, confirm the number and display name, and the provider captures the resulting IDs, attaches billing, subscribes webhooks and registers the number. You never touch an API. This is the path to expect if you are moving to a no-code sending platform.

Programmatic. If you are running your own integration, the sequence is: disable two-step verification, POST the number to the destination account's phone numbers endpoint with migrate_phone_number set to true, request a verification code by SMS or voice, verify the six-digit code, then call the register endpoint with messaging_product set to whatsapp and a six-digit PIN. Your app needs the whatsapp_business_management permission. If you want the request shapes for sending once you are live on the other side, the guide to sending a WhatsApp message with the API has the payloads.

Does the number go down during the switch?

Registration itself is effectively instant, and Meta's documentation says you can keep sending and receiving without interruption. The realistic caveat is templates: while duplication is still running, a template that has not landed yet cannot be sent, so a campaign fired at exactly the wrong moment will fail on the template rather than on the number.

Which gives you the sensible plan: migrate in a quiet window, do not schedule a campaign across it, and send one live test message per template category on the far side before you resume normal volume. Afterwards, confirm your webhook endpoint is genuinely answering rather than assuming it is, because a silently failing callback URL looks exactly like a quiet day of inbound messages. If you do not already have something checking that endpoint every 30 seconds, a migration is a good moment to add it.

Do the pricing math while you are already moving

Switching providers is the one moment you have real leverage, so it is worth spending an hour on the numbers rather than porting your way into the same bill. Meta charges per delivered template by category and destination country, and your provider adds its own fee on top. That second number is where providers differ enormously: some mark up every message, some charge a flat monthly rate.

The crossover matters more this year than last, because two dated changes are landing. From October 1, 2026, free-form replies inside the open 24-hour customer service window stop being free, which hands per-message providers a newly billable category to mark up. Our WhatsApp pricing changes hub tracks both dated changes, and the pricing calculator will let you put your own volume against a flat plan and a per-message plan side by side. If you are leaving a specific vendor, the Twilio WhatsApp alternative and Wati alternative comparisons lay out what each charges.

Frequently asked questions

Can I switch WhatsApp Business API provider?

Yes. Meta supports migrating a registered business phone number from one WhatsApp Business Account to another, including when the two accounts sit with different providers. Your number, display name, quality rating, messaging limits and Official Business Account status all carry over, and approved green-quality templates are duplicated into the destination account automatically.

How long does WhatsApp number migration take?

The registration step itself completes in minutes. What sets the real timeline is the preparation: getting two-step verification disabled by whoever owns the source account, and having Business Verification already approved on the destination side. With those done in advance the switch is same-day. Waiting on a provider to disable two-step verification is what turns it into a multi-day job.

Do I lose my message templates when I migrate?

Not most of them. Templates that are both approved and at green quality are duplicated into the new account and automatically approved. Templates that are rejected, still pending review, or sitting at a lower quality score are not copied, so you rebuild and resubmit those. Duplicated templates are also re-checked and can be rejected if they appear miscategorized.

Will I lose my chat history when I switch providers?

Yes. Conversation history does not move between WhatsApp Business Accounts. If those transcripts matter for compliance or account context, export them from your current provider before you start the migration, because you will not be able to pull them afterwards.

Does my quality rating reset when I migrate?

The phone number's quality rating carries over, and so does your messaging limit tier, so you do not restart at the lowest tier. Individual template ratings do reset: every duplicated template begins at UNKNOWN and stays there for about 24 hours, until Meta has enough delivery data to score it again.

Do I need to disable two-step verification to migrate?

Yes, and it is mandatory. Meta will not migrate a number with two-step verification enabled. If your WhatsApp Business Account sits in your own Meta Business Portfolio you can turn it off yourself. If the account belongs to your provider, only they can do it, which is why account ownership is worth confirming before you sign with anyone.

The short version

Migration is a solved, documented process, and the technical part is genuinely routine. The risk is almost never the API call. It is discovering late that your provider holds the WhatsApp Business Account, that two-step verification cannot be disabled without their help, or that a third of your template library was never at green quality in the first place. Check those three things first and the rest is an afternoon.

WaBulkSend runs on the official WhatsApp Business Platform, so a number migrated in keeps its display name, quality rating and messaging limits, and our plans are flat monthly rather than per message. You can start on the free plan with 500 messages a month and move the number once you have seen how the sending side works, or read what the platform covers on the WhatsApp Business API page.