Why teams migrate from WATI (top 5 reasons)
- Pricing hits a scaling wall. WATI Growth ($59) caps at 5 agents. Adding agents 6-10 costs $50/month. AI on Pro is $99+. A 10-agent team pays ~$256/month all-in vs $146 on Go4whatsup Standard.
- AI features locked behind higher tier. WATI Growth's "chatbot" is keyword-only. Real AI needs Pro or paid add-on.
- USD-only billing. India / GCC / Europe teams pay FX + card fees on every invoice.
- Missing native Zoho / Odoo integration. WATI's strength is Shopify. If your CRM stack is Zoho or Odoo, WATI = Zapier + friction.
- Support responsiveness. Growth-tier support is ticket-based only. Complex issues take days.
The 6-step migration timeline (24-48 hours total)
Step 1 — Sign up with new BSP (5 minutes)
Create an account with your chosen new BSP (Go4whatsup, AiSensy, Interakt — whichever). Verify email. Add billing method. Don't transfer the number yet.
Step 2 — Export from WATI (1-2 hours)
This is the step most teams skip and later regret.
- Export contact list — WATI dashboard → Contacts → Export CSV
- Export chat history — WATI support ticket → request JSON/CSV export → takes 24-48 hours to receive
- Export approved templates — screenshot each Meta-approved template, note category + language
- Export webhook configurations — copy every integration setting
Once the number transfers, WATI locks the account. Get everything now.
Step 3 — Meta number transfer request (30 minutes)
Your new BSP initiates the transfer inside your Meta Business Manager. You'll receive a Business Manager notification. Approve it. Meta then migrates the number to the new BSP (24-48 hours).
Step 4 — Re-submit templates to Meta (1-24 hours)
Templates don't auto-transfer between BSPs. Re-create each approved template in the new BSP's template manager. Match the category, language, and body text exactly. Meta usually approves within 1-24 hours if the templates were approved before.
Step 5 — Reconnect integrations (30 min – 4 hours)
Reconnect your CRM, e-commerce platform, webhook endpoints. Test each integration end-to-end before switching production traffic.
Step 6 — Cutover + WATI cancellation (last step)
Once new BSP is fully live and templates approved:
- Send a test message from the new dashboard to your own number — confirm delivery
- Have a team member reply — confirm inbound routing works
- Run one small production campaign — verify delivery + analytics
- Only then cancel WATI subscription (check contract for early-termination clauses)
The 2 mistakes that cause 90% of failed migrations
Mistake 1 — Cancelling WATI before new BSP is live
Cancelling WATI immediately locks your account and voids your export access. If new BSP setup hits a snag, you've lost chat history and templates. Rule: cancel WATI ONLY after new BSP is production-verified.
Mistake 2 — Skipping template re-approval before cutover
Templates need Meta re-approval on the new BSP. Skipping this means when you try to send a campaign on new BSP the day after cutover, nothing sends because no templates are approved. Rule: submit + confirm approval of all templates 24 hours before cutover.
What you keep vs lose
Keep
- Your business phone number
- Your Meta Business Manager verification
- Your green tick (if you had one)
- Your customer contact list (if you exported)
- Your Meta quality rating (transfers with the number)
Lose (if you don't export first)
- Chat history
- Template library on old BSP
- Integration configurations
- Any custom chatbot flows built on WATI's flow builder
Cost of migration
- New BSP setup fee: ₹0 with Go4whatsup, $60-180 with AiSensy/Interakt (often waived on promo)
- Meta number transfer: Free
- Template re-submission: Free (Meta doesn't charge for approval)
- WATI early-termination: Depends on contract — check fine print for annual commitments
- Team time: ~8-12 hours across engineering + operations
Migration checklist (print + tick)
- ☐ New BSP account created + verified
- ☐ WATI contact CSV exported
- ☐ WATI chat history export requested (24-48 hr fulfilment)
- ☐ All approved templates screenshotted with category + language
- ☐ All webhook / integration configs documented
- ☐ Meta number transfer request initiated inside Business Manager
- ☐ Meta transfer approved
- ☐ Templates re-submitted on new BSP
- ☐ Templates approved by Meta
- ☐ CRM / integrations reconnected + tested
- ☐ Test message sent + received on new BSP
- ☐ Test campaign run + analytics verified
- ☐ Team trained on new dashboard
- ☐ WATI subscription cancelled (only after all above ✓)