Metrics and analysis
Coexistence or migration: which path to pick for your number
Keep the number in the app and the API at once, or take it out of the app for good. The honest comparison, what each costs, and when each is right.
Also available in: Português · Español
Anyone taking WhatsApp to the API finds two paths, and the difference between them is not technical. It is about who answers.
Migration removes the number from the app. It exists only on the Cloud API, and all support happens through whatever tool you connect.
Coexistence keeps both. The app keeps working, the team stays in it, and the API can read and send on the same number.
The comparison, without a thumb on the scale
| Migration | Coexistence | |
|---|---|---|
| WhatsApp Business app | stops working | keeps working |
| Who answers | only the connected tool | team in the app plus automation |
| Team retraining | required | none |
| Setup complexity | lower | higher |
| Reversible | hard | easier |
| Old history | stays on the device | part is synced |
| Conversation cost | same | same |
Notice migration wins on simplicity and coexistence wins on continuity. That is the whole trade.
When migration is right
You will run on a support platform. If the team will work inside a system with queues, assignment and centralized history, the app becomes redundant — and keeping both creates two inboxes, which is worse than one.
Volume outgrew the app. Above a few hundred conversations a day the app stops coping, and the team already feels it.
Support is mostly automatic. If 80% of interactions are transactional — confirmations, statuses, duplicate invoices — the human is the exception, and the app gets in the way.
You are starting from zero. New number, new operation, no team used to anything. Migrating is simpler and saves you coexistence's complexity.
When coexistence is right
The team works and you do not want to touch it. The most common case, and the reason coexistence exists. Swapping the tool out from under people who answer well is risk with no guaranteed return.
You want to automate part, not everything. Send the confirmation by system and leave the conversation to a person. The app stays the place where conversation happens.
The number is old and widely advertised. The more a number circulates, the higher the cost of anything going wrong. Coexistence is the lower-risk path.
You want to measure before reorganizing. Connect in order to see — where conversations come from, how many become sales — and only then decide whether the operation changes. That is a sensible sequence, and coexistence lets you do it without changing anything first.
The mistake of deciding on technical grounds
The discussion usually stalls on which is more "modern" or more "complete", and neither word decides anything.
The useful question is different: if nothing changes in the team's routine, does the project still make sense?
- If yes, coexistence. You want what the API gives without paying for the change.
- If no — if the value depends on the team switching tools — migrate, because the change will happen either way and keeping the app only delays it.
The hybrid path that works
A sequence that works well for mid-sized operations:
- Connect with coexistence. Nothing changes for whoever answers.
- Measure for three months. How many conversations, where from, how many become sales.
- Automate one thing. The most repetitive one, with the lowest risk.
- Reassess. With data in hand, the decision to migrate stops being an opinion.
The advantage is that steps 1 and 2 require no hard decisions, and step 4 is where you find out whether the app is still needed. Plenty of operations get there and realize they barely use the app any more — at which point migration is a consequence, not a bet.
What does not change either way
Worth stating, because the expectation sometimes runs otherwise:
Sending rules. A business-initiated message outside the 24-hour window needs an approved template, on both paths.
Cost per conversation. WhatsApp's billing does not depend on whether you are in coexistence or migrated.
Number quality. Blocks and reports drag the rating down the same way in both. The piece on WhatsApp number quality covers it.
Summarizing the decision
If you answered yes to most of these, coexistence:
- the team answers well through the app today
- the number is old and widely advertised
- you want to automate part, not everything
- you want to measure before reorganizing
If you answered no to most, migration — and probably alongside a support platform.
For the list of what has to be ready before connecting with coexistence, see coexistence requirements.
Frequently asked questions
Is migration better than coexistence?
Neither is better in the abstract. Migration is simpler and removes the app; coexistence keeps the team where it already is. The choice depends on who answers today and how you want them answering tomorrow.
Can I migrate after using coexistence?
Yes. Coexistence is not a dead end: if the operation matures and the app stops being used, migrating the number is the natural next step.
Is coexistence more expensive?
Platform cost is the same, because WhatsApp charges per conversation. The cost difference lives in the tool you run on top, not in the path you choose.
Do I lose history either way?
With coexistence, part of the recent history is synced at the start. With migration, old conversation content does not travel — the number moves, the old messages stay on the device.