MessagingUAE & KSA7 min read
WhatsApp Number Migration: Keep Your Number on the API
WhatsApp number migration for UAE and KSA businesses: keep the number customers know when moving from the app to the API. Two routes, compared.
By Quickship Editorial Team · Published
Looking for the software itself? See our WhatsApp Business API UAE, free to try for 3 days.
WhatsApp number migration means moving the number your customers already message from the WhatsApp Business app to the Cloud API, without giving them a new one. Meta gives you two routes. You can delete the app account and register the number on the API (chat history is lost), or you can onboard through a partner that supports Business app numbers, so the app and the API run side by side.
If your number is printed on trade licences, delivery bags, Instagram bios and noon or Shopify store pages, losing it costs you more than any software saves. So pick the route before you touch the app.
What are the two routes for WhatsApp number migration?
Meta's migration guide says a Business app number can go to the Cloud API in only two ways. You delete the account, or you onboard through a partner that supports Business app number onboarding. Partners call the second one "coexistence". Meta's own name is "Onboard WhatsApp Business app users".
| Delete and register | Coexistence | |
|---|---|---|
| Chat history | Lost, so back up first | Kept, and synced to the API side |
| App and API at the same time | No | Yes |
| Can you go back to the app only? | Only after you deregister the number from the API | You keep using the app |
| Who does it | Provider or you | Must go through a Solution Partner or Tech Provider |
| Main risk | Gap in service, lost history | Features change, number can disconnect |
Short version: if history and day-to-day chats on the phone matter, ask for coexistence. If you want a clean break and a fully automated inbox, deleting is simpler.
How does the coexistence route work?
Coexistence lets one number work in the Business app and on the API at once. Messages sent and received are mirrored between the two, per Meta's documentation.
You can't switch this on from inside the app alone. Meta's Embedded Signup overview says it goes through a Solution Partner or Tech Provider. Meta converts your existing WhatsApp Business account into a backward-compatible Messaging account and shares it with the provider. The number is already registered, so the register step is skipped.
Here is the usual order:
- Update the Business app. Meta requires version 2.24.17 or higher.
- Check the basics with your provider. Providers report the number must have been active in the Business app for at least 7 days, and you need a smartphone with a camera for the QR code. One provider says Meta publishes no fixed country list, so eligibility is confirmed per number during onboarding. I found no UAE or KSA exclusion, but check yours.
- Back up your chat history from the app anyway.
- Start Embedded Signup through your provider. Meta's changelog says the flow now enters coexistence automatically when the number is already in the Business app and coexistence is enabled.
- Scan the QR code on the phone that holds the app.
- Choose whether to share chat history. Meta's page covers options for a customer who shares history and one who declines.
- Add billing. Meta's Tech Provider docs say clients must add a credit card to the WhatsApp Business Platform account.
- Send one test message in each direction before you tell the team it's live.
What changes in the app after coexistence?
Some app features change, and the phone has to stay in use. This is the part owners miss.
- Speed limit. Meta says numbers used with both the app and Cloud API have a fixed throughput of 20 messages per second. For most UAE and KSA sellers that's plenty. A big campaign to a large list is where you'd feel it.
- Phone must stay active. One provider reports Meta disconnects the number after about 14 days of inactivity, and reconnecting means onboarding again. Don't leave the app phone in a drawer at the Sharjah office.
- History sync. Providers report contacts and up to 6 months of one-to-one chats sync once, within 24 hours of onboarding, and group chats are not synced.
- Disabled features. Providers report that for individual chats, broadcast lists, disappearing messages, view once and live location stop working. Groups are not affected. Meta's page has the official table of changed features, so read that before you commit.
If your team uses broadcast lists today, plan the replacement now. Broadcasts to opted-in contacts, sent with approved templates through the API, are the route that fits Meta's rules and UAE and Saudi privacy expectations. Never upload a list of people who didn't ask to hear from you.
What happens if you delete the app account instead?
If you delete the account, your messaging history is lost and the number can't go back into the Business app unless you deregister it from the Cloud API. Meta is clear about this in its migration guide.
The steps:
- Export or back up chats from the Business app.
- Save your catalogue items, quick replies and labels somewhere safe. You'll rebuild them on the API side.
- In the app, go to Settings > Account > Delete my account.
- Wait. Meta says the disconnected number can take up to 3 minutes to become available. Messages sent to it are queued meanwhile.
- Register the number for Cloud API through your provider.
- Send a test message.
Providers report that some contacts see "This person no longer uses WhatsApp" after a deletion. An approved template message to opted-in contacts fixes that. Do the switch outside your busiest hours. A restaurant in JLT should not do it at Friday lunch, and a COD-heavy seller should avoid the day after a big sale.
Which route fits which business?
Say a Dubai online seller has three staff answering order questions from one phone, and sells on noon and its own Shopify store. The owner wants an automated order-status reply, but the team still likes the app on their phones. Coexistence fits.
Now say a courier company in Jeddah gets thousands of tracking requests a day and wants every chat inside a shared inbox with routing. The app is a bottleneck. A clean delete and register fits, as long as they accept the history loss.
A quick test:
- Do staff need the app in their hands? Coexistence.
- Do you need old chats on screen? Coexistence, or back up and accept the loss.
- Do you need heavy automation and many agents? Delete and register, or coexistence with a plan to move fully later.
- Is the number a personal one? Convert it to the Business app first, per providers, or use a new number.
If you want one inbox for WhatsApp, Instagram and Messenger, that's what our Meta Messaging Module is for. Whichever provider you pick, ask them in writing whether they support Business app number onboarding. Not all do.
What will messaging cost after the move?
Meta charges per message, and rates depend on the market and message category. Check the official pricing page for current UAE and KSA rates, because rate cards change and Meta needs to give at least one month's notice.
What I could confirm from Meta's pages:
- AED and SAR billing currencies were introduced, per the changelog.
- Visa and Mastercard credit and debit cards are accepted from 8 September 2026.
- Service message rates equal utility and authentication rates per market, according to Meta's non-template pricing page.
Provider blogs report figures for the 1 October 2026 rate card. These are not from Meta's pages, so treat them as a guide only. As reported by providers, marketing messages are about USD 0.0576 in both the UAE and KSA. Utility is about USD 0.0157 in the UAE and USD 0.0107 in KSA. Confirm against Meta before you budget.
What mistakes should you avoid?
- Deleting before backing up. No backup, no history.
- Skipping the eligibility check. Confirm the number is accepted before you plan a launch date.
- Leaving the app phone idle. The coexistence number can disconnect.
- Messaging people who never opted in. Moving to the API doesn't change who you're allowed to message. Opted-in contacts only, tied to something they asked about, with a clear opt-out.
- Planning a second move too early. Provider-to-provider moves exist, but Meta's process can't migrate numbers in use with the Business app, and numbers move one at a time.
- Forgetting templates. Outside the 24 hour window you need approved templates. Write and submit them before cutover.
Pick your route this week, list your broadcast lists and quick replies, and ask your provider the eligibility question in writing. Then book the switch for a quiet day.
Frequently asked questions
Will my customers see a new number or a new chat after the move?
No. The chat stays on the number they already saved. With the delete route, some contacts may briefly see "This person no longer uses WhatsApp", according to one provider. Sending an approved template message to opted-in contacts is the usual fix.
Can I move a personal WhatsApp number to the API?
Providers report that a personal number must first be converted to the WhatsApp Business app, or you start with a new number. Once it is a Business app number, either route above applies. Check with your provider before you start.
Can I move several numbers at once?
Meta's guide for switching between providers says there is no bulk migration and numbers move one at a time. Plan one number per onboarding, and start with the least busy line.
Can I switch API provider later and keep the number?
Yes, for numbers already on the API, Meta has a process to move numbers between Solution Partners. It cannot migrate numbers that are in use with the Business app, so finish your first move before you think about a second one.
Do I need a Facebook account to onboard?
Usually the flow uses a Facebook login. Meta's changelog lists a beta that lets coexistence onboarding use the Business app account instead. Ask your provider whether it is available for your number.
Sources
- Meta: Migrate an existing WhatsApp number to a business account
- Meta: Onboard WhatsApp Business app users (coexistence)
- Meta: Embedded Signup overview
- Meta: Get started for Tech Providers
- Meta: WhatsApp Business Platform pricing
- Meta: Migrating phone numbers among Solution Partners
Rules and fees in the UAE and Saudi Arabia change. This guide reflects the sources above on 17 November 2026. Check the official source before acting on it.
