Switch WhatsApp API Providers: What Carries Over

Who actually owns my WhatsApp Business Account, me or my provider?

If you were onboarded through Embedded Signup — the popup where you chose a business portfolio and a phone number inside Facebook's own dialog — you do.

Meta states it without hedging: "Business customers onboarded via Embedded Signup own all of their WhatsApp assets, which they can leverage with other Meta solutions such as Ads that Click to WhatsApp" (Meta — Embedded Signup). The same page adds that customers "have full access to WhatsApp Manager, which they can use to access their assets. Note that you cannot restrict this access in any way."

That last sentence is written at providers, not at you. So a switch is not a favour anyone grants you; it is a permission you already hold.

There is a second model, worth ruling out first. Some Solution Partners onboard clients onto an account in the partner's portfolio, on their line of credit. That is legitimate, but the ownership is genuinely different and moving off it is a different job.

Meta's rule for telling them apart is simple: "A WABA must belong to only one business portfolio. You cannot have two or more portfolios owning one WABA" (Meta — WhatsApp Business Accounts).

Open WhatsApp Manager, find the account, and read which business portfolio owns it — every other decision in this article follows from that one line. If it is your company's portfolio, the provider has shared access, and the same page notes "You can share a WABA with up to two partners."

Checked against Meta's documentation on 28 August 2026.

• Who actually owns my WhatsApp Business Account, me or my provider?
• Can I keep my same WhatsApp number when I switch providers?
• What carries over to the new provider, and what do I lose?
• Does my old provider have to release the number before I can move?
• What does a WhatsApp provider migration look like, step by step?
• Why does my number say it is already registered, or ask for a PIN I do not have?
• How many times can I try to register the number before Meta blocks it?
• How much downtime should I expect when moving providers?
• Do both providers have to be in the same Meta Business Manager?
• What should I check before signing with the next provider?

Can I keep my same WhatsApp number when I switch providers?

In the common case, yes, and the number does not move at all.

If your portfolio owns the account and you are only changing which software reads it, nothing about the number changes. A new application subscribes, the old one unsubscribes, and Meta's records — display name, status, history — are untouched, because none of that was ever stored by the software.

The harder case is when the account itself has to change: your number sits on a partner-owned account and you want it on one you control. That is a genuine migration between WhatsApp Business Accounts, and Meta documents it as such.

Two limits are worth knowing. Meta records that "Existing WhatsApp Business Accounts (WABAs) that were originally created via the developer app cannot be selected or onboarded directly through the Embedded Signup flow," and that its 555 test numbers "Cannot be migrated to another WhatsApp Business account, or used outside of the WhatsApp Business platform" (Meta — Embedded Signup).

A number running under coexistence, still live in the WhatsApp Business app on a handset, is its own case — Meta's programmatic guide excludes WhatsApp Business App numbers from the API migration path.

Checked against Meta's documentation on 28 August 2026.

What carries over to the new provider, and what do I lose?

Meta publishes the list, and it is more generous than most switching guides suggest. Clients "can migrate their business phone numbers between WhatsApp Business Accounts (WABAs) and retain their display names, quality ratings, template messaging limits, Official Business Account statuses, and approved, high-quality templates" (Meta — Migrating a business phone number via Embedded Signup).

The programmatic guide gives the same list in a different shape: "Display name, Quality rating of the phone number, Messaging limits, Official Business Account status, Any High quality message templates previously approved" (Meta — Migrating phone numbers among Solution Partners programmatically).

Read that precisely: it names high-quality approved templates. Anything else is absent from Meta's list, so plan to recreate it.

When the account does change, duplication is automatic rather than manual: "Templates are automatically duplicated in the destination WABA and initially granted the same status as their source counterparts." Eligibility is narrow, though — "Only templates with both a status of APPROVED and quality_score of GREEN are eligible for duplication" (Meta — Migrating a business phone number via Embedded Signup).

That is why a well-built product offers a sync-from-Meta button rather than a template import: the templates were never the software's to own. A provider saying its templates cannot be exported is describing its own product, not Meta's.

What does not travel is everything the software invented: conversation history in its database, contact tags, saved replies, automation rules, department routing and campaign reports. Take a CSV of contacts and message logs before cancelling anything.

Meta's deregistration note reassures: "Deregistration does not delete a number or its message history" (Meta — Register a business phone number).

Checked against Meta's documentation on 28 August 2026.

Does my old provider have to release the number before I can move?

Documented fact and vendor folklore diverge most sharply here, so separate them line by line.

