A vendor-neutral guide to migrating a WhatsApp business phone number away from a Business Solution Provider: what Meta preserves, what it does not, the prerequisites that block the flow, who pays for messages mid-migration, 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 14 August 2026.
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, Official Business Account status, or eligible approved high-quality templates.
Meta migrates the number between WhatsApp Business Accounts, normally through Embedded Signup run by the new provider. The prerequisites that trip people up are: two-step verification must be disabled on the number, the display name must be approved with no pending change request, the WABA must be approved with a valid payment method attached, and the Meta Business Account must be verified.
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, and that a routine action — disabling two-step verification — requires the cooperation of the vendor they are trying to leave.
Leaving is a legitimate, Meta-supported operation. Nothing below is a workaround.
What You Keep
From Meta's Solution Partner migration documentation, verbatim:
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.
And on why:
Since the client's business phone number is not changing, its display name, quality rating, messaging limit, and Official Business Account status are all preserved.
On templates:
Templates are automatically duplicated in the destination WABA and initially granted the same status as their source counterparts. After duplication however, templates are re-checked to ensure they are correctly categorized according to our guidelines. This may result in some duplicated templates having their status set to REJECTED. Only templates with both a status of APPROVED and quality_score of GREEN are eligible for duplication.
In practice that means the assets you spent months earning — your display name, your quality rating, your messaging tier, your OBA badge — survive the move intact.
What You Do Not Keep
This is the half most migration guides skip.
Template quality ratings. Meta, verbatim: "Quality ratings of templates will NOT be migrated. All migrated templates will start with an UNKNOWN rating. This rating will remain for the first 24 hours, after which a new rating will be generated if sufficient data is available."
Non-approved or non-GREEN templates. Only templates that are both APPROVED and GREEN are eligible for duplication. A YELLOW template, a paused template, a pending template, or a rejected one does not come across. Recreate and resubmit them.
Templates beyond the destination limit. If the destination WABA hits its template limit during duplication, the remainder are simply not created. Count your templates before you start.
Duplicated templates that fail recategorization. Meta re-checks category correctness on duplication. A utility template that was quietly miscategorized in the source WABA can arrive as REJECTED. See template category updates.
Message history and media. Meta's migration page states that uploaded media can continue to be used, but it does not include chat history among the assets it promises to transfer. Treat chat-history transfer as not provided unless your source and destination providers explicitly document it for your path, and export anything you need before you start. This matters especially when your current BSP is also your inbox: that product's conversation archive is separate from the WABA migration.
Prerequisites Checklist
From Meta's migration documentation. Every one of these blocks the flow if unmet:
| Requirement | Who can satisfy it |
|---|---|
| The Meta Business Account has a verified status | You, via Meta Business Verification |
| The existing WABA has a status of approved | Existing WABA owner |
| The existing WABA has a valid payment method attached in Payment Settings | Whoever owns the WABA |
| The business phone number has two-step verification disabled | You if you own the WABA; otherwise your current Solution Partner |
The business phone number has an approved display name (name_status is APPROVED) | You, before starting |
| No pending display name change request on the number | You, before starting |
| The number will be registered for Cloud API | Migrated numbers can only use Cloud API |
| The number is not a Meta test number | Test business phone numbers cannot be migrated |
Meta's first migration step is explicit: migration cannot complete until two-step verification is disabled on the number.
That single line is the whole negotiation. If you do not own your WABA, you need your current provider to perform an action whose only purpose is to let you leave. Ask for it in writing, early, with a date. It is a routine request and most providers action it, but it is not instant, and it is the step that turns a two-day migration into a two-week one.
See Two-Step Verification for where the setting lives once you own the WABA.
Billing During Migration
Meta, verbatim:
Messages delivered before migration is complete are charged to the old Solution Partner. Undelivered messages sent before migration is complete will be charged to the old Solution Partner if they are delivered after migration is complete. Messages delivered after migration is complete are charged to the business customer.
This is not a simple delivery-time cut. Messages delivered before completion go to the old Solution Partner, and Meta applies a carryover rule to messages sent before completion but delivered afterwards: those also go to the old Solution Partner. Messages sent and delivered after completion go to the business customer.
Meta also notes that phone number registration happens instantly, so sending and receiving continue without interruption, while template duplication takes time. If template downtime is your concern, migrate templates first.
The Coexistence Caveat
If your number runs WhatsApp Coexistence — the WhatsApp Business app and Cloud API on the same number — leaving a partner is more constrained than the standard migration path.
Meta's Coexistence onboarding documentation 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.
Do not assume the standard WABA-to-WABA migration path applies unchanged to Coexistence. 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 source WABA, destination WABA, 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.
Migration Runbook
- Confirm the prerequisites. Meta Business Account verified, WABA approved, valid payment method attached, display name approved with no pending change request.
- Get two-step verification disabled. Do it yourself in WhatsApp Manager if you own the WABA. Otherwise request it from your current Solution Partner in writing, with a target date.
- 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. Meta does not promise chat-history transfer in its migration documentation.
- Inventory your templates. Note which are
APPROVEDandGREEN— only those duplicate. Everything else is a recreate-and-resubmit task on the far side. - Complete Embedded Signup with the new provider. Depending on the migration path, create or select the destination WABA under your business portfolio, then migrate the number. Registration is instant, so messaging continues.
- Re-verify what carried over. Display name, quality rating, messaging limit, and OBA status should be intact. Template quality ratings will read
UNKNOWNfor roughly the first 24 hours. - Reconfigure webhooks. If you want message-path webhooks delivered to your own endpoint rather than a vendor's, set the WABA-level Webhook Override at this step. Your endpoint must already answer Meta's
hub.challengeverification. - Recreate the templates that did not duplicate. Non-approved, non-GREEN, over-limit, or recategorized-to-rejected.
- Reconcile the final invoice. Messages delivered before completion, plus messages sent before completion but delivered later, belong to the old partner. Messages sent and delivered after completion belong to the business customer.
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 WABA 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 migration 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 WABA-level Webhook Override 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.
FAQ
Will I lose my WhatsApp number when I leave my BSP?
No. Migration moves the number between WhatsApp Business Accounts. The number itself does not change, and Meta registers it on the destination WABA instantly so messaging continues.
Will my quality rating and messaging limits reset?
No. Meta preserves the phone number's display name, quality rating, messaging limit, and Official Business Account status, because the number itself is not changing. Template quality ratings are the exception: they reset to UNKNOWN for the first 24 hours after duplication, then regenerate if there is enough data.
Do my templates come with me?
Only templates that are both APPROVED and GREEN are duplicated into the destination WABA. Meta re-checks category correctness after duplication, so some can arrive REJECTED. Anything not approved, not GREEN, or over the destination WABA's template limit must be recreated and resubmitted.
Do I need my current provider's cooperation to leave?
For at least one step, usually yes. Two-step verification must be disabled on the number before migration can complete. If you own the WABA you can do that yourself in WhatsApp Manager; if your Solution Partner owns it, only they can.
Is there downtime during migration?
Phone number registration is instant, so sending and receiving continue. Template duplication takes time, so migrate templates first if template downtime matters to you.
Who pays for messages sent during the migration?
Messages delivered before migration completes are charged to the old Solution Partner. Meta also charges messages sent before completion to the old partner when they are delivered afterwards. Messages sent and delivered after completion are charged to the business customer.
Does my message history come with me?
Do not assume it does. Meta's migration documentation says uploaded media remains usable but does not promise chat-history transfer. Export anything you need before starting, especially when your BSP also provides the inbox where that history is stored.
Can I migrate a Coexistence number to a new provider?
It is more constrained than a standard migration. Meta warns that a prior shared credit line can block a partner switch, and provider-specific WABA rules differ. Confirm the source and destination WABA path with both providers, 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.
Sources
- Meta, Migrating a business phone number from one Solution Partner to another
- Meta, Migrating a client off a Multi-Partner Solution
- Meta, Onboarding WhatsApp Business app users
- 360dialog, WhatsApp Coexistence — provider-specific migration guidance
All checked 14 August 2026. Quoted passages are Meta's wording. Provider-specific Coexistence guidance and the absence of a Meta promise to transfer chat history are labelled explicitly rather than presented as universal Meta behavior.