Yes — your number can move from the WhatsApp Business App to the API, and customers who have it saved will keep reaching the same number. What happens to your chat history, and whether the app keeps working, depends on which of two paths you take. Coexistence keeps the app and adds the API to the same number; the classic port moves the number to the API alone. Vendors describe these paths contradictorily; Meta's platform documentation draws the line, and this guide follows it.
The short answer: your number can move — history depends on which of the two paths you take
Under coexistence, you connect your Business App number to the API through a provider's Embedded Signup flow. The app stays active, messages are mirrored between app and API, and you can choose to sync contacts and up to six months of one-to-one chat history into the platform. Under the classic port, the number is deregistered from the app and registered on the API alone: the app stops working for that number, and chat history does not transfer — it survives only in the backup or export you made beforehand. Both paths keep the number. Neither brings group chats across.
The problem: app limits today vs the fear of losing the number everyone has saved
The free app was built for one person on one phone. The account lives on a single handset, with linked devices as companions rather than independent team seats. Broadcast lists cap at 256 contacts. You cannot assign a conversation to a colleague, no shared record the team can search, and no CRM connection, so customer knowledge sits in one person's chat list.
The rational response is to move to the API. The emotional blocker is the number. It is printed on vehicles, shopfronts and invoices, and saved in thousands of customer phones. Owners refuse any move that sounds like starting again — and contradictory vendor answers turn that caution into indefinite delay.
Know which move you are making: classic port vs coexistence (table)
Most confusion comes from vendors describing one path while you picture the other.
| Question | Coexistence | Classic port |
|---|---|---|
| Same number? | Yes | Yes |
| Business App keeps working? | Yes, on the same number | No — deregistered from the app |
| Chat history in the new inbox? | Contacts plus up to 6 months of 1:1 history, if you approve sharing at onboarding | No — backup/export only |
| Group chats | Stay in the app; never sync to the API | Do not transfer |
| Who runs it? | A Meta Tech Provider or Solution Partner via Embedded Signup | Your chosen provider or BSP |
| Best for | Teams that still answer personally from the phone | Firms ready for a fully shared, API-only operation |
Choosing between providers is a separate decision, covered in our guide to choosing a WhatsApp Business API service provider in the UAE.
Before you touch anything: eligibility and backup checklist
Work through this list before any signup flow begins, whichever path you choose:
- App version: coexistence requires the WhatsApp Business App at version 2.24.17 or later on the phone that holds the number. Update first, then start.
- The phone must be present: the number's owner confirms the connection inside the app during Embedded Signup. Schedule the cutover when that person and phone are available.
- Business verification ready: Meta's business verification compares your legal business name against your documents. In the UAE, have the trade licence ready and expect the names to need to match exactly.
- Full chat backup: run a complete backup of the app, and export any individual chats you cannot afford to lose. On the classic port this backup is your only history.
- Contacts saved to the phone: make sure important contacts live in the phone's address book, not only inside chats.
- An inventory of what to rebuild: list your catalogue, quick replies, greeting and away messages, labels and broadcast lists. Note which ones your team actually uses weekly.
- Templates drafted: write your first message templates — appointment reminders, delivery updates, re-engagement — in English and Arabic where needed, ready for approval.
Path A — coexistence via Embedded Signup, step by step (keep the app, add the API)
One, choose a provider that supports coexistence onboarding and start its Embedded Signup flow; it is offered through Meta Tech Providers and Solution Partners, not self-serve. Two, sign in with the Facebook account that manages your business and select the option to connect an existing WhatsApp Business App account. Three, enter the number the app uses and confirm the connection inside the Business App on the phone when Meta prompts you. Four, decide the sharing prompts: Meta offers one-time requests to sync contacts and chat history at onboarding; history you decline then cannot be pulled later. Five, keep the app open while the sync runs and check the inbox: one-to-one threads and contacts should appear. Six, test both directions — a reply sent from the phone should appear in the platform (Meta calls these message echoes), and a platform reply should appear in the app. Seven, brief the team on the coexistence limits below.
Path B — classic port, step by step (API-only number)
One, finish the checklist above; on this path the backup is not a precaution, it is the archive. Two, export individual chats that carry commitments — quotes, agreements, addresses — because none will appear in the API inbox. Three, agree the cutover window with your provider: during deregistration and re-registration the number is in transit, so choose a quiet period. Four, deregister the number from the Business App by deleting the WhatsApp account in the app, as Meta's migration documentation directs. Five, your provider registers the same number on the platform and you complete the verification code step. Six, complete business verification with the trade licence and matching legal name. Seven, rebuild what the app held: business profile, catalogue, and quick replies rewritten as approved templates. Eight, reconnect the places the number appears — website chat links, ads, printed codes — and confirm each lands in the new inbox.
What syncs, what doesn't, and what never comes across (history, groups, catalogue, labels)
On coexistence, contacts and up to six months of one-to-one chat history sync when you approve it at onboarding, and every message is then mirrored both ways. On the classic port, nothing syncs: the new inbox starts empty. On both paths, group chats never come across to the API — under coexistence they simply continue living in the app. Under coexistence, Meta also restricts some app behaviours in one-to-one chats: broadcast lists become read-only, and disappearing messages, view-once media and live location are turned off. Expect to rebuild your catalogue and quick replies in the new platform; labels stay app-side and do not carry over. Once you are on the API, the next decision — connecting it to your CRM or a custom web application — is an architecture question of its own. Keep the pairing alive: Meta's documentation warns that a coexistence connection can drop if the Business App is not opened for around two weeks, and uninstalling the app disconnects the number.
Cutover day: sequencing, templates, messaging limits and telling your team
Run the cutover in your quietest window and staff it: the phone owner, the provider contact and one person answering customers. Get templates approved before cutover day, not after — outside the 24-hour customer service window you can only open conversations with approved templates, and Arabic templates deserve the same care as your click-to-chat Arabic prefill messages. Expect a new API number to start on a lower messaging limit; limits rise as you build a record of well-rated messages, and your quality rating falls if customers block or report you, so never celebrate cutover with a blast to an old list. On cost, follow Meta, not vendor summaries: since 1 July 2025 Meta charges per delivered template message, priced by category — marketing, utility or authentication — and by the recipient's country. Those are Meta's rates, published on Meta's own pricing page; any provider platform fee is charged on top, and any guide still quoting per-conversation prices describes the retired model. Tell the team which path you took, what changed in the app, and where history now lives.
Common mistakes that strand numbers or burn history
The classic error is deregistering the number before the backup and exports are verified — on the port path there is no undo. Next is declining the history sync during coexistence onboarding and asking for it a week later; the request is one-time. Teams start Embedded Signup on an outdated app version, or without the phone's owner present, and stall mid-flow. Others assume group chats, labels and the catalogue will follow the number. The quietest mistake is leaving coexistence to a handset nobody opens: the app must stay installed, or the connection drops.
FAQ
Can I keep the same number when I move to the WhatsApp API?
Yes, on both paths. Coexistence connects your existing Business App number to the API while the app keeps working. The classic port deregisters the number from the app and registers the same number on the API alone. Customers keep messaging the number they have saved.
Will my chat history transfer to the API?
Only under coexistence, and only if you approve sharing during onboarding: contacts and up to six months of one-to-one chat history sync into the connected platform. On the classic port, history does not transfer — it survives only in the backup and exports you made beforehand.
Can I use the WhatsApp Business App and the API at the same time?
Yes, but only through coexistence, connected via a provider's Embedded Signup with the Business App at version 2.24.17 or later. Messages are then mirrored between the app and the API. On a classic port, the app stops working for that number.
Do group chats, labels and my catalogue come across?
No. Group chats never sync to the API on either path, although under coexistence they continue in the app. Labels stay app-side, and the catalogue and quick replies should be rebuilt in the new platform rather than expected to import.
What documents does Meta ask for to verify a UAE business?
Meta's business verification checks your legal business name against official documents. For a UAE business, have the trade licence ready and make sure the legal name you submit matches it exactly, along with a business phone number and address Meta can corroborate.
Plan your app-to-API move (CTA)
If the app limits are costing you customers but the number feels untouchable, the path above is the way through: pick coexistence or the port, prepare the checklist, and cut over once. WebStackRank handles app-to-API migration as a one-off integration project — start with our WhatsApp Business API setup service, or contact us with your current app setup and the path you are considering, and we will reply with an itemised proposal within 24 business hours.
