WhatsApp Platform Alternatives: What Actually Happens When You Switch
Meta removed number migration between WhatsApp providers in September 2026. You now share one account with several platforms — what resets, and what it costs.
Este artigo está disponível em inglês.
Publicado em
If you looked at alternatives to your current WhatsApp platform earlier this year and decided the switch was not worth the disruption, the specific thing that made it disruptive has been removed. Meta began rolling out a new account model on September 23, 2026, and in that model a business phone number cannot be migrated from one provider to another at all. It does not need to be. Meta's own documentation describes the old migration process as having "acted as a natural switching barrier" and states plainly that it "no longer applies".
Here is the short version, because it is the part that changes decisions. Your number now sits in a WhatsApp account that you own, not your provider. Each platform you work with gets its own separate container for templates and billing. You can give a second platform access to the same number without removing the first, and without interrupting a single conversation. What does not travel with you is your template library: templates get recreated rather than moved, and recreating them resets their quality ratings and your messaging tier, which Meta says takes roughly two to four weeks to earn back.
Four different things people mean by "alternative"
Searches for a platform's alternatives collapse four separate problems into one phrase, and they have genuinely different answers. Working out which one you have saves a lot of wasted evaluation.
- Adding a second platform to the number you already use. This is now the cheapest option and most people do not know it exists. Sharing is additive, so your current provider keeps working while you test another one on the same number.
- Replacing your platform entirely. Still a real project, but the cost has moved. It is no longer a migration with downtime; it is a template rebuild and a quality ramp-up.
- Coming off an unofficial tool. If your current setup drives WhatsApp Web through a browser extension or an unofficial library, none of this applies to you, because you were never on the official API. You are not switching providers, you are onboarding for the first time, including business verification and display name review.
- Dropping the platform layer and going direct to Cloud API. Meta does not charge a platform fee. If you have engineers and your needs are narrow, this is the honest baseline every paid option should be measured against.
The switch that used to exist, and what replaced it
Under the old model your number lived inside a WhatsApp Business Account that was usually created and held by your provider. Leaving meant migrating the number to a different WABA, which is why the two documentation pages covering that process now open with the same warning: phone number migration is not supported for accounts on the new model, and the rest of those pages describes something that no longer exists.
The legacy WABA has been split in two. A WhatsApp account — Meta abbreviates it WAAC — holds the phone number, the business profile and the product catalogs, and it is always owned by you rather than by a partner. A Messaging account holds message templates, billing and webhook subscriptions, and each partner you work with gets their own. Your old WABA ID became your Messaging account ID, which is why existing integrations kept working through the change.
That split is what removes the barrier. Because the number is no longer tied to the template-and-billing container, a provider can be added or dropped without touching it. Meta's wording on whether you have to leave your current provider first is unusually direct: "Sharing is additive. Whether your client keeps their previous partner on the number or removes them later is their decision, and neither is a prerequisite for onboarding you."
What moves, what resets, what stays
| Asset | What happens when you add or change a platform |
|---|---|
| Phone number | Stays. It lives in your WhatsApp account and does not move. |
| Conversations in progress | Uninterrupted. Meta states existing conversations are not interrupted when a new partner is added. |
| Display name | Unchanged. Meta lists display names among what stays the same, and a new partner can change one without knowing your PIN. |
| Quality rating | Unchanged. Meta's asset table keeps it on the phone number before and after the split. |
| Messaging limit | Unchanged, and shared. It stays at business portfolio level — 250 unique recipients per 24 hours on a new portfolio, rising to 2,000, 10,000, 100,000 and then unlimited — and every partner on the number draws from that one allowance. |
| Throughput | Shared. Capacity sits at the phone number level, so two partners on one number divide the same throughput. |
| Message templates | Do not transfer. They belong to the Messaging account that created them, so a new platform starts with none. |
| Template quality and messaging tier | Reset to baseline on any template you copy across, with a ramp-up Meta puts at about 2–4 weeks. |
| Billing | Separate per platform. Each Messaging account has its own payment method and is billed for the messages its app sends. |
| Business verification | Unchanged. It sits on your business portfolio, not on the platform. |
Templates are the real bill
Everything on that list is free except the templates, so this is where an honest switching estimate comes from. Meta's Template Migration API exists to copy templates between Messaging accounts, and the documentation is careful about what it does: "Migration doesn't move templates; it recreates them in the destination Messaging account." Three limits decide whether it is any use to you.
- Same Meta business only. Templates can only be migrated between Messaging accounts owned by the same Meta business. If your current provider owns the account holding your templates, there is no API path out of it, and you rebuild by hand.
- Approved and green only. Only templates with a status of APPROVED and a quality score of GREEN or UNKNOWN are eligible. Anything that has picked up a yellow or red quality score has to be recreated and resubmitted, which puts it back through review and every rejection reason Meta can send.
- Batches of 500. The endpoint takes a zero-indexed page number and a count capped at 500, and it times out after 30 seconds, so large libraries go across several parallel calls. The response hands back a list of what succeeded and a map of what failed with reasons, which in practice are mostly category errors and dangling parameters.
The practical consequence is that a library of a dozen clean utility templates is close to free to move, and a library of two hundred marketing templates with mixed quality scores is a project. Count yours before you ask anyone for a quote, and remember that whatever you copy starts at baseline quality regardless of how well it performed before.
Running two platforms on one number
This is the part worth knowing even if you have no intention of switching, because it turns an evaluation into something you can do with real traffic instead of a sandbox. You can keep your current platform running and give a candidate access to the same number, then compare them on the same conversations. Four things to plan for.
- Throughput and messaging limits are shared, not duplicated. Two platforms on one number draw from one throughput capacity and one unique-users allowance. Meta's own warning about portfolio-level limits applies directly: "it's possible for one number to consume all of the portfolio's messaging capability within a given period". A heavy campaign on the new platform eats into what the old one can send.
- Each platform bills you separately. The charge goes to the Messaging account belonging to the app that sent the message, so you will see two invoices, and the comparison needs to account for both.
- Attribution needs a parameter once more than one Messaging account can send. Meta added messaging_account_id to the Messages API so it knows which account to bill and attribute. It is optional now and required from the next Graph API version in H1 2027. If your integration still sends paid_messaging_account_id, that alias is deprecated and Meta asks you to move off it by December 31, 2026.
- A credit line locks the account. If a provider attaches their credit line to a Messaging account you own, Meta's documentation says that account cannot then be shared with another partner. Worth asking about before accepting credit terms, because it quietly restores the lock-in the new model removed.
Moving numbers inside your own business
A related job that used to need migration and now does not: regrouping your own numbers. In Meta Business Suite, under Settings then Accounts then WhatsApp Accounts, select a primary WhatsApp account and open the Linked WhatsApp accounts tab, where numbers can be linked and unlinked. The number stays connected and keeps its conversations. The constraints matter more than the clicks.
- Both hierarchies have to be in the same business portfolio. A number cannot cross portfolios.
- Partners with access to a hierarchy can use every number in it, so moving a number changes who can send from it. This is the one to think about before reorganising.
- A number that is not already part of a hierarchy cannot be linked while it is shared with a partner or has its own Messaging accounts.
- You need permission to manage phone numbers on every hierarchy involved, and linking and unlinking are still rolling out, so the option may not be there yet.
What to compare, and three platforms people are comparing
Start with the baseline nobody sells you: Cloud API direct, with no platform in front of it. Meta charges per conversation and nothing for access — its rates vary by country, and that bill reaches you either way — so a team with engineering capacity and a narrow use case, order notifications triggered from one system say, can do that and should. What you give up is every operational surface a platform exists to provide: a shared inbox with assignment and history, template management that does not run through curl, campaign scheduling against consented audiences, and someone to call when your quality rating drops on a Friday. Price the alternatives against that, not against zero.
Among the platforms searched alongside us, three publish enough to compare honestly. Figures below are from each company's own pages, checked on November 17, 2026, and platform pricing changes often enough that you should re-check before deciding.
| Platform | Published platform price | What the price is based on | Channels |
|---|---|---|---|
| Kanal | €89, €149, €350 and €1,900 per month | Plan tier, with 1 seat on Pro, 5 on Scale and unlimited above; extra markets +€50/mo from Scale | WhatsApp, RCS, iMessage, SMS |
| Walytic | $4, $10 and $23 per month, billed annually | Message volume: 1,000, 10,000 and 50,000 messages a month | |
| WAX | Not published | Demo and quote | WhatsApp, RCS, SMS |
| WABPO | Not published | Usage-based, no platform fee to open an account | WhatsApp, Instagram, Messenger |
Where each of those genuinely wins
- Kanal is built around Shopify. Abandoned-cart recovery and post-purchase upsell flows running on Shopify data, EU hosting, and from the Business plan upward its team builds and keeps optimising the flows for you. If you run a Shopify store in the EU and want the campaigns operated rather than configured, there is nothing in our feature list that substitutes for that.
- Walytic has the lowest published entry price we found anywhere: $4 a month billed annually, for a thousand messages. If you want to put a real platform in front of the official Cloud API and find out whether any of this suits you before committing a budget, that is hard to argue with.
- WAX carries RCS and SMS next to WhatsApp. We do Instagram and Messenger, and we do not do either of those. If your campaigns need to fall back to SMS where WhatsApp is not available, that is a real gap on our side and not one we are going to close quickly.
Where WABPO fits, and where it does not
We are a Meta Tech Provider, and the reason we care about this account change beyond the SEO of it is that it is good for customers and awkward for providers. A model where you can add us without leaving anyone, test us on your own traffic, and remove us as easily, puts the burden on us to be worth keeping. We would rather compete on that than on how painful it is to leave.
Where we are the right answer: you are running WhatsApp alongside Instagram and Messenger and want one inbox and one set of campaigns across all three rather than a WhatsApp tool plus something else. That is the problem the product was built for, and it is the one place in the table above where we are the only option.
Where we are not: if you are a single Shopify store wanting someone else to run your commerce flows, Kanal is a better fit than us. If you need SMS or RCS fallback, we do not have it. If your WhatsApp need is one system firing order notifications and nothing else, go direct to Cloud API and keep the money. And if you have just moved platforms in the last month, do not move again yet — your templates are still ramping, and a second reset would cost you another two to four weeks for no reason.
Perguntas frequentes
Can I still migrate my WhatsApp number from one provider to another?
No, not on the new account model. Meta's documentation states that migrating a business phone number from one Solution Partner to another is not supported, and both migration guides now open with that warning. The replacement is sharing: your WhatsApp account can be shared with more than one partner, so the number stays where it is and there is no migration to perform.
Do I have to leave my current provider before onboarding a new one?
No. Meta's wording is that sharing is additive, and whether you keep your previous partner on the number or remove them later is your decision rather than a prerequisite. In practice this means you can run a candidate platform alongside your current one on the same number and compare them on real traffic.
Will my message templates transfer to a new WhatsApp platform?
No. Templates belong to the Messaging account that created them, and each partner gets their own, so a new platform starts with none. The Template Migration API can copy them, but only between Messaging accounts owned by the same Meta business, and only templates that are APPROVED with a GREEN or UNKNOWN quality score. Anything else has to be recreated and resubmitted.
Does switching reset my quality rating or messaging limit?
Not at the number level. Your display name, quality rating and messaging limit are unchanged, because they belong to the phone number and the business portfolio rather than to the platform. What does reset is template quality and messaging tier on any template copied into a new Messaging account, and Meta puts the ramp-up at roughly two to four weeks.
What happens to throughput if two platforms share one number?
They share it rather than each getting their own. Throughput stays at the phone number level and messaging limits stay at the business portfolio level, so two partners on one number draw from one capacity and one unique-users-per-24-hours allowance. A heavy campaign on one platform reduces what the other can send.
Is there anything that can still lock me into a WhatsApp provider?
Credit lines. Meta's documentation states that if a partner attaches their credit line to a Messaging account you own, that account cannot then be shared with another partner. That restores the switching barrier the new model removed, so it is worth asking about before accepting credit terms from any provider.
Escrito por
Saifullah AlamFounder — Spadasoft, WABPO & WAWCD
Saifullah Alam founded Spadasoft, WABPO and WAWCD. He builds WhatsApp Business API products and writes practical, no-hype guides about what actually ships.
Continue lendo
7 Best WhatsApp Marketing Tools in 2026 (Honest Comparison)
Every list like this is written by one of the tools on it — including this one. So here's the honest version: what actually matters, and who each tool fits.
WhatsApp Template Rejected? Every Reason Meta Sends, Explained
Meta rejects a template and hands you a single word: INCORRECT_CATEGORY, INVALID_FORMAT, SCAM. Here is what all eight of those words mean, why three of them are indistinguishable in Meta's own docs, and which one does not mean rejected at all.
Twilio WhatsApp Pricing: What It Costs, and What You Still Have to Build
Twilio bills $0.005 per WhatsApp message in both directions, while Meta charges nothing for inbound. Here is what that costs at real volumes, and when Twilio is still the right answer.