Documented. Two-step verification must be disabled first. Meta's migration guide lists as a client prerequisite that "Their business phone number must have two-step verification disabled," and adds "You cannot complete the remaining steps until two-step verification is disabled."

Documented. A provider's application is attached through the subscribed apps edge and comes off the same way: DELETE will "Unsubscribe your application from webhook events for the specified WhatsApp Business Account" (Meta — Subscribed Apps API).

Documented. For an account-to-account move, the number "Must be currently registered with the source WABA" and must have "an approved display name (name_status is APPROVED)" with no pending change request.

Asserted, not documented. Meta documents the prerequisites above. If a provider tells you a formal written release or "NOC" ticket from the incumbent is additionally required, note that Meta's documentation does not say it.

One wrinkle looks like a lock and is not one. In Business settings, the controls for removing a shared account can appear greyed out with a note that the partner must be removed first. Meta's documentation does not describe that behaviour. The operative step is the partner-side unsubscribe above — which is why a provider that will not run it can slow you down even when it cannot stop you.

Checked against Meta's documentation on 28 August 2026.

What does a WhatsApp provider migration look like, step by step?

Meta publishes two guides, and both are narrower than the question most people are asking. One covers moving "business phone numbers from one Solution Partner and WhatsApp Business account (WABA) to another Solution Partner and WABA." The other covers the same move through the API. Neither addresses the commoner case of a customer who owns their account and wants different software on it — read them as reference, not as your runbook.

The short path, when your portfolio owns the account:

1. Confirm ownership in WhatsApp Manager; note the account and phone number IDs.
2. Export contacts, message logs and template text from the outgoing product.
3. Disable two-step verification on the number.
4. Connect the new provider, by Embedded Signup or with credentials.
5. Sync templates and send one real test message in and out.
6. Have the outgoing provider unsubscribe its application.
7. Cancel the old subscription only after live traffic has run through the new one.

The long path, when the account has to move, adds the migration itself: the number is added to the destination account with migrate_phone_number=true, ownership is re-verified by SMS or voice code, and the number is registered with a PIN. Meta's Embedded Signup variant runs: disable two-step verification, put the client through Embedded Signup, capture the phone number ID and new account, share the credit line, subscribe to webhooks, register the number.

One recommendation Meta will not give you, because it concerns vendor implementations rather than the platform: where a provider offers both a popup signup flow and a manual credentials route — account ID, phone number ID, permanent System User token — the manual route is the more predictable for a migration.

Popup flows depend on a browser window handing an authorization code back to the vendor's server after Meta has already attached the partner. When that hand-back fails, the number ends up connected on Meta's side and absent from the platform, with nothing logged because nothing reached the vendor's server. That is a real, observed failure mode of the flow shape in general, not a claim about any named vendor's internals.

Checked against Meta's documentation on 28 August 2026.

Why does my number say it is already registered, or ask for a PIN I do not have?

Almost always two-step verification, and almost always a PIN somebody set years ago and nobody recorded.

Meta's description is short: "Set up two-step verification for your phone number to require a 6-digit PIN when registering the phone number" (Meta — Two-step verification). Registration then demands it: "If your verified business phone number already has two-step verification enabled, set this value to your number's 6-digit two-step verification PIN." If the number never had one, you are setting it rather than recalling it.

The recovery route is the interface, not the API. Meta's page states "There is no endpoint to disable two-step verification," and directs you through WhatsApp Manager instead: Settings, WhatsApp Accounts, the account, Settings, WhatsApp Manager, the phone number's Settings, Two-step verification, Change PIN.

Reset the PIN yourself in WhatsApp Manager before the migration window opens, rather than discovering mid-cutover that the person who set it left the company.

"Already registered" as an error usually means the number is still live on another account and the new registration is being refused, not that the number is stuck. If it persists after two-step verification is off, stop attempting — the next section explains why.

Checked against Meta's documentation on 28 August 2026.

How many times can I try to register the number before Meta blocks it?

Ten, in a rolling three-day window — and the ceiling is the exact opposite of the advice most switching guides give.

Meta: "Requests to the registration endpoint are limited to 10 requests per business number in a 72-hour moving window." And then: "If you have already made 10 requests, the API will return error code 133016, and the API prevents the number from being registered for the next 72 hours" (Meta — Register a business phone number).

Read that as a three-day outage with a ten-click fuse, because that is what it is.

Deregistration is capped identically, so backing out of a half-finished attempt burns a second allowance.

A failed connection attempt in a provider's dashboard often is a registration call. Ten frustrated retries — the natural response to a spinner that does nothing — is a business off WhatsApp until Thursday. If a switch fails twice, stop and find out why. Once blocked, the window has to expire.

