Migrate Your WhatsApp Business API Between BSPs Without Losing WABA (2026 India Guide)

Switching your WhatsApp Business Solution Provider in India does not mean starting from zero. Your phone number, display name, green tick, quality rating, messaging tier, and approved high-quality templates all travel with you — if you run the migration correctly. Done wrong, you lose your green tick, reset your messaging limits to Tier 1, trigger a Meta Business verification re-review, and sit in silence for two to three days while customer conversations back up. This guide walks Indian D2C brands, SaaS founders, and marketing agencies through a zero-downtime migration from AiSensy, Interakt, Wati, Gupshup, MSG91, or any other BSP, with the 2026 Meta process, the GST and billing overlap math, the template preservation rules, and the four specific failure modes that kill 40% of first-attempt migrations.

What Actually Transfers When You Switch BSPs

When you migrate a WhatsApp Business Account from one BSP to another, Meta preserves the phone number, display name, official business account status, green tick verification, quality rating, current messaging tier, and every high-quality approved template (up to the 250-template WABA limit). Low-quality templates, rejected templates, pending templates, chat history, and customer phone number lists do not transfer automatically. Business verification does not need to be redone as long as the Facebook Business Manager stays the same. The phone number remains active throughout the migration window.

The Pre-Migration Checklist (Do This Before Touching Anything)

The single largest cause of failed BSP migrations is not running the pre-migration checklist. Meta's migration flow rejects the request the moment any one of these conditions is unmet, and because the error messages are cryptic ("permission denied" covers at least six distinct causes) most teams waste a day diagnosing a thirty-second fix. Run all six checks before you open a ticket with either BSP.

1. Disable two-factor verification on the WABA. Meta requires 2FA to be OFF for the WABA throughout the migration window. Log in to your source BSP dashboard, find the phone number settings, and disable the 6-digit PIN. You can re-enable it on the destination BSP after migration.
2. Confirm the source WABA is approved and active. A pending, rejected, or restricted WABA cannot be migrated. Check status in Facebook Business Manager → Accounts → WhatsApp Accounts.
3. Verify the Facebook Business Manager ID. You will need this (15–16 digit number) on the destination BSP. Get it from business.facebook.com → Settings → Business Info.
4. Note your current messaging tier. If you are on Tier 3 or 4, flag it to your destination BSP so they can confirm infrastructure readiness. Brand-new BSP relationships sometimes cap you at Tier 1 for the first week regardless of historical tier — ask in writing whether your tier carries over immediately.
5. Export templates, flows, contacts, and chat history from the source BSP. Templates re-approve automatically but chat logs and contact attributes do not transfer. Every BSP has a different export format; do this before you click migrate because access to source systems typically ends 24 hours after migration.
6. Settle outstanding invoices with the source BSP. Some BSPs block the migration authorization if there are unpaid balances. Check your billing tab before you schedule migration day.

The Migration Process: Step by Step

Every BSP exposes the Meta migration flow slightly differently in their dashboard, but the underlying Meta API calls are identical. The destination BSP triggers a "request migration" call to Meta, which in turn asks the source WABA owner (you, via the Facebook Business Manager) to approve the transfer. Once approved, Meta re-associates the phone number with the destination BSP's infrastructure within 1–10 minutes. The phone number continues to send and receive during the entire window.

Migration sequence:

1. Destination BSP creates a new account for your business
   → you supply Business Manager ID + phone number

2. Destination BSP calls Meta's Migrate API
   → POST /{phone_number_id}/register with pin disabled
   → Meta validates source WABA status

3. Meta emails the admin of the Facebook Business Manager
   → subject: "Approve WhatsApp Business Account migration request"
   → click link, confirm destination BSP identity

4. Meta re-associates phone number with destination infrastructure
   → phone_number_id gets a new webhook endpoint
   → templates copy over to the destination account

5. Destination BSP surfaces the migrated number in their dashboard
   → set new 2FA PIN
   → reconfigure webhook URL in your backend if applicable
   → resume sending

Typical window: 3–15 minutes from step 2 to step 5.
Risk window: zero-message gap only between steps 3 and 4 (~90 seconds).

Cost Overlap: What You Pay During Migration

Migrations that span two BSPs for a few days create a billing overlap that most teams do not budget for. Between the moment you sign up with the destination BSP and the moment you cancel the source BSP, you pay platform fees to both. Meta's per-message conversation charges do not double — they route to whichever BSP currently holds the number — but the SaaS subscription or minimum commitment on each side is separately payable.

If you are on a usage-only BSP with no subscription floor (rare in India — most Indian BSPs lock you into ₹2,500+ per month as a platform fee), the overlap approaches zero. Always confirm the cancellation policy with the source BSP before you sign with the destination.

Template Preservation: The 250 Limit and the Quality Trap

