How to migrate from Wati to another WhatsApp platform

Tanay PatelAI and full-stack engineer4 July 2026Updated 14 September 2026

The short answer

Plan the move by checking account ownership, number eligibility, exports, templates, and workflows. Confirm what is available in the destination account before switching traffic. Migration timing depends on the account and connection path; do not assume a one-week schedule or uninterrupted delivery.

Before leaving Wati, check which assets your business owns, what you can export, and which workflows need rebuilding. Use this guide to plan the move with your destination platform.

Jump to a section

What moves with you, and what doesn't?

Make an inventory and confirm the treatment of each item with the destination provider.

Number and account: confirm ownership, migration eligibility, display name, badge status, quality, and messaging limits for the exact connection path.
Templates: record each name, language, body, and category. Check which templates are present and approved in the destination account, and resolve missing or rejected ones before sending.
Contacts: check export and import support for contacts, opt-in records, tags, and custom attributes.
Chatbots and flows: document each step and rebuild the journeys the destination platform cannot import.
Chat history: export the records Wati makes available and confirm what the destination platform can import. Keep an accessible archive for your team.

Plan the cutover in stages.

Inventory the current setup. Export available contacts and consent records, list active templates, capture each flow, and note where integrations such as Shopify, webhooks, or Zapier send their events.

Prepare the destination workspace. Import supported data and rebuild the workflows your team relies on. Check template availability and approval. Keep the current service running while preparing the replacement where the connection path permits it.

Run a controlled test. Verify the relevant replies, integrations, templates, and human handoffs with a test number before moving customer traffic.

Confirm the cutover path with your destination provider. In Waaru, use the existing API connection only when Meta lets you authorize that account and select the number. If it does not, preserve the current connection and ask Meta or your provider for the supported next step. Waaru does not offer a separate provider-migration option.

After cutover, test inbound delivery and eligible outbound replies. Check integrations, quality, and failed sends. Cancel the previous service only after verifying the new setup, preserving required records, and reviewing the contract.

What are the traps that actually cause downtime?

Missing templates: check the destination account before cutover. Do not schedule order updates or authentication messages until their required templates are available and approved.
Missing consent records: preserve the source, purpose, timestamp, and available evidence with the contact export.
Starting campaigns before testing: first verify delivery, opt-outs, quality checks, and replies on the destination platform.
Outdated integrations: verify where Shopify, CRM, and other business events go after cutover. Update and test each connection that needs to change.
Poor timing: choose a quieter period for your business and make sure the people responsible for checking delivery are available.

Will you lose your green tick or quality rating?

Record the number's current badge, quality, and limits, then ask the destination provider to confirm how the selected move handles them. Resolve existing restrictions before scheduling the move. Do not assume a platform change removes a restriction or preserves every account attribute.

What does migration cost?

Budget for any provider overlap, remaining contract commitments, data exports, and rebuilding workflows. Confirm migration eligibility and account ownership before scheduling a cutover. Waaru’s platform is free. Public signup is open. AI features are paid separately, and Meta messaging charges remain separate. Agree the onboarding scope and timing with the team before relying on a migration deadline.

FAQ

Frequently asked questions.

Can I keep my WhatsApp number when leaving Wati?

Check ownership and eligibility for the exact number with your destination provider. Preserve the existing connection until the supported move is confirmed.

Do my approved templates transfer from Wati?

Check the destination account rather than assuming that every template transfers or must be recreated. Resolve missing templates and confirm approval before sending.

Will customers notice the migration?

Do not promise an invisible switch. Test the displayed identity, incoming messages, replies, and customer journeys after the move, and prepare your team to handle interruptions.

How long does a Wati migration actually take?

Estimate the work after reviewing eligibility, data exports, workflow rebuilds, template status, and integration testing. Agree the cutover window with both providers; there is no universal completion time.

Can I migrate mid-way through a Wati annual plan?

Check the technical move separately from your contract. Ask Wati about cancellation, refunds, exports, and remaining commitments before choosing a cutover date.

Research notes

Evidence checked for this article.

Waaru's guide explains supported connection paths and what to do when an existing provider account or number is unavailable.
Waaru, connect your WhatsApp number · Accessed 14 September 2026
Business-initiated conversations require approved templates, and Meta can review or change template status.
WhatsApp Business Messaging Policy · Accessed 14 September 2026

About the author

Tanay Patel

AI and full-stack engineer

Tanay builds production AI systems, agent workflows, and the full-stack software around them. His work focuses on reliable state, recovery, and human handoff.

Read Tanay's engineering notes

Keep reading.

Put this into practice on your own number.

The platform is free. AI features are paid separately.

Create free workspace Explore WhatsApp Business API