Migrating off Wati takes under a week and zero message downtime if sequenced right. Your WhatsApp number, display name, quality rating, and verified badge belong to your WABA — they move with you via Meta's embedded signup. Templates must be re-created and re-approved on the new platform (submit them before cutover; approval usually lands within a day). Chat history and contact data export from Wati; flows must be rebuilt. The only irreversible step — re-registering the number — takes minutes.
The fear of migration keeps more businesses overpaying on WhatsApp platforms than any contract does. In reality Meta designed the WABA model so businesses own their assets, not platforms. Here is the playbook we run for founding members coming from Wati, generalised so it works for any destination platform.
What moves with you, and what doesn't?
Get this straight first, because it determines the whole plan.
Moves automatically with the WABA: your phone number, display name, business verification status, verified badge, and messaging limits/quality history.
Must be re-created: message templates (re-submit on the new platform; Meta re-approves, typically within hours to a day).
Must be exported and re-imported: contacts, opt-in records, tags/attributes.
Must be rebuilt: chatbots and flows (platform-specific by nature — also your chance to fix what never worked).
Usually cannot move: full chat history. Export what Wati allows for records; conversations restart on the new platform.
The 7-day cutover plan.
Day 1 — inventory. Export contacts (CSV), list every active template with its exact body and category, screenshot every flow, note every integration (Shopify, webhooks, Zapier) and where it points.
Days 2–3 — build in parallel. Set up the new workspace, import contacts with opt-in status, re-submit all templates for approval, rebuild the 2–3 flows that carry 80% of your traffic. Wati keeps running untouched — this is the trick that makes downtime zero.
Day 4 — dry run. Test flows against a test number on the new platform, verify integrations fire, confirm every template is approved.
Day 5 — cutover. Re-register the number to the new platform via Meta's embedded signup (minutes). Inbound messages now land on the new platform. Update webhook URLs in any external systems.
Days 6–7 — watch and settle. Monitor delivery and quality rating, keep Wati read-only until the billing period ends, then cancel.
What are the traps that actually cause downtime?
Cutting over before templates are approved — your transactional messages (order updates, OTPs) stop until approval lands. Always submit templates days before switching.
Forgetting opt-in records. Export proof of consent with your contacts; it is both Meta policy and DPDP Act hygiene.
Broadcasting on day one from the new platform. Warm up: normal transactional traffic for a few days, then campaigns. A volume spike right after re-registration is the classic quality-rating dip.
Leaving old webhook URLs in Shopify/CRM pointed at Wati — orders silently stop triggering messages.
Timing the cutover mid-campaign. Pick your quietest day; hotels pick mid-week, D2C avoids sale periods.
Will you lose your green tick or quality rating?
No. Business verification and the verified badge attach to your Meta Business Manager and WABA, not to Wati. Quality rating and messaging limits likewise travel with the number and WABA history. What can hurt the rating is behaviour after migration — hence the warm-up rule above. If your number is currently rate-limited or flagged, resolve that before migrating; a platform switch does not reset Meta's view of the number.
What does migration cost?
Meta charges nothing to move a WABA between providers. Your costs are the overlap month (running both platforms briefly), the rebuild time for flows, and any annual commitment you are exiting.
If Waaru is your destination: founding members get the entire playbook above executed for them in the 48-hour white-glove setup — templates re-submitted, contacts imported, first flows rebuilt — and the platform is free during early access, so the overlap month costs nothing extra.
FAQ
Questions worth answering.
Yes. The number belongs to your WABA in Meta Business Manager, not to Wati. Re-registering it with a new provider through embedded signup takes minutes, and inbound messages switch over immediately.
Research notes
Evidence checked for this article.
WABA assets (number, display name, verification, messaging limits) are managed in Meta Business Manager and move between solution providers via embedded signup; templates are submitted and approved per platform.
Meta — WhatsApp Business Platform documentation · Accessed 4 July 2026