Meta carries over only high-quality approved templates on migration, and only up to 250 per WABA. If your source account has 400 approved templates — common for D2C brands running seasonal campaigns — the 150 lowest-quality ones are dropped. You cannot pick which 250 survive; Meta uses an internal quality score. Audit your templates before migration, archive or delete unused ones, and promote the ones you actually send by running a fresh send cycle on each to boost their quality score the week before migration.

The Four Failure Modes That Kill 40% of First-Attempt Migrations

Failure 1: Two-Factor PIN Still Active on Source

Meta rejects the migration call with a "permission denied" error if 2FA is active on the source WABA. The source BSP dashboard may show 2FA as disabled but the underlying phone_number_id still has it set. Log the raw Meta API response; if you see error code 100 with subcode 33, the PIN is still set. Fix: call the source BSP support, request them to disable via API directly, not via dashboard toggle.

Failure 2: Business Manager Mismatch

The destination BSP's Meta app must be granted access to your Business Manager before migration. Many teams skip this step because it is not in the destination BSP's onboarding checklist. Go to Business Manager → Settings → Business Integrations → Add → search for the destination BSP's app name → grant WhatsApp Business Account permissions. Skipping this step returns "app not authorized" and blocks migration.

Failure 3: Templates Over the 250 Limit

If your source WABA has more than 250 approved templates, Meta drops templates silently during migration. The destination BSP dashboard will not alert you that templates are missing. Audit post-migration by comparing template counts in both dashboards. Rebuild anything that was dropped; they will need to re-enter the Meta review queue (24–48 hours).

Failure 4: Webhook URL Not Updated in Your Backend

Meta re-associates the phone number to the destination BSP's webhook endpoint. If your internal systems (CRM, order management, support dashboard) still hit the source BSP's webhook forwarder, inbound messages silently drop. Update every integration point to the destination BSP's webhook URL during the 10-minute migration window. If you run your own ingestion layer (like RichAutomate's tenant-scoped webhook endpoint in WebhookController), the change is a one-line environment variable flip.

Migration Cost Comparison: Staying vs Switching (Indian D2C at 100K Marketing Msgs/Month)

When You Should NOT Switch BSPs

• Active Red quality rating. Migrating while your number is Red resets some internal Meta signals but not all. Wait until you recover to Yellow or Green, then migrate. Otherwise you move a penalized number onto new infrastructure with the penalty intact.
• Pending Meta Business verification. If your Business Manager is still under Meta review, do not migrate. Wait until verification completes.
• Active template dispute. If Meta has flagged a template pending review, let the review close before migrating.
• Peak seasonal campaign (Diwali, Black Friday, New Year). Never migrate during a launch window. The 90-second zero-message gap is low-risk on a Tuesday afternoon; on Diwali Day 1 at 6 PM it is a revenue disaster.
• Legacy BSP with proprietary flow logic you cannot export. If your chatbot logic is locked inside a BSP's visual builder with no export format, budget extra engineering weeks for rebuild before you commit.

The GST Angle: Indian Invoice Reconciliation

Two BSP invoices in the same tax quarter means two separate GST filings if the BSPs are registered in different states. Coordinate with your CA: file the source BSP's final invoice before the migration closes (so input credit is not lost), confirm the destination BSP issues an invoice against the same GSTIN you registered originally, and log the migration date in your books so audit trails are clean. Indian D2C brands registered under GST composition scheme face an additional rule: BSP invoices over ₹20,000 in a month require an e-invoice from the BSP; confirm this before switching to a BSP that does not generate e-invoices.

RichAutomate's Migration Path

RichAutomate positions as a destination BSP for brands moving off AiSensy, Interakt, Wati, Gupshup, MSG91, and other India-focused BSPs. The platform supports both billing models so you can choose Client Pay (₹0.10/msg platform fee, you hold the Meta credit card) or SaaS Pay (₹1.20/Marketing inclusive, no Meta card required). Templates move over via Meta's native migration process, contacts import via CSV, and chatbot flows are rebuilt in RichAutomate's visual flow builder (dual-engine: custom chatbot flows plus Meta Native Flows out of the box). Typical migration timeline end-to-end is 2 business days including audit, pre-migration checklist, Meta handshake, webhook reconfiguration, and first live campaign.

Decision Checklist Before You Migrate

1. Is your current BSP costing more than 15% of your monthly Meta conversation spend? → Switch.
2. Is your current BSP capping features you need (Flow builder, team inbox, custom webhooks, white-label)? → Switch.
3. Have you been locked into a yearly contract with no exit clause? → Wait until 60 days before renewal, then start the migration timeline.
4. Is your quality rating Red or in dispute? → Recover first, migrate after.
5. Are you in a launch window? → Delay migration to the post-launch lull.
6. Can you export your current flows, templates, and contacts? → If no, the switch is harder than it looks. Budget rebuild time.