How to change your WhatsApp API provider without losing the number, templates or limit

Anusha Reddy runs a NEET coaching centre in Vijayawada with fourteen staff, 2,400 parents on WhatsApp, 31 approved templates and a messaging limit of 10,000 that took two years to earn. Her contract ends in December and she wants a different inbox before the January admissions rush. Her first question was whether she would lose the number. Her second was which of Meta’s pages applied to her, because Meta is halfway through changing the answer. (Anusha and her centre are invented. Everything quoted is from Meta’s pages, read on 15 October 2026.)

To change WhatsApp API provider in October 2026, find out one thing first: whether Meta has already moved your account to its new account model. (The industry calls these providers BSPs, Business Solution Providers; Meta’s pages say Solution Partner or Tech Provider.)

First, which account model is your account on?

Meta began moving every WhatsApp Business account to a new model on 23 September 2026, in stages, and says the rollout “reaches all businesses by mid-October 2026”. The check takes a minute: in Meta Business Suite open Settings, then Accounts. Two tabs, “WhatsApp Accounts” and “Messaging Accounts”, mean you have moved. One WhatsApp Accounts tab means you haven’t yet; Meta says Business Suite keeps “the previous WhatsApp Business account (WABA) experience” for a business until its turn comes.

The split: the WhatsApp account holds the phone number, profile, catalogues and, later, a username, and Meta says it “is always owned by the client”. The messaging account holds templates, billing and webhook subscriptions, keeps the old WABA’s ID, and “can be owned by the client or by a partner”. Existing IDs and tokens keep working. Our 2026 changes timeline has the dates; the glossary has the terms.

On the new model: share the number, don’t migrate it

Meta’s changelog entry of 18 August 2026 is the operative line: “phone number migration isn’t supported for accounts on the new WhatsApp account model. If the destination WhatsApp account doesn’t already own the phone number, the request is rejected, and disconnecting the number from its current account doesn’t make it available.” The migration page itself now opens with the same notice.

What replaces it is sharing. From the account model page: “a client who wants to work with you shares their existing WAAC instead. The number does not move, conversations are uninterrupted, and there is no migration to perform.” Sharing “is additive”: keeping or removing the previous provider is your decision, “and neither is a prerequisite for onboarding” the new one.

In practice Anusha goes through the new provider’s Embedded Signup with her existing number. Meta’s onboarding page says “clients already onboarded with one partner can onboard with a different partner using their existing phone number”, and the flow creates a separate messaging account for the new provider automatically.

Three things are shared rather than duplicated. Throughput stays at the number level: “when multiple partners share a phone number, they share the phone number’s throughput capacity”. The messaging limit “is shared across all partners on that number”. And incoming messages go to one place: since 23 September Meta’s Conversation Routing “controls how inbound messages are routed to partners when more than one partner shares a WhatsApp account”, with thread ownership, standby partners and a conversation summary handed over with the thread. While both providers are on the number, agree with both which one owns inbound chats.

One caveat where the current provider pays Meta on your behalf: “if you attach your credit line to a client owned Messaging account, that Messaging account cannot be shared with another partner”. The new provider gets a fresh messaging account either way, but the old one, and the templates in it, stay with the old provider.

Templates on the new model: copied, not moved

Meta’s page is plain: “Templates belong to the Messaging account in which they were created and are not shared across Messaging accounts.” You either create them again or use the Template Migration API to copy them, and “when templates are migrated to a new Messaging account, their quality ratings and messaging tier reset to baseline, requiring a ramp-up period of approximately 2 to 4 weeks”.

The template migration page adds two limits. Templates “can only be migrated between WABAs owned by the same Meta business”, and only templates with a status of APPROVED and a quality score of GREEN or UNKNOWN are eligible. The API returns a list of failures with reasons; Meta’s own examples are “Incorrect category” and “Formatting error - dangling parameter”.

So if the old provider owns your messaging account, common when its credit line pays Meta, the copy route is closed and you are re-creating templates by hand. That is survivable if the texts, sample values and button URLs are saved somewhere other than the old inbox.

On the old model: the three routes Meta documents

If your Business Suite still shows one tab, Meta’s older migration pages apply for now. All three routes need two-step verification disabled on the number, business verification on both sides, a payment method on the destination account, an approved display name with no pending change, and a real rather than a test number. Coexistence numbers, “in use with the WhatsApp Business App”, can’t be migrated this way at all.

Route	Who starts it	What happens	Meta’s own steer
Through the new provider’s Embedded Signup	You, in the signup flow, with your existing number	A new WABA is created for you; the provider shares its credit line, subscribes to webhooks and registers the number	”Simpler and is the preferred solution”
Through Meta Business Suite (Multi-Partner Solutions)	The provider tags your WABA with a migration intent; you accept under Requests, then Received	A new WABA, templates duplicated, number migrated and registered	For providers that work through a partner solution
Programmatically	The new provider, through the API	The provider creates and owns the destination WABA and you accept a “Messaging For” request	”Only recommended if you will be working with the client using the On-Behalf-Of model”

A fourth variant exists for businesses that own their WABA: unshare it from the old partner in Business Settings, then pick the existing WABA in the new provider’s Embedded Signup. Nothing migrates and the templates stay, but you are “prevented from sending messages” until the new credit line replaces the old one “on the 1st of the following month”. Meta’s advice: start near month end, at least three days before it.