This is a different mechanism from an account restriction or a disabled number, which is a policy action rather than a rate limit, but the advice is identical: diagnose before retrying.

Checked against Meta's documentation on 28 August 2026.

How much downtime should I expect when moving providers?

Less than most people fear, and in the ordinary case none.

Meta is explicit for the account-to-account move: "Business phone number registration happens instantly, therefore you can continue to send and receive messages without interruption." Meta's guide for moving a client off a Multi-Partner Solution adds that the route "does not require business phone number reverification. Skipping reverification eliminates downtime" (Meta — Migrating customers off solutions via Embedded Signup).

The gap that does exist is a template gap: "template duplication takes time, therefore you will not be able to use affected templates until they are migrated." Meta's own remedy is sequencing — "To avoid this downtime, you can begin template migration first, before phone number registration."

So inbound messages keep arriving and free-form replies inside the customer service window keep working, while template sends may be briefly unavailable. Do not schedule a broadcast on cutover day.

Billing has a boundary rather than a gap. For a Solution Partner move, "Messages delivered before migration is complete are charged to the old Solution Partner," and "Undelivered messages sent before migration is complete will be charged to the old Solution Partner if they are delivered after migration is complete." If you hold your own payment method on your own account, Meta bills you either way. Per-message rates change and are not reproduced here — see WhatsApp Business API pricing in India.

Checked against Meta's documentation on 28 August 2026.

Do both providers have to be in the same Meta Business Manager?

No. Each provider connects its own application from its own business portfolio; yours stays yours.

The constraint that matters is the sharing ceiling: "You can share your WABA (or any of your business assets) with any business-verified partner using Meta Business Suite" — and "You can share a WABA with up to two partners."

That ceiling is a gift and a trap. Two slots let the incoming and outgoing providers hold access simultaneously, which is how you get an overlapped switch with a tested fallback. It also means that if two partners are already attached, a third cannot join until one leaves.

One asymmetry matters if you are considering a partner-owned account. Meta calculates capacity above the account: "Messaging limits are calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio" (Meta — Messaging limits). A number in your own portfolio has a limit that is yours, earned by your sending. The broadcast limits guide covers how those tiers are earned.

Whether your provider is a Solution Partner reselling messaging on a shared credit line, or a Tech Provider that cannot, changes what a switch means commercially — unpacked in BSP versus Tech Provider.

Checked against Meta's documentation on 28 August 2026.

What should I check before signing with the next provider?

Everything below is a question a reader could fairly aim at WabaCRM, written that way deliberately. A page that tells you how to leave a vendor and will not accept the same interrogation is an advertisement.

• Whose portfolio will own the account? If the answer is anything but "yours", you are buying a switching cost with the software.
• Is there a manual credentials route as well as a popup? A single connect path is a single point of failure, and hand-backs are the part that breaks.
• Can you export contacts and message logs on any plan, including the free one? Ask to see the export, not the roadmap.
• Does the product resell Meta's message fees, or bill only for software? A Tech Provider has no Meta credit line and cannot mark up per-message charges; Meta bills your own payment method. Compare vendors at the alternatives hub, and read whether the WhatsApp Business API is free before accepting any figure as all-in.
• Where does the data physically sit, and is it stated on a page you can link to? WabaCRM's server is in Mumbai and the operating company is named on every page.
• What does a seat cost? Per-agent pricing is what quietly makes leaving expensive as a team grows. WabaCRM charges for no seats at any level — the pricing page carries the model — but check rather than take a vendor's word.
• Who can disable two-step verification on your number? If the honest answer is only the provider's support desk, that is a lock with a friendly name.
• Is your business portfolio verified, and does it stay verified through the move? Verification attaches to the portfolio rather than to the software, so it survives a switch — but if it was never completed, the documents Meta accepts in India is the gap to close before the messaging limit starts to bind.
• Is the tier claimed on the marketing site the tier held? WabaCRM is a Meta-verified Tech Provider, verified 30 July 2026. WabaCRM is not a Meta Business Partner and is not Meta Verified; those are separate things, and neither should be implied by anyone who lacks them.

A switch is easy in proportion to how much of the arrangement lives on Meta's side rather than the vendor's. Your number, display name, quality rating, templates and limits are Meta's records about your business. Choose tools that treat them that way.

Every Meta quotation on this page was read from Meta's own documentation on 28 August 2026. Meta changes that documentation without notice; the linked pages are authoritative and this one is not.