WhatsApp Coexistence vs Migration: Three Paths, Three Different Rulebooks
Coexistence keeps the Business App and Cloud API on one number. An App-to-API-only move gives up the app for standard Cloud API capacity. Moving a number that is already on the API between providers or WABAs is a third operation, with different asset-preservation rules.
Do not use “full migration” without saying which migration you mean. Business App to API-only and existing API/WABA to another WABA do not preserve the same data or assets.
First separate the three operations
Coexistence
Onboard an existing Business App number to Cloud API while the app stays active.
App → API-only
Move the number off the Business App and register it solely on Cloud API.
WABA → WABA
Move a number already on the Business Platform to a new provider or destination WABA.
This guide uses Meta's current coexistence rules and Dualhook's vendor-neutral WABA migration checklist, checked on 30 August 2026. Provider-specific coexistence constraints are labeled as such.
Business App to coexistence vs API-only
| Decision point | Coexistence | API-only |
|---|---|---|
| Phone number | Kept | Kept |
| Business App one-to-one use | Kept | No longer available for that number |
| Existing app history | Up to 180 days syncable; groups excluded | No coexistence history-sync path |
| Throughput | Fixed at 20 mps | Standard Cloud API tiers; not fixed at 20 mps |
| Calling | Business App calls only; no Cloud API Calling | Cloud API Calling available when eligible |
| OBA / blue verified badge | Provider documentation says OBA is unsupported; Meta Verified is separate | Available through the normal eligibility process |
| Catalog, labels, quick replies, away messages | Keep working in the app; not exposed on Cloud API | Business App tools are no longer available on that number |
| Companion devices | Unlinked during onboarding; supported devices can be relinked | Not applicable |
| Onboarding gate | Onboarding party must be a Solution Partner or Tech Provider | Standard Cloud API onboarding |
What a WABA-to-WABA migration preserves
When the number is already on the Business Platform, Meta can carry the phone number, approved display name, phone-number quality rating, template messaging limit, OBA status, and eligible approved templates to the destination. These rules do not describe a number that has only ever lived in the Business App.
Template quality ratings do not carry over initially. Templates can also be excluded if they are not approved and green, exceed the destination WABA's limit, or fail Meta's category re-check. Meta does not promise to transfer chat history.
Prerequisites that can block the migration
- A verified Meta Business Account.
- An approved destination WABA with a valid payment method.
- Two-step verification disabled on the phone number.
- An approved display name with no pending change.
- A production Cloud API number, not a Meta test number.
Two-step verification is often the practical dependency on the old provider when the business does not control the source WABA. Resolve it before scheduling the cutover.
Billing and downtime at cutover
The source connection remains active until final registration, so a migration need not start with a long outage. Still plan a controlled cutover: stop nonessential sends, register the destination, validate inbound webhooks and templates, then resume traffic.
Billing follows when the message was sent, not when it was delivered. A message sent before completion remains chargeable through the source arrangement even if delivery happens afterward. Messages sent after completion use the destination arrangement.
Coexistence partner and credit-line constraints
Meta warns that a business that previously worked with a partner and still shares that partner's credit line may hit an error when switching. Respond.io documents that its coexistence credit line cannot simply be reassigned to another BSP under the same WABA ID. 360dialog documents WABA-to-WABA migration as unsupported for its coexistence numbers.
Owning the WABA and phone number reduces provider lock-in, but it does not erase Meta's partner-state rules. With Dualhook, a stale relationship can surface as Embedded Signup error 2655093 before Dualhook receives access. The safe sequence is to update the Business App, disconnect the old platform under Settings, Account, Business Platform, wait for the relationship to clear, and obtain full offboarding from the old provider. Do not delete the number or WABA as a first troubleshooting step.
Can you change paths later?
- Coexistence to API-only:possible as a planned migration, not a simple dashboard toggle.
- Coexistence to app-only:disconnect the platform in the Business App. Meta emits a
PARTNER_REMOVEDaccount update. - Deregister API: Meta explicitly blocks it while the number is active on both the app and Cloud API.
Which path should you choose?
- Keep app-side one-to-one chats and app calling: choose coexistence.
- Need sustained throughput above 20 mps or Cloud API Calling: choose API-only.
- Already on Cloud API and changing vendor: plan a WABA migration.
- Need an OBA: verify the current API-only route and eligibility with Meta.
- Concerned about lock-in: own the Meta assets and audit credit-line state before signing.
Frequently asked questions
Is WhatsApp Coexistence the same as migrating to the API?
No. Coexistence keeps the WhatsApp Business App and Cloud API active on the same number. API-only onboarding removes app use for that number. Moving an already-API number between WABAs or providers is a third migration with its own preservation rules.
Does chat history move?
Coexistence can synchronize up to 180 days of one-to-one Business App history when requested within 24 hours. Meta does not promise chat-history transfer for a WABA-to-WABA migration, and standard App-to-API-only onboarding does not use the coexistence history-sync path.
Do approved templates survive a BSP-to-BSP migration?
Eligible approved templates can be duplicated to the destination WABA. Template quality ratings reset initially, and templates can be excluded because of status, quality, destination limits, or Meta's category re-check.
Does a provider migration have zero downtime?
The source connection remains active until final registration, which limits disruption, but you should still plan a short controlled cutover and test inbound and outbound traffic after registration.
Why can switching a coexistence provider fail?
Meta says a previous shared credit line can block switching. Provider documentation also describes coexistence-specific partner and WABA constraints, so owning your Meta assets reduces lock-in but does not eliminate every credit-line or partner-state issue.
Can Cloud API Calling be used on a coexistence number?
No. Calls can continue in the WhatsApp Business App, but Cloud API Calling requires an API-only number.
Can coexistence be undone?
Yes. The business disconnects the platform from Settings, Account, Business Platform in the WhatsApp Business App. Meta does not allow the Deregister API on a number actively used by both the app and Cloud API.