Switch WhatsApp API Providers Without Losing Green Tick
In this article
Switching WhatsApp Business API providers sounds risky, and that fear keeps a lot of businesses stuck with a BSP they've outgrown. The good news is that Meta has a defined process for moving a WhatsApp Business Account (WABA) between providers that preserves your number, your official verification status, and your approved message templates. This post walks through exactly how that migration works in 2026, what can go wrong, and how to plan it so your customer conversations never stop.
What Actually Transfers and What Doesn't
When you migrate a WABA between BSPs, Meta carries over your phone number, display name, official business account status (including the green tick if you have one), quality rating, current messaging tier, and every high-quality approved template, up to the 250-template WABA limit. What doesn't move automatically is your chat history, saved customer contact lists, low-quality or pending templates, and any chatbot flows or automation logic you built with the old provider. Those need to be exported and rebuilt on the new platform. Be precise about this split before committing to a timeline: the Meta-side transfer is the fast part, and rebuilding automations, inboxes, and integrations is where the real project effort sits.
The Migration Checklist
| Question | Why it matters |
|---|---|
| Are the source and destination WABAs under the same Business Manager? | Meta requires the source and destination Facebook Business Manager IDs to match before it will approve the transfer. |
| Has 2FA (two-step verification) been disabled on the source number? | Meta rejects the migration with a permission error if two-factor authentication is still active on the source WABA, even if the old BSP's dashboard shows it as off. |
| Do you still have access to the registered phone number? | You'll need to receive a 6-digit OTP via SMS or voice call during the migration, so the number must be reachable. |
| Have you exported templates, contacts, and chat history? | Access to the old BSP's dashboard typically ends within 24 hours of migration completing, so export before you start. |
| Have you cleaned up unused or low-quality templates? | Templates with no sends in the last 90 days often carry a poor quality score, and trimming them improves what transfers cleanly. |
| Does your BSP contract have a notice period or exit fee? | Meta allows transfers anytime, but your commercial contract with the old BSP is separate and may have its own terms. |
How to Evaluate the New BSP Before You Commit
A migration only makes sense if the destination is genuinely better, so pressure-test the new provider before you touch the live number. Ask how their pricing sits on top of Meta's per-message charges: platform fee, any per-message markup, onboarding cost, and how rates change as volume grows, in writing with GST treatment spelled out. Ask who does the migration work, because a provider that assigns a named onboarding contact for the 2FA checks, template review, and cutover is a very different experience from one that emails you a help article. Check the features you use daily: shared team inbox, agent roles, campaign scheduling, chatbot builder, CRM and webhook integrations, and reporting. Ask about support hours in Indian time and how escalations work when a campaign fails the night before a sale. Finally, since you're handling customer numbers and chat data, ask where data is stored and how the provider supports your DPDP Act 2023 obligations, including deleting customer data on request. Vague answers now won't improve after you've migrated.
How the Technical Migration Actually Works
The new BSP first adds your number to a fresh WABA slot, or vacates one if needed, then you enter your existing phone number on their platform. This triggers a warning that the number is about to move to a new WhatsApp Business Account. The destination BSP then sends a "request migration" call to Meta, which asks the source WABA owner to approve the transfer. Once approved, Meta re-associates the number with the new provider's infrastructure, usually within 1 to 10 minutes, though some businesses see a brief sending pause of 15 to 60 minutes while the handover completes.
Here's the part that surprises most businesses: until the migration is finalized, your old number keeps sending and receiving messages normally on the source BSP, so there's no dead period where customers can't reach you. Once the new WABA is active, you can start sending immediately, no re-verification, no waiting for the green tick to reappear. This is why testing your new provider's WhatsApp Business API and chatbot setup in a sandbox before triggering the live migration is worth the extra day it takes.
A Week-by-Week Cutover Plan
Treat the switch as a two to three week project rather than a single afternoon. In week one, do the audit: confirm Business Manager access and admin rights, list every template with its quality status, document chatbot flows and auto-replies, note every system connected to WhatsApp (CRM, order updates, payment reminders), and read your contract for notice terms. In week two, build on the new platform in parallel: recreate templates that won't transfer, rebuild the chatbot and routing logic, reconnect integrations against a test number, and train agents on the new inbox. Then export everything from the old dashboard, since access usually closes within a day of migration. Pick a low-traffic window for the cutover, disable 2FA, run the migration, and verify with live test messages in both directions. Keep week three as a stabilisation buffer: watch delivery rates, webhook events, and quality rating daily, and hold off on your first large bulk WhatsApp messaging campaign until routine two-way traffic has run clean for a few days.
Common Mistakes That Cause Failed Migrations
The single most common failure is forgetting to disable 2FA properly, since the old BSP's dashboard can show it as off while the underlying phone number ID still has it enabled on Meta's side, which triggers a silent permission denial. The second is not exporting data first and losing chat history or contact segmentation that took months to build. The third is treating the migration as purely technical and ignoring the commercial contract, only to get hit with an early termination clause after the switch is already done. A fourth, quieter mistake is forgetting the systems around WhatsApp: webhooks pointing at the old provider's endpoints, opt-in forms feeding the old platform, and agents still logged into the old inbox answering nothing. Plan the cutover during a lower-volume period, and re-configure your messaging and automation flows on the new platform before you send your first live campaign, so nothing breaks the day traffic picks back up.
Frequently Asked Questions
Will I lose my green tick during the migration?
No, the official business account status including the green tick transfers with the WABA as long as the source and destination Business Manager IDs match.
Does my chat quality rating reset to zero?
No, your current quality rating and messaging tier carry over to the new BSP along with the number.
How much downtime should I expect?
Typically none for receiving messages, with some sources reporting a brief 15 to 60 minute pause in sending during the actual handover window.
Who gets billed for messages sent right around the migration?
Messages sent before migration are billed by the old BSP, and messages sent after are billed by the new one, even if delivery happens later.
Do approved templates need to be resubmitted for review?
No, high-quality approved templates transfer as-is and can be used immediately without going through Meta's review process again.
Can I migrate without involving my old BSP at all?
The Meta-side technical transfer doesn't require the old BSP's cooperation, but you should still check your contract for notice periods or exit terms.
What if the OTP never arrives during migration?
The registered number must be reachable for SMS or a voice call, so recover access to that SIM or line before starting rather than mid-migration.
Do my webhooks and integrations move automatically?
No, anything pointing at the old provider's endpoints, CRM sync, order notifications, chatbot triggers, must be reconfigured against the new platform.
Can I switch back if the new provider disappoints?
Yes, the same Meta migration process works in any direction, though repeating the full rebuild effort is exactly why evaluating the new BSP thoroughly first matters.
Why India's Growing Businesses Choose LeadNXT
LeadNXT handles WABA migrations for businesses switching from other providers, including template cleanup, 2FA checks, and rebuilding chatbot flows so nothing breaks during the switch. See the full breakdown on the WhatsApp Business API page, and check the AI chatbot automation page if you're rebuilding flows on the new platform.
Try It
Book a free demo to see it in action, no credit card required.
