How to Migrate from WhatsApp Business App to the API (2026)

If you have outgrown the free WhatsApp Business App and want to send to thousands of contacts, automate replies, or connect multiple team members, you move to the WhatsApp Business API (also called the Cloud API). But in 2026 you usually do not have to throw the app away to do it.

There are two paths, and choosing the right one is the whole decision:

1. Coexistence (recommended for most): You keep using the WhatsApp Business App on your phone and connect the same number to the API at the same time. Your team keeps chatting from the phone; the API handles broadcasts and automation. Nothing is torn down.
2. Full migration: The number is fully moved onto the API and the Business App on that number is deactivated. You handle all conversations through an API inbox instead of the phone app.

This guide walks through both, but for almost every small business the honest recommendation is: start with Coexistence. It is lower risk, keeps your phone working, and lets you adopt the API gradually. You can sign up and connect your number in minutes at payperwa.com/signup.

The Business App is excellent and free, but it was designed for a single person replying from one phone. You should move to (or add) the API when you hit any of these walls:

1. Broadcasts are failing silently. The app's broadcast lists are capped at 256 recipients and only deliver to people who have saved your number. If most of your customers have not saved you, your messages quietly never arrive.
2. You need more than one agent. The Business App ties the number to a single phone. The API lets a whole team work the same number from a shared inbox.
3. You want automation. Chatbots, auto-replies, drip sequences, and order/payment notifications all require the API.
4. You need delivery reports. The app gives you ticks; the API gives you campaign-level sent, delivered, read, and failed counts.
5. You are scaling. Sending hundreds or thousands of template messages per day is exactly what the API was built for.

If none of these apply yet, stay on the free app. Migration is a tool for growth, not a box to tick. For the bigger picture on what the API unlocks, see our features overview.

Coexistence is a Meta feature that lets one phone number run on the WhatsApp Business App and the Cloud API at the same time. You do not lose the app. Your owner or staff keep replying to day-to-day chats from the phone exactly as before, while the API layer (through a platform like PayPerWA) handles bulk template broadcasts, automation, and a shared team inbox on top of that same number.

The practical effect: messages sent and received in the app sync with the API side, so your team is not split across two disconnected tools. It is the lowest-friction way to add API power without disrupting how you already work. We cover the mechanics in depth in WhatsApp Business App Coexistence mode.

Full migration is the older, all-or-nothing route: the number is registered entirely on the API and the Business App on that number stops working. Everything then happens through an API inbox. This is the right choice when you no longer want anyone using the phone app at all — for example, a pure call-centre setup — but it is more disruptive, so most businesses choose Coexistence first.

Spend ten minutes here and the rest is smooth. Confirm the following before you connect anything:

1. Decide the number. You can connect your existing Business App number, or use a brand-new number. Most people keep their existing one so customers see no change.
2. Have a Facebook Business Manager. Meta requires a verified or verifiable Business Manager to run the API. If you do not have one, you can create it during onboarding.
3. Back up anything critical from the app. Export labels, saved replies, and your catalogue if you rely on them, because some app-only features do not carry over (see the section below).
4. Note your opt-in source. Outbound marketing on the API requires that contacts opted in. Make sure you can point to where each contact agreed to hear from you.
5. Pick your platform. The Cloud API is raw infrastructure; you connect it through a platform that gives you an inbox, campaigns, and billing. That is what PayPerWA does — no subscription, just pay per message.

Here is the full process. With Coexistence, the embedded signup flow keeps your app alive automatically — you do not flip a separate switch.

1. Create your PayPerWA account. Go to /signup and register your business. This takes a couple of minutes.
2. Start the WhatsApp connection. From the dashboard, click Connect WhatsApp. This launches Meta's official embedded signup, hosted by Facebook, so your credentials stay with Meta.
3. Choose Coexistence or new setup. If you want to keep the Business App on your number, pick the Coexistence path and select your existing number. If you are starting fresh, add a new number.
4. Verify the number. Meta sends a verification code by SMS or call. Enter it to prove you control the number.
5. Select your Business Manager and WABA. The flow links the number to your WhatsApp Business Account (WABA) under your Business Manager. Create one inline if needed.
6. Approve permissions. Grant the permissions Meta requests so the API can send and receive on your behalf.
7. Confirm Coexistence is active. Once connected, send a test broadcast from PayPerWA and reply to a chat from your phone — both should work. That confirms the app and API are coexisting on the same number.
8. Recharge your wallet. Add a starting balance so campaigns can send. PayPerWA is prepaid — you only ever spend what you load.

That is it. There is no waiting weeks for a Business Solution Provider; the whole thing is self-serve. See the docs for screenshots and edge cases.

Yes. The biggest fear businesses have — losing the number their customers already know — is unfounded. Whether you choose Coexistence or full migration, you keep the same phone number. Customers see no change in how they reach you.

What you must understand is the one-number-one-place rule for full migration: a number registered on the API in full-migration mode cannot also be logged into the consumer WhatsApp app or the Business App at the same time. Coexistence is the exception that Meta built specifically to let both run together. So if keeping the phone app matters to you, Coexistence is the path that preserves it.

This is where expectations need to be realistic. Your existing one-to-one chat history lives on the device and in WhatsApp's backup, not on the API. The API is a forward-looking pipe: it manages conversations from the moment you connect onward.

1. Coexistence: Because the app stays active, your old chats remain visible in the phone app, and new conversations sync between the app and the API inbox. You do not lose access to past threads.
2. Full migration: Past chat threads in the app are not transferred into the API inbox. You start with a clean conversation log on the API side. Back up anything you need to keep for reference before you fully migrate.

For most businesses this is fine — you rarely need yesterday's small talk inside the new system. But if your old threads are operationally important, Coexistence is the safer choice precisely because it keeps the app and its history alive.

Once you are on the API, several things work differently. The table below summarises the practical day-to-day differences so there are no surprises.

The headline: the API trades a few app-only conveniences (Status, in-app catalogue editing) for scale, automation, teamwork, and reporting. Coexistence lets you keep the conveniences while gaining the scale.

Unlike the free app, the API charges per message — but with PayPerWA there is no subscription. You pay two clearly separated amounts on every message:

1. PayPerWA platform fee: ₹0.20 per message in India, or $0.004 per message internationally.
2. Meta's per-message charge: set by Meta, not us. In India that is Marketing ₹0.86 and Utility ₹0.13 per message. For other countries the rate varies — see /pricing/rates.

So a marketing message in India costs you Meta ₹0.86 + PayPerWA ₹0.20 = ₹1.06 total, shown transparently and broken out. A utility message is Meta ₹0.13 + PayPerWA ₹0.20 = ₹0.33. Inbound replies you send within the 24-hour service window do not incur a Meta conversation charge. Because the wallet is prepaid, you are never billed a flat monthly fee — you only spend on messages you actually send. Full numbers live on the pricing page.

A few avoidable errors trip people up. Steer clear of these:

1. Full-migrating when you only needed Coexistence. If you still want staff replying from the phone, do not fully migrate — you will deactivate the app unnecessarily.
2. Broadcasting to non-opted-in contacts. Outbound marketing requires opt-in. Sending cold blasts gets your number flagged and risks quality-rating drops.
3. Forgetting to back up app data. Export labels and catalogue items before a full migration.
4. Not loading the wallet. A connected number with an empty wallet cannot send campaigns. Recharge first.
5. Skipping template approval planning. Marketing and utility messages need pre-approved templates; draft them early so a campaign is not blocked on approval.

Get these right and the move is painless. Ready to begin? Create your account and connect your number today.