The quick answer
Eligible businesses can use an existing WhatsApp Business App number with the Cloud API through a supported coexistence onboarding route. Availability depends on the account and integration. Check eligibility, supported features and history handling before changing the number you rely on.
Your WhatsApp number is printed on packaging, saved in customer phones and attached to years of relationships. Moving to a team platform should start with protecting that continuity, not with deleting the account or buying another number in a hurry.
Coexistence is one possible route. It lets an eligible business connect an existing Business App account to the platform while retaining app-based use. The important work is checking what your particular account can do and preparing a transition your staff can understand.
Identify which situation your number is in
First establish whether the number is in the WhatsApp Business App, already connected to an API provider, or unused for WhatsApp. These are different onboarding situations. A business moving between API providers needs a migration assessment; that should not be confused with connecting the Business App through coexistence.
Ask the person who controls the business assets to participate. You need to know who owns the number, who can receive verification messages, and who has administrative access to the relevant Meta business account. A staff member knowing the phone PIN is not the same as the company controlling its business assets.
| Starting point | First question | Preparation |
|---|---|---|
| Business App number | Is this account eligible for coexistence? | Keep the app accessible and review current features |
| Existing API number | What does the current provider migration require? | Identify ownership, account access and service dependencies |
| New number | Can the business verify and retain control of it? | Confirm number access and business details |
Understand what coexistence does—and does not promise
Meta documents coexistence as an Embedded Signup option for eligible WhatsApp Business App accounts. The business completes the supported connection process and can continue using the app alongside Cloud API messaging. Historical synchronization requires permission and has limits; it is not an unlimited archive import.
The same number does not make every app feature available inside another platform. For example, Meta’s comparison distinguishes individual chat synchronization from group chat support. Some app behaviours change after onboarding. Review the current official feature table with your implementation team before promising the staff that nothing will change.
In your project checklist, separate “can connect the number” from “can operate our complete process.” You may successfully connect and still need to set agent ownership, import business data, approve templates, map customer fields and train the team. A connected status is the beginning of the operating setup.
Prepare a number transition checklist
List the places where the number appears: website, printed materials, advertisements, receipts, directory listings and team signatures. Keep that inventory even if you expect to retain the number. It is useful if an unexpected account issue requires you to explain a temporary service change.
Review the conversations the business must retain for customer service and recordkeeping. Decide what must be present in the new platform, what can remain in an authorised existing archive, and who can access either. Do not assume a phone backup can be imported as a complete team timeline.
Choose a quiet period for the connection and appoint one decision maker. Have a support contact and a written recovery route ready. Avoid running a major sale, changing provider, editing number ownership and training new agents on the same afternoon.
- Confirm company ownership and administrator access.
- Keep the existing app and verification channel accessible.
- Inventory active automations, templates and customer commitments.
- Agree what evidence proves a successful transition.
- Tell staff which inbox they should use during the change.
Use the supported onboarding route
Follow the connection flow supplied for your account. Read the business and number selections carefully, and make sure the company representative approves the intended assets. If an existing-number option is absent or the account is rejected, stop and investigate eligibility instead of repeatedly disconnecting assets.
Never share a one-time code with a stranger or paste business credentials into an informal form. Your implementation partner should explain what you are approving and why. Keep a record of the selected account and number so support can distinguish a configuration problem from a customer using the wrong workspace.
After the connection, confirm the business name, profile information and team access. Then assess history and new messages separately. Old records appearing in the interface do not prove that fresh messages are arriving; a fresh test reply does not prove the historical data you need was synchronized.
Test the customer journey before announcing success
Use consenting internal test contacts. Send a new enquiry, assign it to a colleague, reply, attach a small file and check the contact record. Confirm that the right staff can see the conversation and that another business workspace cannot. Capture the expected result beside every test.
Test app-based and platform-based work independently if both will remain part of daily operations. Decide where notes, ownership and follow-up tasks live. A business can create confusion when two people answer through different surfaces without knowing who is responsible.
For campaigns or follow-ups, confirm template status and current messaging rules before using a real audience. A newly connected number is not permission to contact everybody in the phone. Keep business continuity, customer expectations and distribution readiness as three separate checks.
Receive
A consenting test customer sends a fresh enquiry.
Work
An agent receives ownership, replies and records the next step.
Verify
Check both the customer’s phone and the platform timeline, including any synchronization delays.
Get clear answers before committing to a provider
Ask for the account-specific onboarding route, supported app features, history scope, likely transition steps and recovery process. Ask who owns the business assets after connection and how you would leave the provider later. The answer should be understandable to a business owner, even if the support team also needs technical identifiers.
For Wamigos, arrange a walkthrough of the route available to your business. Coexistence and onboarding depend on Meta eligibility and the approved integration configuration. This article explains how to prepare; it does not guarantee that every account can connect immediately.
Common questions
Do I need to delete my WhatsApp Business App account first?
Do not delete it as a routine preparation step. Ask which supported route applies to your number; coexistence is designed for eligible existing Business App accounts.
Will every old chat appear in the new platform?
Do not assume so. Confirm the available synchronization period, permissions, message types and completion evidence for your account before relying on a historical record.
Is moving from another API provider also coexistence?
It is a different starting situation. Review the existing provider arrangement, asset ownership and migration requirements before making changes.
Can my team keep using both interfaces?
Where supported by your account configuration, app and platform use can coexist. Agree a clear operating process so ownership and customer replies stay coordinated.
Does keeping the number make campaigns automatically compliant?
No. Connection, recipient permission, approved content and current distribution rules remain separate checks.
Sources & further reading
Primary documentation reviewed 16 November 2026. Provider rules, pricing and eligibility can change. Check the linked source before making account or billing changes.






