How to Switch from WATI to Go4whatsup — The 2026 Migration Guide

1. Why teams are switching from WATI in 2026

No one migrates a WhatsApp BSP for fun. A switch means retraining agents, coordinating IT, and explaining the change to every team that touches WhatsApp. The teams who do it in 2026 almost always give one of four reasons — worth being honest about which of these you're actually solving for before you start:

Pricing pressure

WATI's per-seat pricing starts reasonable but scales steeply. A 10-agent support team that was paying $39/month two years ago now pays closer to $799/month on their Business plan — before the Meta conversation fee. Teams running broadcasts at volume also discover that WATI's included conversation caps are tight for the price tier, pushing them into a higher plan or per-conversation overages. Go4whatsup's AED/INR pricing is flat per month, includes unmetered seats on Premium and above, and passes through Meta's conversation fee with no markup — so monthly bills are predictable and typically 40–60% lower for similar volumes.

AI catching up on the competition, not on WATI

In 2025 WATI added a chatbot builder with intent detection. In the same window, AI-first platforms shipped genuine GPT-grade auto-reply, drafted-reply suggestions inside the agent console, campaign copy generators, and language detection baked into the inbox. Teams with multilingual customer bases (Hindi / Marathi / Tamil / Arabic) in particular hit a ceiling on WATI's bot logic that the AI-native platforms simply don't have. See our AI WhatsApp Platform guide for the capability checklist.

Integration gaps with Indian and regional stacks

WATI's native integrations lean toward the global SaaS stack — HubSpot, Salesforce, Shopify. Teams running on Odoo, Zoho, or Tally find themselves rebuilding everything with Zapier or webhooks, which works but makes the integration brittle. Go4whatsup ships native connectors for Odoo, Zoho CRM, Shopify, Google Sheets, and the accounting tools that Indian and GCC businesses actually use.

Support responsiveness

WATI's support model is primarily ticketed, with higher-tier SLAs gated behind enterprise plans. Teams running urgent campaigns — a flash sale, a recalled product notification, an election-day alert — report response times that don't match the business criticality. Go4whatsup's WhatsApp-first support for customers is one of the most-cited reasons buyers give for switching.

2. What actually moves and what gets rebuilt

The fastest way to de-risk a BSP migration is to separate your WhatsApp assets into three buckets on day one. Every asset falls into exactly one of these, and each bucket has a different handling instruction:

Bucket A — Moves as-is

These transfer without rebuild:

• The WhatsApp Business Account (WABA) number. Your phone number stays yours. It detaches from WATI and re-attaches to Go4whatsup via Meta's official BSP transfer flow.
• Green-tick status. If you have the Official Business Account badge on WATI, it moves with the number. Meta ties verification to the WABA, not the BSP.
• Meta Business Manager and Facebook Business Page. These sit with you directly in Meta, not with WATI. Unaffected by the migration.
• Your display name. Stays with the WABA.

Bucket B — Exports from WATI, imports into Go4whatsup

These move with a CSV / file export, re-import, and a short verification pass:

• Contacts and tags. WATI exports to CSV; Go4whatsup's import wizard preserves tag structure.
• Conversation history (last 90 days). WATI exports in CSV or JSON; Go4whatsup imports as archived threads indexed against the contact record.
• Saved replies / canned responses. Manual copy-paste or bulk CSV import.
• Template content. The template copy (headers, body, buttons) copies across. The approval does not — see bucket C.

Bucket C — Must be rebuilt on Go4whatsup

These are platform-specific and rebuilt from scratch — which sounds painful but is usually cleaner than trying to migrate them as-is:

• Message template approvals. Meta re-reviews templates per BSP. You re-submit the same copy; approval usually returns in 24–48 hours.
• Flows and automations. Every BSP's flow builder has a different logic model. Your WATI flows become the specification; Go4whatsup's flow builder rebuilds them.
• Chatbot intents. Intent definitions are platform-specific; same copy, new tool.
• Integration webhooks and connectors. Zapier zaps, Shopify apps, CRM plugins — re-installed against Go4whatsup's API or native connector.
• Agent accounts and team structure. Users are recreated on Go4whatsup and invited to the workspace. Typically done by the switching team's admin in under 20 minutes.

3. The 7-day migration plan (step by step)

The seven days don't have to be seven consecutive days, but the steps have to happen in order because of how Meta's approval queue and the WABA transfer flow work. Most teams run it across a working week + the following Monday.

1. Day 1 · Audit

   Inventory what you have on WATI

   Export the list of active templates, flows, contacts, integrations, and agents from WATI. Sort into buckets A, B, and C above. Note message volume, primary campaign cadence, and the top 3 automations by usage — these are what you test first during parallel week.

   Deliverable: a single-page migration spec

2. Day 2 · Setup

   Set up your Go4whatsup workspace and invite agents

   Create the Go4whatsup workspace, invite the same agent list you have on WATI, match role assignments (admin, agent, viewer), and configure working hours and routing rules. Do this before any data comes in so the workspace structure is ready to receive contacts.

   Deliverable: agents logged in, routing rules live