What moves and what doesn’t

Item	Old-model migration	New model (sharing)
Phone number	Moves to the new WABA	Stays; shared with the new provider
Display name	Kept	Unchanged
Number’s quality rating	Kept	Unchanged
Messaging limit	Kept	Shared across the partners on the number
Official Business Account badge	Kept	Unchanged
Approved, high-quality templates	Duplicated, then re-checked for category; some may come back REJECTED	Copied with the API if the same Meta business owns both accounts; otherwise re-created
Template quality ratings	Not migrated; UNKNOWN for 24 hours, then re-rated	Reset; Meta’s ramp-up estimate is 2 to 4 weeks
Low-quality, rejected or pending templates	Not duplicated	Not eligible for copying
Chat history	Not through Meta; the Cloud API keeps messages for at most 30 days	The same; future conversations continue uninterrupted, past ones live in the old tool
Contacts, tags, notes, opt-in records	Only in the old provider’s tool	Only in the old provider’s tool

The chat history row is the one people get wrong. Meta’s data privacy page says Cloud API messages “have a maximum retention period of 30 days”. Anusha’s two years of parent conversations live in her provider’s inbox, not at Meta, and stay there when she leaves.

How long is the number dark?

On the new model, Meta’s answer is not at all: “no migration, no number provisioning, no downtime”.

On the old model it depends on the route. With Embedded Signup, “business phone number registration happens instantly, therefore you can continue to send and receive messages without interruption”, but “template duplication takes time”; Meta suggests starting template migration before registering the number. With unshare-and-reshare, sending stops until the first of the next month, and attempts in between fail with error 131042.

The two-step PIN is the gate

On the old model, Meta’s programmatic page states it without hedging: “Two-step verification must be disabled on the phone number before you can initiate migration.” If you own your WABA, you do it in WhatsApp Manager, under Account tools, Phone numbers, the number’s settings and the Two-step verification tab; a confirmation link goes to the portfolio’s email. If the provider owns the WABA, “the phone number owner must ask the source WABA owner to disable it”. It can’t be switched off through the API. Whoever controls that switch controls your exit, which is why it belongs in the contract, with a date.

On the new model the PIN is on its way out. Meta’s two-step page says it “is being deprecated for eligible Cloud API phone numbers”, with eligibility “rolling out gradually”; if the Two-step verification tab is gone, there is nothing to disable, and “partners can change the display name without knowing the PIN”. Our phone number options guide covers the PIN in full.

Billing: whose payment method, and in which currency

Old-model pages give one cut-off: “messages delivered before migration is complete are charged to the old Solution Partner”, including messages sent before and delivered after, and “messages delivered after migration is complete are charged to the business customer”. The destination account needs a payment method before it can send, and a credit line attached to a WABA “cannot be changed”, so a different credit line means a new WABA.

On the new model, “each Messaging account has its own payment method, completely independent from other Messaging accounts”. Check in Business Suite which payment method each one carries before you send.

Currency matters this year. Indian businesses billed by Meta must move every messaging account to rupees by 31 December 2026, and Meta says it stops delivering from non-INR accounts on 1 January 2027; our INR billing guide has the detail. With a provider’s credit line the provider is the “Bill To Party” and you pay the provider; with your own payment method, Meta bills you at its rate card.

What to take out of the old tool before you cancel

None of this moves through Meta; take it out of the old inbox while you still have the login.

• Contacts, with the opt-in date, source and wording for each. Our opt-in guide says what a record needs to show.
• Every template’s text, category, language, sample values and button URLs.
• Tags, segments and internal notes, in whatever form they export.
• The list of open conversations and who owns each.
• Campaign reports, for your own records.
• Every integration pointed at the old provider: website forms, the Shopify connection, any webhook endpoints.

The ten-step checklist

1. In Meta Business Suite, note whether Accounts shows one tab or two.
2. Confirm who owns the WhatsApp account and the messaging account. If the provider owns the latter, plan to re-create templates.
3. On the old model, find out who controls the two-step PIN and get a written date for switching it off.
4. Save every template’s text and sample values, and note which are APPROVED and green.
5. Export contacts and opt-in records from the old tool.
6. Pick the date. New model: any day. Unshare-and-reshare: the last week of a month, at least three days before it ends.
7. Go through the new provider’s Embedded Signup with the existing number, or its migration flow on the old model.
8. Add or confirm the payment method on the new messaging account, in rupees.
9. Send one template and one reply from the new inbox, watch the delivered and read statuses, and agree who owns inbound chats while both providers are on the number.
10. Remove the old provider only after the templates you need are approved on the new side and a week of sends has gone cleanly; keep the old login until the final invoice is settled.

Anusha’s account had two tabs. She shared the WhatsApp account with the new provider on a Tuesday, found that her old provider owned the messaging account, re-created the 31 templates from a spreadsheet she had kept, had 29 approved within a day, and sent small batches for three weeks while they earned their ratings. She removed the old provider in week four, after its last invoice. Before you sign the next contract, send our provider questions, and get question 6, what comes with you when you leave, answered in writing.