BSP Migration Cost Calculator — See What You Save Leaving Wati / AiSensy / Interakt in 2026
Updated as of June 2026 · June 2026 Meta India rates · Free, no signup
Migrating a WhatsApp Business number between BSPs in India typically costs ₹12,000–₹40,000 one-time for a 25-template, 5-seat SMB. You keep your number, display name and green tick. Breakeven usually lands at 2–4 months for volumes above 30k messages a month, driven mostly by platform-fee savings, not per-message rates.
BSP migration cost calculator
As of June 2026. Meta India FY26 rates: marketing ₹0.8631, utility & auth ₹0.115 per conversation. Vendor markups sourced from public pricing pages.
Migration pays for itself in this many months. Anything under 6 months is a clear-cut switch decision for Indian SMBs.
Net Year-1 savings of ₹1,54,187 after deducting migration effort and lock-in buyout.
Why a migration calculator beats a vendor pricing page
Every BSP pricing page in India shows per-message rates. Almost none show the four numbers that decide whether switching pays off: 12-month TCO including platform fees, one-time migration effort, lock-in buyout and the breakeven month. The reason is straightforward — those four numbers favour the buyer, not the incumbent. This calculator forces the math out into the open. Plug your own volumes and lock-in clause from your latest MSA, and the output will hold up under a CFO review.
The underlying Meta India conversation rates are public: Meta WhatsApp Pricing developer documentation confirms the FY26 marketing rate of ₹0.8631 per conversation and ₹0.115 for utility and authentication. Vendor markups in this calculator are pulled from each provider's public Indian pricing pages as of June 2026.
How long does a BSP migration actually take?
For a typical Indian SMB with 25 templates and 5 seats, end-to-end migration takes 5–10 working days:
- Day 1–2: kickoff — export contacts, template bodies and existing chatbot flow JSON from current BSP
- Day 2–4: re-submit all templates on the new BSP (Meta auto-review is usually under 24 hours per template, often under a minute)
- Day 4–6: wire webhooks, re-integrate CRM, rebuild chatbot flows on the new platform
- Day 6–7: staging dry-run with two test numbers, verify status callbacks and template variable substitution
- Day 8: production cutover during a low-volume window (Tuesday 09:00–11:00 IST is the lowest-traffic slot for most B2C profiles)
The cutover itself takes about 30 minutes of downtime spread across two OTP-reset windows. Inbound webhooks resume immediately once the number registers under the new BSP's WABA. Use the template approval checker before re-submitting to flag any wording Meta is currently rejecting.
Hidden costs the vendor pricing pages do not list
Three line items consistently surprise buyers during a migration audit:
- Platform fee compounding. A ₹4,799/month platform fee is ₹57,588 a year — usually 30–60% of the entire bill for a 50k-message profile, and 100% pure margin to the BSP. Zero-platform-fee BSPs eliminate this line entirely.
- Per-message markup on Meta's rate. Most BSPs add ₹0.05–₹0.15 per message on top of Meta's wholesale rate. On a 50k-message account, that is another ₹30,000–₹90,000 a year on top of platform fees.
- Seat licensing. Wati, AiSensy and Interakt all gate inbox seats. Adding a 6th or 11th support agent often jumps you into a higher tier costing ₹1,000–₹3,000/month per seat. RichAutomate has unlimited seats on all plans.
Compare line items in detail on the Wati vs AiSensy vs Interakt vs RichAutomate breakdown.
Migration checklist (print this before cutover)
- Read your current BSP's MSA — locate the termination clause and the lock-in months remaining
- Export all approved template bodies (text + variables) into a spreadsheet
- Export contact list with opt-in timestamps (mandatory under the DPDP Act 2023 — do not lose consent records)
- Snapshot current quality rating and tier limit (Meta carries this across BSPs but verify post-cutover)
- Disable all marketing campaigns 24 hours before cutover
- Notify support team of the 30-minute cutover window
- Pre-create the new WABA on Meta Business Manager under your business account — do not let the new BSP create a fresh business
- Two-Step Verification PIN: keep a copy in a password manager (you will be asked to re-enter on the new BSP)
- Test inbound webhook delivery for at least 1 hour post-cutover before resuming marketing sends
On DPDP compliance specifically — opt-in records and the right to erasure must be preserved across the migration. The MeitY DPDP framework page and our DPDP WhatsApp marketing checklist cover what to retain.
When migration does NOT make sense
Three profiles where staying put is the right call:
- You send under 5,000 messages/month. Platform-fee delta is small, the re-submission cost dominates, breakeven slides past 12 months.
- You have a proprietary BSP-specific feature. If you rely on a custom chatbot builder or CRM integration that has no equivalent on the target BSP, factor in rebuild cost — usually ₹50,000–₹2,00,000.
- You signed an annual plan less than 60 days ago. Lock-in buyout will exceed Year-1 savings. Wait it out, then switch.
Frequently asked questions
How much does it cost to switch WhatsApp BSP in India?
Switching a WhatsApp Business API number between BSPs in India typically costs ₹12,000–₹40,000 one-time for an SMB profile (25 templates, 5 seats). That covers 1–2 engineering days to re-wire webhooks, 4–6 days of waiting for Meta to re-approve templates and a 2-day low-volume cutover. There is no Meta fee for the migration itself — Meta supports BSP-to-BSP number portability and the WhatsApp Business Account (WABA) retains its display name, green tick and quality rating. The bigger variable is your current BSP’s lock-in clause, which our calculator estimates as a buyout penalty on top.
Can I keep my WhatsApp Business number when I migrate to another BSP?
Yes. Meta’s BSP-to-BSP migration flow lets you keep the same phone number, the same display name and the same green-tick verification. You move the number out of the old BSP’s WABA and re-register it inside the new BSP’s WABA via Embedded Signup. Two short outages (5–10 minutes each) occur during the OTP/two-step verification reset. Schedule the cutover during a low-volume window — Tuesday morning is the lowest-traffic slot for most Indian B2C profiles.
Will my approved templates re-approve on the new BSP?
Templates do not auto-transfer between BSPs because they are tied to the WABA + BSP pair. You must re-submit each template on the new BSP. Approval is usually 60 seconds to 24 hours for utility/auth, up to 48 hours for marketing, since Meta’s review is automated and the template body has not changed. If your current copy is already compliant, expect 95%+ to re-approve on first submission. Plan for ~12 minutes of operator time per template plus the Meta review queue.
What lock-in or contract penalty will Wati / AiSensy / Interakt charge?
As of June 2026, Wati and Interakt annual plans typically include a clause that bills out the unused months at the discounted rate (no further discount). AiSensy monthly plans have no lock-in; annual plans bill remaining months. Gupshup’s enterprise contracts vary — read your MSA. MSG91 is mostly pay-as-you-go and rarely has a penalty. Our calculator estimates the buyout at roughly 50% of (platform fee × months remaining) — request the exact figure in writing before cancelling.
How many months until BSP migration breaks even?
For an Indian SMB sending ~50,000 messages per month split 30k marketing / 15k utility / 5k auth, switching from Wati or AiSensy to a zero-platform-fee BSP like RichAutomate breaks even in 2–4 months. Volumes above 100k/month break even inside the first month because the platform-fee delta dominates. Volumes below 5k/month often do not break even within 12 months — stay on a no-fee tier and revisit when volume grows.
Is there a downside or risk to migrating BSPs?
Three real risks: (1) two short OTP-reset outages during cutover, (2) the 24-hour customer service window resets, so any in-flight free service messages need to be re-opened by the user, (3) any BSP-specific features (custom chatbot flows, no-code automations, native CRM sync) need to be rebuilt on the new platform. The Meta-level assets — WABA, display name, green tick, message history at Meta — are unaffected. Always export contact lists and template bodies before initiating cutover.
Ready to see your exact savings?
Get a personalised side-by-side line-item comparison against Wati, AiSensy, Interakt or your current BSP — delivered to your inbox, no signup required.
Related reading
- 4-way comparison: Wati vs AiSensy vs Interakt vs RichAutomate →
- Wati vs RichAutomate detailed breakdown →
- AiSensy vs RichAutomate detailed breakdown →
- Wati vs AiSensy — which is actually cheaper in India 2026? →
- Meta WhatsApp rate hike January 2026 — INR impact calculator →
- State of WhatsApp BSPs in India — Q2 2026 research →
- WhatsApp Business API cost calculator →
- Template approval checker →
Sources: Meta WhatsApp Pricing developer documentation, vendor public India pricing pages (Wati, AiSensy, Interakt, Gupshup, MSG91) as of June 2026, MeitY DPDP Act 2023 framework. Vendor markups are estimates based on published list prices — your negotiated contract may differ. This calculator is informational and not a quote.