WhatsApp Coexistence vs Migration: Which Should You Choose?
Coexistence keeps your Business app running alongside the API; a full migration moves the number over for good. Here is how to pick the right one for your team.
Short answer: choose coexistence if you still handle chats by hand and want to keep your Business app, contacts, and history while adding automation; choose a full migration if you are a high-volume sender who no longer needs the app and wants maximum throughput. Coexistence is the low-risk on-ramp with a way back; migration is the one-way door to the full API. Most small teams should start with coexistence.
Since Meta launched coexistence in May 2025, connecting a number to the WhatsApp Business API is no longer a single all-or-nothing move. You now have two genuinely different paths, and picking the wrong one either caps your sending or wipes an app you still need. Here is how they actually differ and how to decide.
The two paths in plain terms
Coexistence links your existing WhatsApp Business app number to the Cloud API while the app keeps running on your phone. New messages sync in both directions, your saved contacts carry over, and you gain template campaigns, scheduling, and a shared inbox. It is covered in full on our WhatsApp coexistence page.
Full migration registers the number to the WhatsApp Business Platform and removes it from the app entirely. Nothing imports, you start with an empty inbox, and in exchange you get the highest sending speed and every API feature with no coexistence restrictions.
Side by side
| Question | Coexistence | Full migration |
|---|---|---|
| Keep the Business app? | Yes, it keeps working | No, the number leaves the app |
| Keep contacts and chats? | Contacts and new chats sync | Nothing imports; fresh start |
| Sending speed | Around 20 messages per second | Up to 80+ per second, upgradable |
| Groups, Status, catalog, Pay | Stay in the app, app-only | Not available |
| Reversible? | Yes, the app is still there | No, it is a one-way move |
| Best for | Small teams adding automation | High-volume senders going all-in |
How to decide in five questions
- Do you still answer customers by hand in the app every day? If yes, lean coexistence. Losing the app would disrupt real relationships.
- Are your contacts and chat history valuable? If losing them would hurt, coexistence keeps them; migration does not.
- How fast do you need to send? If a campaign of a few thousand messages spread over minutes is fine, the roughly 20-per-second coexistence cap is plenty. If you push tens of thousands in a tight window, migration's higher throughput matters.
- Do you rely on Status, groups, catalog, or WhatsApp Pay? Those stay app-only under coexistence and disappear under migration, so weigh which features you actually use.
- Are you sure about the change? If you want to test API automation before committing, coexistence gives you a clean way back. Migration does not.
The path many teams actually take
A common and sensible route is to start with coexistence, learn how templates, scheduling, and a shared inbox fit your workflow, and grow into a full migration only when your volume genuinely outgrows the cap. That way you never gamble your customer base on a tool you have not tried. When you are ready to scale, our WhatsApp Cloud API guide walks through the full setup.
What each path costs
The path you pick does not change Meta's core billing, but it changes how much of your sending is free. On both paths, messages you send from the WhatsApp Business app are always free, and utility templates delivered inside an open 24-hour customer service window carry no Meta fee. Where they differ is volume and behavior:
- Coexistence keeps more of your traffic on the free app side, because you are still answering many chats by hand there. You pay Meta only for the approved templates your platform sends, billed per delivered message by category and recipient country.
- Full migration pushes everything through the API, so more of your sending is billable template traffic, but you get the throughput to run large campaigns that would choke a coexistence connection.
Neither path has a Meta platform subscription fee; you pay per delivered template plus whatever your sending platform charges. For a rough US benchmark, a delivered utility template runs in the low single-digit cents through providers that publish rates. Model your monthly template volume, not your total chat volume, since app-side replies stay free on both paths.
Two quick scenarios
A local clinic that answers most patients by hand and sends a few hundred appointment reminders a week should coexist. It keeps the app its front desk already uses and pays only for the reminder templates. A promotions-heavy retailer blasting tens of thousands of opted-in template messages in tight windows should migrate, because the 20-per-second cap would stretch a large send across too long a window.
Where US rules fit in
Neither path enables US marketing blasts today. Meta paused marketing template delivery to US phone numbers in April 2025, and that applies whether you coexist or migrate. Utility templates and support replies inside the 24-hour window still deliver to US numbers on both paths, so your transactional messaging works the same either way. The choice between coexistence and migration is about the app and throughput, not about which US messages you can send.
Do not stop at one channel
Whichever path you choose, WhatsApp is one lane. As you scale outreach it often pays to run a complementary channel, and putting the rest of your outbound email on autopilot keeps prospects warm between WhatsApp touches without adding manual work. Treat the platform decision as the foundation, then layer channels on top.
The rule of thumb: coexistence when you want to keep what you have and add to it, migration when you are ready to leave the app behind for speed. For most small and mid-size US teams, coexistence is the smarter first step.
Common questions
Can I move from coexistence to full migration later? Yes. Coexistence is a starting point, not a ceiling. When your volume outgrows the roughly 20-per-second cap, you can move the number to a full API setup. Plan for the app to drop off at that point, since full migration removes it.
Is coexistence slower than migration? For sending, yes. Coexistence tops out near 20 messages per second while a full API setup starts higher and can be upgraded. For a few thousand messages that difference is a matter of seconds; for very large blasts it becomes minutes, which is when migration starts to pay off.
Does migration give me features coexistence does not? Migration removes the coexistence restrictions and gives you the full throughput and feature set, but it costs you the app, your synced contacts, and your history. It is the right trade only when you no longer need the app side at all.