Switch WhatsApp API Provider Without Losing Your Number

Most teams stay with a WhatsApp provider they've outgrown for one reason: moving felt risky. The number had to be migrated between accounts, templates rebuilt, and every integration repointed, with a nervous window where customers' messages might go nowhere. If you want to switch WhatsApp API provider in late 2026, that picture has changed more than most guides admit.

Meta's new account model, rolled out from September 23 and reaching all businesses by mid-October 2026, removed number migration between partners entirely. You now share your number with the new partner and remove the old one when you're ready. This guide covers what changed, a pre-switch inventory, a step-by-step cutover, and the contract and template traps that still catch people. Meta details are from its account model documentation as of October 2026.

What changed in 2026

Your number no longer moves when you change provider. Meta split the old WhatsApp Business Account into two:

• A WhatsApp account, holding one business phone number, its profile and catalog. Your business always owns it, and you can share it with up to five Solution Partners.
• A Messaging account, holding templates, the payment method and webhook subscriptions. Each partner you work with gets its own, and existing WABA IDs now identify Messaging accounts.

Meta's partner docs now say plainly that migrating a phone number from one Solution Partner to another isn't supported in the new model. Instead, the new partner gets access when you share the WhatsApp account, and Meta says sharing is additive: conversations aren't interrupted, there's nothing to migrate, and removing the old partner is a separate decision you make later. Customers keep seeing the same contact, with the same chat thread on their phone.

If Meta Business Suite still shows you a single list of WhatsApp accounts rather than separate WhatsApp Accounts and Messaging Accounts tabs, ask Meta support or your new partner which process applies before you start.

Before you switch: the inventory

Spend an hour on this before signing anything. Each line has caught someone out.

1. Who owns what. In Meta Business Suite, under Settings and Accounts, check who owns your WhatsApp account and your Messaging account. If the old provider owns the Messaging account, your templates live in their asset, not yours.
2. Credit lines. If a Solution Partner's credit line is attached to a Messaging account you own, Meta says that Messaging account can't be shared with another partner. Plan for a new Messaging account with the new provider.
3. Templates. Export the name, category, language, body and buttons of every approved template, plus its quality rating.
4. Chat history. Meta's API doesn't give you old conversations back. Whatever lives in the old provider's inbox stays there unless you export it.
5. Integrations. List every webhook consumer, CRM sync, chatbot and Zapier or Make scenario that reads from the old provider.
6. Opt-in records. Make sure proof of opt-in is in your own systems, not only in the provider's database.
7. The number itself. If the phone number is rented from the provider, ask in writing how you keep it after you leave.
8. Billing currency. Meta says a Messaging account's currency can't be changed once selected, so choose it deliberately when the new partner sets one up.

Step-by-step cutover

The safe order is overlap first, then removal. Expect a few days of both providers having access.

1. Onboard with the new partner using your existing number. Most partners do this through their Embedded Signup flow, which Meta now lets clients complete with a number already onboarded elsewhere. Alternatively, share the WhatsApp account and a Messaging account with the partner's business portfolio ID in Meta Business Suite, using Assign partner. Messaging only works once the partner has both.
2. Rebuild or copy templates. Templates belong to the Messaging account they were created in. If both Messaging accounts are owned by your business, Meta's Template Migration API copies approved templates with green or unknown quality. Otherwise, resubmit them, and expect category rechecks.
3. Attach a payment method. Each partner is billed through its own Messaging account, so the new one needs a card or the partner's credit line before it can send paid messages.
4. Repoint integrations. Switch webhook consumers and CRM syncs to the new provider's events. Delivery receipts go back to whichever app sent the message, so during the overlap each provider sees statuses only for its own sends.
5. Decide who answers. Meta's new-model docs don't spell out inbound routing when several partners share a number; under its earlier multi-solution beta, every partner on a number received every inbound webhook. Assume both providers may see incoming messages during the overlap, and switch auto-replies off on one side.
6. Watch a full day of traffic on the new provider, including a template send, an inbound reply and a failed delivery.
7. Remove the old partner. Meta's offboarding steps unshare the Messaging account first, then the WhatsApp account. Do it promptly: Meta notes that any partner with access can deregister a phone number.

Copying templates looks like this, with the current Graph API version from Meta's changelog in place of v23.0:

