A vendor-neutral guide to moving a WhatsApp business phone number away from a Business Solution Provider: what stays with the number, what does not, what you need before you start, who pays for messages while two providers are on the number, and how to decide whether owning your own WhatsApp Business Account is actually the right call.
Verified against Meta's WhatsApp Business Platform documentation on 27 October 2026, after Meta's account model change.
Direct Answer
You can move your WhatsApp business phone number away from a Business Solution Provider, now called a Solution Partner, without changing the number and without losing your display name, quality rating, messaging limits, or Official Business Account status.
Since Meta's account model change, which rolled out from September 23, 2026, Meta no longer migrates a number from one Solution Partner to another. You share the number's WhatsApp account with the new provider instead, normally through Embedded Signup run by the new provider. The number stays registered and conversations continue, and the new provider gets its own Messaging account for templates and billing. Templates and the payment method in the old provider's Messaging account do not come along. Removing the old provider is your decision and a separate step.
Once you own your WABA and connect through a provider that does not extend a Solution Partner credit line, you attach your own payment method and Meta bills its messaging charges directly to you. A software provider can still charge a separate usage-based platform fee, so verify both Meta's invoice and the provider's price sheet.
Why Businesses Leave a BSP
Two reasons dominate, and they are genuinely different problems with different solutions.
Cost. A Solution Partner can extend a line of credit and directly invoice clients for WhatsApp Business Platform services. A provider acting only as a Tech Provider or Tech Partner does not extend that Solution Partner credit line: the client attaches its own payment method and Meta bills its messaging charges directly. This removes a reseller from Meta's billing path, but it does not prevent the software provider from charging a separate platform or usage fee. Compare both layers.
Data exposure and control. A traditional BSP or inbox platform usually sits in the message path, because that is what makes an inbox, a broadcast tool, or a CRM sync possible. Every message you send and receive transits — and is often stored on — the vendor's systems. If your objection is "we do not want a third party holding our customer conversations," the fix is not a cheaper BSP, it is an architecture where message-path webhooks go from Meta to your own endpoint. See WhatsApp API Privacy and GDPR and EU Compliance.
There is a third, quieter reason: lock-in anxiety. Businesses discover mid-contract that they do not own the WABA their number lives on. Under Meta's new account model, the WhatsApp account that holds the number always belongs to the business, and leaving no longer requires moving the number at all.
Leaving is a legitimate, Meta-supported operation. Nothing below is a workaround.
What You Keep
The number does not move. It stays in its WhatsApp account, which belongs to your business portfolio, and the new provider is added to it. What belongs to the number or the portfolio therefore stays as it is:
- your display name
- your quality rating
- your messaging limit, which belongs to the business portfolio
- your Official Business Account status
- your business verification
- the chat thread your customers already have with your number
Registration also stays in place. Meta lets a business onboard a new provider with a number that is already registered with another one: the new provider's register call succeeds without resetting the two-step verification PIN.
What You Do Not Keep
This is the half most switching guides skip. Everything below belongs to the old provider's Messaging account, not to the number.
Templates. Templates belong to the Messaging account they were created in. The new provider's Messaging account starts empty, so recreate and resubmit the templates you need, or have them copied with Meta's Template Migration API. Copied templates restart at baseline quality rating and messaging tier and need roughly 2–4 weeks to ramp up again. See Messaging Accounts.
The payment method. Each Messaging account has its own. Attach a payment method to the new provider's Messaging account, or, if the new provider is a Solution Partner, let it share its credit line. Until then, paid and template sends fail with error 131042.
Webhook configuration. Webhook subscriptions live on the Messaging account. The new provider sets up its own on its Messaging account.
Message history in the vendor's product. Your current BSP's inbox, CRM sync, and reports are that vendor's storage, separate from Meta's accounts. Export anything you need before you start.
Prerequisites Checklist
| Requirement | Who can satisfy it |
|---|---|
| Admin access to the business portfolio that owns the number's WhatsApp account | You. The WhatsApp account always belongs to the business, not the provider |
| The number stays connected: do not delete or deregister it | You and the old provider |
| A payment method for the new provider's Messaging account | You, or the new provider if it is a Solution Partner with a credit line |
| Your templates' content, so they can be recreated | You, from the old provider or WhatsApp Manager |
You no longer need the old provider to disable two-step verification. Meta is also deprecating the PIN for eligible Cloud API numbers; see Two-Step Verification.
Billing During the Switch
Each provider on the number is billed through its own Messaging account, whichever provider handles the conversation. A message is charged to the Messaging account associated with the app that sent it, and its delivery receipts go back to that app.
In practice:
- Messages sent through the old provider are billed to the old provider's Messaging account until you remove it or stop sending through it.
- Messages sent through the new provider are billed to the new provider's Messaging account.
- While both providers are on the number, they share its throughput and your portfolio's messaging limit.
Meta's older billing rules for a completed number migration no longer apply, because nothing migrates.
The Coexistence Caveat
If your number runs WhatsApp Coexistence — the WhatsApp Business app and Cloud API on the same number — the switch follows Meta's Coexistence onboarding instead of the standard path. Meta converts the existing WhatsApp Business account into a Messaging account and shares it, together with its WhatsApp account, with the new partner. It does not create a separate Messaging account for that partner.
Meta's Coexistence onboarding documentation also states that a business that previously worked with a partner and still shares that partner's credit line may see an error when switching to a new partner, and links to a resolution guide.
Provider guidance differs: for example, 360dialog states that Coexistence numbers cannot be migrated between WABAs and describes a provider switch as an in-app disconnect followed by Coexistence re-onboarding. That is provider-specific guidance, not a universal Meta guarantee. Confirm the account and credit-line state with both providers before choosing a path.
In the field, the way this surfaces is Embedded Signup failing with #2655093 — the account is still shared with a partner — before the new provider is granted any access at all. That code is widely reported and is documented at Error 2655093, though it does not appear in Meta's public Cloud API error tables. The business can disconnect the current Business Platform relationship in the WhatsApp Business app; the previous provider may also need to complete backend offboarding, and Meta support may be needed for a stale relationship. The new provider cannot inspect or remove it before Meta grants access.
The practical consequence: if you are on Coexistence, get written confirmation of full backend offboarding from your current provider, not just "we removed you from our dashboard." Those are different operations and only one of them unblocks you.
Switching Runbook
- Confirm access. In Meta Business Suite, check that you are an admin of the business portfolio and can see the number under Settings → Accounts → WhatsApp accounts.
- Export everything you want to keep. Message history, media, template content, contact lists, and any reporting that lives only in your current vendor's dashboard.
- Inventory your templates. They stay in the old provider's Messaging account, so note the ones you need to recreate.
- Complete Embedded Signup with the new provider. Select your existing number. Meta shares its WhatsApp account with the new provider and creates a Messaging account for it, and the number stays registered, so messaging continues. On Coexistence, follow the new provider's Coexistence flow.
- Attach a payment method to the new Messaging account, or confirm the new Solution Partner shared its credit line.
- Configure webhooks. If you want message-path webhooks delivered to your own endpoint rather than a vendor's, set a Webhook Override on the new Messaging account. Your endpoint must already answer Meta's
hub.challengeverification. - Recreate your templates and test. Submit them in the new Messaging account, or copy them with Meta's Template Migration API, then send a test message.
- Remove the old provider. In Meta Business Suite, open the Partners tab of the number's WhatsApp account and of the old provider's Messaging account and remove the old provider. Ask the old provider in writing not to deregister the number: any partner on a number can deregister it, which takes it off Cloud API for every provider.
- Reconcile the final invoice. The old provider's charges cover messages sent through its Messaging account. Messages sent through the new provider are billed to the new Messaging account.
Decision Framework: BSP vs Owning Your WABA
| Question | Lean toward a Solution Partner / BSP | Lean toward owning your WABA |
|---|---|---|
| Do you need a Meta line of credit because you cannot attach your own payment method? | Yes | No |
| Do you want a turnkey inbox, CRM, or campaign UI included? | Yes | No, you run your own backend or a separate tool |
| Do you accept a provider reselling Meta's messaging charges? | Yes | No, you want Meta to bill its charges directly |
| Does message content need to stay out of a vendor's store? | Not a priority | Priority |
| Do you have engineering capacity, in-house or partnered? | Limited | Available |
| Are you sending high volume where a few cents per message compounds? | Volume is modest | Yes |
| What support and escalation path do you need? | Confirm the BSP's included support | Confirm the Tech Partner's scope and Meta support available to your business |
There is no universally correct answer here. A ten-person company with no developers and 2,000 messages a month may be well served by a BSP inbox. A company sending 500,000 utility templates a month, with a backend team and a compliance requirement, should compare the total provider fee and architecture rather than paying for a bundled UI it does not use.
What Changes Operationally After You Leave
Owning your WABA moves work onto your side of the line. Plan for it:
- Billing. You attach a payment method to your own Messaging account and Meta invoices you directly. Watch for error 131042 if payment setup is incomplete.
- Quality and limits. Account health is yours to monitor. No one else gets the alert first.
- Template lifecycle. Approvals, rejections, quality drops, and category changes arrive as webhooks you need to handle or a dashboard you need to watch.
- Webhook delivery. Your endpoint's uptime is now part of your messaging reliability. Meta retries, but not forever.
- Support. Support scope and Meta escalation access vary by provider and partner status. Confirm ownership for onboarding, account restrictions, billing, and partner-removal cases before you leave.
- Pricing changes. They land on your invoice at Meta's rates. See WhatsApp Pricing Changes 2026 for what is scheduled.
None of that is hard. It is just no longer someone else's problem.
Where Dualhook Fits
Dualhook is a badged Meta Tech Partner, not a BSP. Customers keep their own Meta Business assets and their own billing relationship with Meta, and Dualhook charges a flat platform fee with no per-message component. Dualhook configures the connection through Embedded Signup and sets a Webhook Override on its Messaging account so message-path webhooks route directly from Meta to your endpoint, and it does not store message content.
If you are leaving a BSP specifically to stop paying per-message markup and to keep customer conversations out of a vendor's store, that is the model Dualhook is built for. If what you actually want is a hosted inbox with agents, tags, and campaign tooling, a BSP is a better fit and you should stay with one.
See Dualhook vs BSPs, Tech Partner, and Pricing.
Operational, not legal, advice. If GDPR, data residency, or your current contract's termination and data-return clauses matter to your situation, take your own legal advice and read the contract before you start.
Dualhook Boundary
Dualhook does not remove your previous provider, copy templates between Messaging accounts, attach payment methods, or offer Meta's Template Migration API. You remove the old provider and attach a payment method in Meta Business Suite, and you recreate templates in the Dualhook dashboard or through the Runtime API. See the account model boundary for what Dualhook does with each account type.
FAQ
Will I lose my WhatsApp number when I leave my BSP?
No. Since Meta's 2026 account model change the number does not move. You share its WhatsApp account with the new provider, the number stays registered, and messaging continues.
Will my quality rating and messaging limits reset?
No. The number and its WhatsApp account do not change, so the display name, quality rating, messaging limit, and Official Business Account status stay as they are. Templates copied into the new provider's Messaging account with Meta's Template Migration API are the exception: they restart at baseline quality rating and messaging tier and need roughly 2–4 weeks to ramp up.
Do my templates come with me?
No. Templates belong to the old provider's Messaging account. Recreate them in the new provider's Messaging account, or have them copied with Meta's Template Migration API.
Do I need my current provider's cooperation to leave?
Usually not. The WhatsApp account belongs to your business, so you can share it with a new provider and remove the old one yourself in Meta Business Suite. Ask the old provider in writing not to deregister the number, because any partner on a number can.
Is there downtime when I switch?
The number stays registered, so sending and receiving continue. The new provider's Messaging account starts without templates or a payment method, so attach a payment method and recreate templates before you depend on template sends.
Who pays for messages sent during the switch?
Each provider is billed through its own Messaging account for the messages its app sends. Messages sent through the old provider stay on the old provider's account, and messages sent through the new provider are billed to the new one.
Does my message history come with me?
Your customers keep the same chat thread with your number, because the number does not move. Message archives stored in your old provider's inbox or CRM are separate and stay with that provider, so export what you need before you start.
Can I move a Coexistence number to a new provider?
It follows Meta's Coexistence onboarding path, not the standard one. Meta warns that a prior shared credit line can block a partner switch, and provider-specific rules differ. Disconnect the old Business Platform relationship as instructed, and get written confirmation of full backend offboarding.
What is the difference between a Solution Partner and a Tech Provider?
A Solution Partner (the role formerly called BSP) can extend a Meta line of credit and invoice you for WhatsApp messaging. A provider acting only as a Tech Provider or Tech Partner does not extend that credit line, so you attach your own payment method and Meta bills its messaging charges directly. The provider can still charge a separate platform or usage fee.
Meta is renaming these roles, with the new names taking over in 2027: Tech Partner becomes Technology Partner, and Solution Partner (BSP) becomes Technology Partner with the Reseller add-on. Meta's developer documentation already uses the new names.
Sources
- Meta, Updates to WhatsApp Business accounts (updated 22 September 2026), Onboarding changes (updated 26 June 2026), and Managing messaging accounts (updated 29 August 2026), summarized in WhatsApp Account Model Changes
- Meta, Migrating a client off a Multi-Partner Solution
- Meta, Onboarding WhatsApp Business app users
- 360dialog, WhatsApp Coexistence — provider-specific migration guidance
All checked 27 October 2026. Meta's account model pages state that number migration between Solution Partners is not supported under the new model, which replaces the migration steps this guide described before. Provider-specific Coexistence guidance is labelled explicitly rather than presented as universal Meta behavior.