3. Day 3 · Initiate transfer

   Initiate the Meta BSP transfer request

   In Meta Business Manager, initiate the Business Solution Provider change — the official flow that detaches your WABA from WATI and re-attaches to Go4whatsup. Meta notifies WATI, WATI has a window to release, and the number briefly returns to "unassigned" status before Go4whatsup re-registers it. The number stays active for outbound and inbound traffic during this window.

   Deliverable: BSP transfer initiated in Meta

4. Day 4 · Templates

   Re-upload and re-submit all active templates

   Bulk-upload the template library to Go4whatsup (same copy, same variables, same category tagging). Submit for Meta review. Most templates return approval within 24–48 hours. Any that Meta rejects are usually category mismatches (marketing submitted as utility, utility phrased as marketing) — easy to fix and re-submit same day.

   Deliverable: templates in review, tracking sheet updated

5. Day 5 · Contacts + flows

   Import contacts and begin flow rebuild

   Export contacts + tags from WATI to CSV; import into Go4whatsup using the wizard (map the WATI columns to Go4whatsup fields). Start rebuilding automation flows in parallel — each flow's WATI screenshot or export becomes the spec. Test each flow against a single test contact before marking it live-ready.

   Deliverable: contact base live, flows in staging

6. Day 6 · Integrations + parallel

   Wire integrations, run parallel week

   Connect Odoo, Zoho, Shopify, Google Sheets, or whichever integrations are in-scope. For every integration, send a single test record end-to-end — WhatsApp message triggered, CRM updated, no duplication. Once templates are approved and flows are tested, declare parallel-run live: the same number now answers via Go4whatsup, and WATI is on hot-standby.

   Deliverable: integrations tested, parallel run active

7. Day 7 · Cutover

   Complete cutover and decommission WATI

   Run the final cutover checklist (below). Send one live broadcast through Go4whatsup. Confirm inbound conversations land in Go4whatsup's inbox, agents are routing correctly, and integrations fire. Keep the WATI subscription active for 7 more days as a safety buffer, then cancel. Total elapsed time: one working week.

   Deliverable: live on Go4whatsup, WATI decommissioned

4. How the WhatsApp number transfer actually works

The single most common misunderstanding about a BSP switch is that the phone number has to go dark for hours or days. It doesn't. Meta's official BSP transfer flow was designed specifically so the WABA (WhatsApp Business Account) stays live during the handoff. The mechanics:

1. You initiate in Meta Business Manager. Open Business Settings → Accounts → WhatsApp Accounts, select the WABA, click "Request BSP change" and pick Go4whatsup as the new BSP. This sends a signed request to both WATI and Go4whatsup.
2. WATI releases the account. WATI has a release window (typically 24–72 hours) to formally un-assign the WABA from their system. The account is read-only during this window — outbound still sends, inbound still receives, but no new templates can be submitted on WATI.
3. Go4whatsup re-registers the number. The moment WATI releases, Go4whatsup's backend registers the WABA under your new workspace. The number is now active on Go4whatsup. Total brown-out window if done during business hours: usually under 15 minutes.
4. Webhooks re-point. Inbound message webhooks flip from WATI's endpoint to Go4whatsup's. Any customer who messages during the handoff window receives the inbound in Go4whatsup's inbox automatically.

5. Re-approving your message templates

Templates are the area where most migrations hit a speed bump — not because the process is hard, but because the re-review delay catches teams who didn't plan for it. Meta requires that every active template be re-submitted when a WABA moves to a new BSP. The template copy moves (Go4whatsup can bulk-import from WATI's CSV export), but Meta's approval does not.

What to expect

• Approval time per template: 24–48 hours typical, up to 7 days for borderline marketing content
• Approval rate on first submission: 85–90% for templates that were already approved on WATI. The rest come back with small fixes needed (mostly category or variable-placeholder issues).
• Template category changes since your last approval: Meta tightened the marketing/utility/auth/service category boundaries in 2024 and 2025. Templates approved as "utility" on WATI two years ago may now be classified as "marketing" by Meta — which is a higher conversation rate but a cleaner category.

How to minimise the approval delay

1. Start template re-submission on day 4 — before you actually need them on day 6–7.
2. Submit your highest-volume templates first, not alphabetically. Order of review in Meta's queue is not guaranteed to be FIFO.
3. Keep variable placeholders identical between WATI and Go4whatsup ({{1}}, {{2}} syntax). Changing them is a common reason for rejection even though the copy is identical.
4. For any template that's iffy (promotional with light click-bait, urgent language in utility), have a backup version ready with softer wording.

6. Importing contacts, tags, and history

Every modern BSP exports contacts in CSV with the standard WhatsApp schema (phone, name, tag, language, opt-in status, custom attributes). Go4whatsup's import wizard reads WATI's export format natively — the column mapping is automatic for the common fields and takes two clicks for custom attributes.

Contacts + tags