curl -X POST "https://graph.facebook.com/v23.0/DESTINATION_MESSAGING_ACCOUNT_ID/migrate_message_templates" \
  -H "Authorization: Bearer $WHATSAPP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"source_waba_id": "SOURCE_MESSAGING_ACCOUNT_ID", "page_number": 0}'

The response lists migrated_templates and a failed_templates map with a reason for each, such as an incorrect category. To confirm the new Messaging account can pay for messages, query it:

curl "https://graph.facebook.com/v23.0/MESSAGING_ACCOUNT_ID?fields=primary_funding_id" \
  -H "Authorization: Bearer $WHATSAPP_TOKEN"

If primary_funding_id is missing, no payment method is attached and paid messages won't send.

Templates, quality and limits after the move

Some things reset, some don't, and it pays to know which before launch week.

Because template quality resets, don't schedule your biggest campaign for the week you switch. Run normal utility traffic first. Some providers also ask for a fresh account of their own: Twilio's Self Sign-up guide, for instance, says not to select a WhatsApp Business account created outside Twilio, so expect to rebuild templates in that case. For template rules in general, see our WhatsApp message templates guide.

Contract traps to check

The technical side got easier in 2026. Contracts didn't. Before you give notice, read for:

• Notice periods and auto-renewal. Annual plans often renew automatically unless you cancel by a notice date; find it and put it in a calendar.
• Minimum commitments on message volume or spend that apply even if you leave early.
• Prepaid message credits. Ask whether unused credit is refunded, transferred or lost.
• Credit line balances. Messages delivered on the old partner's credit line are billed by that partner, so settle the final invoice before you remove access.
• Data export. Confirm you can export conversations, contacts and opt-in records in a usable format, and whether that costs extra.
• Number rental. If the provider supplied the number, confirm porting or transfer terms in writing.

Our Cloud API vs BSP guide explains which of these risks disappear if you go direct, and the best WhatsApp API providers roundup compares fee models if you're still choosing where to go.

Where Tenashi fits

Some teams switch providers because the official API never fit how they work: they wanted their whole team in one inbox, groups included, without metering every reply. Tenashi does that on a WhatsApp or WhatsApp Business app number, linked by QR scan, with DMs and groups, a CRM under every chat, and an API, flat from $18/mo with no per-message fees.

It isn't a drop-in replacement for an API provider. Tenashi isn't Meta's platform, it can't link a number that's registered only on the Cloud API, and it has no templates, buttons or verified badge. Many teams keep their API number for notifications and codes and run conversations on a separate app number in Tenashi. Pacing and warm-up reduce ban risk on the linked number; they can't stop WhatsApp acting on spam.

See every feature · Get started

FAQ

Will I lose my WhatsApp number if I change provider?

Not under Meta's new account model. Your business owns the WhatsApp account that holds the number, and you share it with the new partner rather than migrating it. If the number itself is rented from your old provider, though, confirm in writing that you can keep or port it before you cancel.

Is there downtime when switching WhatsApp API provider?

There shouldn't be. Meta says sharing your WhatsApp account with a new partner is additive, so conversations continue while both providers have access. The risky moments are integration cutover and template readiness, so test template sends, inbound replies and webhooks on the new provider before removing the old one.

Do my templates move to the new provider?

Not automatically. Templates belong to the Messaging account they were created in, and each partner has its own. Meta's Template Migration API copies approved templates only between Messaging accounts owned by the same business; otherwise you resubmit them. Either way, template quality resets and takes a few weeks to rebuild.

Can I use two WhatsApp API providers on the same number?

Yes. Under the new account model you can share one WhatsApp account with up to five Solution Partners, each with its own Messaging account, templates and billing. Throughput and messaging limits are shared across them, so agree who sends what, and who replies to inbound messages, before both go live.

What happens to my chat history when I switch?

The thread on each customer's phone is untouched, since the number and its conversations stay where they are. What doesn't carry over is the history stored in your old provider's inbox or database. Cloud API offers no way to fetch past conversations, so export everything you need before you remove access.

---

Switching is now mostly paperwork and planning, not plumbing. Read the complete guide to the WhatsApp API for the platform basics, and if what you really want is one team inbox for chats and groups, get started with Tenashi.