Export from WATI: Settings → Contacts → Export All. The resulting CSV includes phone, name, tags (comma-separated), custom fields, opt-in status, and last-seen timestamp. Import into Go4whatsup via Contacts → Import → CSV. The wizard auto-detects the WATI header row and produces a preview. Verify the tag column is splitting correctly (comma-separated), click import, and the base is live within 1–5 minutes for up to 100,000 contacts.

Conversation history

WATI exports the last 90 days of conversation history as JSON or CSV per contact, or as a bulk archive. Go4whatsup imports this as an archived thread attached to each contact record — visible in the agent inbox as a collapsed "history from WATI" timeline. Agents can search across archived threads exactly like live threads.

Saved replies and canned responses

Small enough that most teams just copy-paste them across during day 2 setup. Go4whatsup supports categorised saved replies and per-agent personal replies — the same structure WATI uses, so nothing is lost in the translation.

7. Rebuilding flows and automations

This is the part of the migration that teams dread — and it's usually much less painful than they expect. The reason: most teams have 5–15 flows that drive 80% of their automation load, and the rebuild of each one averages 20–40 minutes on Go4whatsup's drag-and-drop flow builder.

How to capture a WATI flow for rebuild

The quickest way is a screenshot + a brief note for each node. You don't need WATI's underlying JSON — the goal is to capture the logic, which the rebuilder can translate. For each flow:

• Screenshot the flow canvas with all nodes visible (zoom out).
• Document the trigger: webhook, keyword, button click, scheduled.
• Document conditional branches: what variable is checked, what values route where.
• List the message templates / content each terminal node sends.
• List any webhooks that fire back to your CRM or inventory system.

Flow rebuild mapping: WATI → Go4whatsup

Most teams find that 20–30% of their WATI flows can be simplified or removed entirely on Go4whatsup — because the AI auto-reply and drafted-reply layers cover cases that previously needed a dedicated flow. The rebuild is a useful forcing function to audit what's still worth having.

8. Re-wiring CRM, Shopify, and other integrations

Integrations split into three categories for migration purposes, and each has a different re-wire path:

Native integrations (rebuild with clicks, not code)

For tools where Go4whatsup ships a native connector — Odoo, Zoho CRM, Shopify, Google Sheets, and others — re-wiring is a 5-minute installation from the Go4whatsup integrations page. Credentials (API key, OAuth consent) are entered once; field mapping is pre-configured for the common use cases and customisable for edge cases. This path replaces Zapier zaps that were previously bridging WATI to these tools and usually reduces failure points at the same time.

Zapier / Make (re-point at Go4whatsup)

If you have existing Zapier zaps fired from WATI webhooks, the fastest path is to disconnect the WATI trigger and add the equivalent Go4whatsup trigger. Zapier's Go4whatsup app exposes the same event types — inbound message, template sent, status update, tag added — so the downstream action chain usually works unchanged. Expect to spend 2–3 minutes per zap.

Custom webhooks and direct API integrations

Teams with in-house code calling WATI's API need to update two things: the base URL and the authentication header. Go4whatsup's API is REST with bearer-token auth, broadly compatible in request/response shape with the WhatsApp Cloud API itself — which means if your code was written to the Cloud API standard originally, it often works unchanged. For custom WATI-specific endpoints, our migration team provides a one-page mapping document.

9. The parallel-week validation playbook

Parallel week is the single most important operational decision in a migration — and the step teams are most tempted to skip. Don't. Two to three days of parallel running, where inbound traffic is visible on both WATI and Go4whatsup, catches almost every issue that would otherwise blow up at cutover.

What "parallel" means in practice

Since a WhatsApp number can only be assigned to one BSP at a time, true parallel traffic isn't possible. What is possible is: switching the number to Go4whatsup, keeping WATI's subscription paused-but-active, and having a documented rollback procedure ready if something breaks in the first 48 hours. Teams that skip this step typically lose at cutover because a flow they didn't think to test (usually a low-volume edge case like an abandoned-cart trigger) doesn't fire correctly.

The 48-hour validation checklist

10. What can go wrong (and how to avoid it)

These are the top five issues we see in WATI → Go4whatsup migrations — ordered from most common to least — and the prevention for each one:

11. Real cost of staying on WATI vs switching

A fair comparison has to include three cost buckets, not just the platform subscription. Most teams underestimate bucket 3 (hidden operational cost) and overestimate bucket 2 (migration labour).

Worked example: 10-agent support team, 40,000 monthly conversations

• WATI Business plan: roughly $799 USD/month for 10 seats + Meta conversation fees
• Go4whatsup Premium plan: AED 999 / month (approximately $272 USD) with unmetered seats + Meta conversation fees (pass-through, no markup)
• Monthly delta: roughly $500 saved per month, or $6,000 per year — at the same message volume
• Payback on migration effort: under one month

Always verify with live pricing on our pricing page and WATI's current plans — SaaS prices move.

12. How Go4whatsup runs WATI migrations

For teams on our PRO and Enterprise plans, the migration is a packaged service with a named owner and a shared tracker. Here's what the service includes:

13. Frequently asked questions