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

1. Why teams are switching from Gupshup in 2026

Gupshup is a genuinely capable enterprise platform — multichannel, programmable, well-connected inside Meta. Teams who leave Gupshup almost always cite one of these four reasons, and it's worth being honest about which of them is actually driving your decision:

Pricing opacity and USD billing

Gupshup's pricing is quote-driven and typically quoted in USD. That works well for large enterprises with a dedicated procurement team; it works poorly for growing businesses that need to know what WhatsApp costs this month versus last month. Most Gupshup invoices combine platform fees, Meta conversation fees, and professional services into a single line — making it hard to see what's actually driving spend. Go4whatsup publishes AED / INR tiers on a public pricing page, passes Meta's conversation fee through at exact cost, and gives you a monthly bill with individual line items for each.

Bot Studio complexity and change velocity

Gupshup's Bot Studio is powerful but it's an engineering-grade tool. A small change — swap a button label, add a branch to an existing flow, route a different segment to a new template — often requires a ticket to Gupshup's services team or a 2-week professional-services engagement. For teams iterating on campaign funnels weekly, this is a serious drag. Go4whatsup's drag-and-drop flow builder moves most of these changes into the hands of the marketing team directly.

ACE AI priced separately (and adding up)

Gupshup's ACE AI conversational layer is a genuinely strong product, but it's licensed as a separate SKU on top of the base platform fee. Teams that adopt it find themselves paying for two things — the messaging platform and the AI layer — with combined monthly spend that often exceeds Go4whatsup's all-inclusive Premium or PRO plan. Go4whatsup ships auto-reply, drafted replies, campaign copy generation, and language detection inside the base product.

Enterprise-sales cycle for product changes

Upgrading your Gupshup plan, adding a new number, or enabling a new feature typically routes through an account manager and a signed change order. This is appropriate for large enterprises but frustrating for mid-market teams that just need to add a sender or a seat. Go4whatsup's plan upgrades are self-serve inside the app.

2. What actually moves and what gets rebuilt

On day one, sort your Gupshup assets into three buckets. Each bucket has a different handling instruction during migration:

Bucket A — Moves as-is

• The WhatsApp Business Account (WABA) number. Transfers cleanly via Meta's official BSP change flow. Number stays active during the handoff.
• Green-tick status. Meta ties OBA verification to the WABA, not to the BSP. Green tick transfers with the number.
• Meta Business Manager and Facebook Page. Sits with you in Meta, not with Gupshup. Unaffected.
• Display name and business category. Remain with the WABA through the transfer.

Bucket B — Exports from Gupshup, imports into Go4whatsup

• Contacts, tags, and custom attributes. Gupshup exports a well-structured CSV — one of the easier inventories to re-import.
• Template library content. Template copy, variables, buttons, and category tags export via CSV.
• Conversation history (last 90 days). Gupshup provides a JSON / CSV export; Go4whatsup imports as archived threads.
• Opt-in consent records. Gupshup tracks opt-in timestamps and source; preserve these during import to maintain your DPDPA / PDPL audit trail.

Bucket C — Rebuilt on Go4whatsup

• Message template approvals. Meta re-reviews per BSP. Re-submit same copy; approvals typically land in 24–48 hours.
• Bot Studio flows. These are the most structurally different from other BSPs' flow builders — node types, branch logic, and session-state handling don't map 1:1. Plan for 1.5× the per-flow rebuild time of a WATI or AiSensy migration.
• ACE AI configurations. Intent definitions, prompt templates, and escalation rules from ACE AI get re-created using Go4whatsup's built-in AI auto-reply layer (often with simpler configuration).
• Conversation Cloud integrations. If you're using Gupshup's Conversation Cloud as a unified agent console, the WhatsApp-specific part moves to Go4whatsup's inbox; any SMS or voice channels that were co-handled on Conversation Cloud need a separate vendor or continue on Gupshup's SMS-only plan.
• Agent accounts and team routing. Recreated on Go4whatsup in roughly 20 minutes for most team sizes.
• Webhooks and custom integrations. Re-pointed from Gupshup's endpoints to Go4whatsup's API.

3. The 7-day migration plan

The steps have to happen in order because of Meta's approval queue and BSP transfer flow. Most teams run this as one working week, sometimes stretched to 8–10 days if the Bot Studio inventory is deep.

1. Day 1 · Audit

   Inventory your Gupshup stack

   Export template list, Bot Studio flow inventory, ACE AI intent library, contact base, integration list, and agent roster. Document the top 5 flows by monthly execution volume — these are the critical-path rebuilds. Pull one invoice to confirm what features you're paying for.

   Deliverable: migration spec + "what to actually keep" list

2. Day 2 · Setup

   Provision your Go4whatsup workspace

   Create the workspace, invite the same agent list, mirror role assignments, set working hours and routing rules. Pre-configure the WhatsApp sender number in Go4whatsup's queue so it's ready to receive once the BSP transfer completes.

   Deliverable: agents logged in, workspace configured

3. Day 3 · Initiate transfer

   Start the Meta BSP transfer

   In Meta Business Manager → WhatsApp Accounts → select WABA → Request BSP change → select Go4whatsup. Meta notifies Gupshup; Gupshup has a 24–72 hour release window. Number stays active throughout. Templates cannot be newly submitted on Gupshup during the release window (but existing ones still send normally).

   Deliverable: BSP change initiated

4. Day 4 · Templates

   Bulk re-submit your template library

   Upload your template CSV to Go4whatsup. Submit for Meta review with the highest-volume templates prioritised. Most Gupshup-approved templates pass on first review; borderline marketing ones occasionally need a wording softening. Meta's 2024 category tightening means utility-tagged templates need a second look before re-submission.

   Deliverable: templates in review, tracker populated

5. Day 5 · Contacts + flow rebuild

   Import contact base; begin Bot Studio flow rebuild

   CSV import contacts with tags and custom attributes. Start rebuilding your top 5 Bot Studio flows using the screenshots / exports as the specification. For each flow, map node-by-node: Bot Studio keyword nodes become Go4whatsup keyword triggers, branches become conditional splits, API hooks become webhooks out.

   Deliverable: contact base live, top flows in staging

6. Day 6 · Integrations + AI + parallel

   Wire integrations, recreate AI layer, declare parallel

   Connect Odoo / Zoho / Shopify / Google Sheets native. Rebuild ACE AI intents using Go4whatsup's AI auto-reply + drafted-reply configuration (often 40–60% simpler). Test each flow end-to-end. Declare parallel-run: the number is now live on Go4whatsup, Gupshup is on hot-standby.

   Deliverable: integrations tested, AI live, parallel active

7. Day 7 · Cutover

   Run the cutover checklist, decommission Gupshup

   Send a live broadcast through Go4whatsup; confirm delivery rate and click-through. Verify inbound conversations land in Go4whatsup's inbox, agent routing fires, integrations update downstream systems. Keep the Gupshup subscription active 7 more days as a safety buffer, then cancel. Elapsed time: one working week.

   Deliverable: live on Go4whatsup, Gupshup decommissioned

4. How the WhatsApp BSP transfer works

The single biggest misconception about a Gupshup switch is that the phone number has to go dark. It doesn't. Meta's official BSP transfer flow was built specifically for this handoff — and because Gupshup is a tier-1 Meta Business Partner, they consistently process BSP release requests quickly and cleanly.

1. Initiate in Meta Business Manager. Business Settings → Accounts → WhatsApp Accounts → select the WABA → Request BSP change → pick Go4whatsup. Meta sends a signed notification to both BSPs.
2. Gupshup releases. Typical release time: 24–72 hours. During this window, the account is read-only for configuration but outbound and inbound traffic continue normally on Gupshup.
3. Go4whatsup re-registers. Once Gupshup releases, Go4whatsup's backend claims the WABA. Brown-out window during business hours is usually under 15 minutes.
4. Webhooks flip. Inbound message webhooks re-point from Gupshup to Go4whatsup. Customers messaging during the handoff land in Go4whatsup's inbox automatically once registration completes.

5. Re-approving your message templates

Gupshup and Go4whatsup both use Meta's standard template format, so the copy transfer itself is clean. What doesn't transfer is Meta's approval — every template has to be re-reviewed once the WABA moves.

What to expect

• Per-template approval: 24–48 hours typical, up to 7 days for borderline promotional content
• First-pass approval rate: 85–90% for templates already approved on Gupshup — the rest usually need category corrections
• Category reclassification: Meta's 2024–2025 category tightening means some "utility"-tagged templates are now treated as "marketing" — check tagging before re-submission

Minimising the delay

1. Start template re-submission on day 4 — a day or two before you need them on cutover day.
2. Submit highest-volume templates first. Meta's queue is not strictly FIFO.
3. Keep variable placeholders character-for-character identical ({{1}}, {{2}}). Re-formatting these is a silent rejection trigger.
4. For anything iffy, queue a softer-worded backup version in parallel.

6. Importing contacts, tags, and conversation history

Gupshup's CSV exports are one of the cleanest in the BSP market — the structure maps almost directly to Go4whatsup's import schema. Expect minimal column mapping work.

Contacts + tags + custom attributes

Export from Gupshup: Platform → Contacts → Export. The CSV includes phone, name, tag list, opt-in status with timestamp, opt-in source, language preference, and any custom attributes you've configured. Go4whatsup's import wizard auto-detects Gupshup's header structure and produces a preview. Verify tag splitting, confirm opt-in metadata is carrying across, click import. For bases up to 500,000 contacts, the import runs in 5–20 minutes.

Conversation history

Gupshup retains 90 days of conversation history by default; some enterprise plans extend this. Export as JSON or CSV per contact, or as a bulk archive from the Platform. Go4whatsup imports this as archived threads indexed against each contact, visible in the agent console and searchable alongside live conversations.

Opt-in consent preservation

Your opt-in list is regulated under India's DPDPA and the UAE's PDPL. Gupshup's exports include opt-in timestamp and source fields (common sources: website signup, form fill, SMS short-code, in-conversation agree-to-receive). Preserve these during import so the audit trail remains intact.

7. Rebuilding Bot Studio flows on Go4whatsup

Bot Studio is the most capable flow builder among the major BSPs — and its structural depth is exactly what makes the rebuild the longest part of a Gupshup migration. Plan for 40–60 minutes per medium-complexity flow on Go4whatsup.

How to capture a Bot Studio flow for rebuild

Unlike WATI or AiSensy, Gupshup's Bot Studio often encodes session state and contextual branching in ways that a screenshot alone won't fully capture. For each flow:

• Screenshot the flow canvas at full zoom.
• Export the flow as JSON if Bot Studio allows (on most plans, yes).
• Document the trigger (webhook, keyword, scheduled, campaign-scoped).
• For each conditional node, write out the variable being checked and the full list of values and their routes.
• Identify any session variables the flow reads or writes — these need to map to Go4whatsup's variable system.
• List every API hook with method, URL, headers, and expected response shape.

Bot Studio → Go4whatsup mapping

Many teams find that 25–35% of their Bot Studio flows can be simplified or dropped entirely on Go4whatsup because the built-in AI auto-reply layer covers cases that previously required a bespoke flow. The rebuild is a forcing function to audit which flows are actually still serving the business.

8. Replacing ACE AI and Conversation Cloud setups

If you're on Gupshup's ACE AI or Conversation Cloud add-ons, this is the part of the migration that needs the most care — because the functionality is real and valuable, and you need to make sure the replacement actually delivers the same customer experience.

ACE AI → Go4whatsup AI

ACE AI handles intent detection, entity extraction, slot-filling, and contextual responses. Go4whatsup's built-in AI layer covers: auto-reply with context awareness, drafted reply suggestions inside the agent inbox, campaign copy generation, language detection (Hindi, English, Arabic, Marathi, Tamil, and more), and fallback-to-agent routing. The setup model is different — Go4whatsup's AI uses natural-language configuration rather than explicit intent-and-entity trees — which means fewer configuration hours but a slightly different mental model. Teams typically rebuild an ACE AI setup on Go4whatsup in 1–2 working days.

Conversation Cloud → Go4whatsup inbox

The WhatsApp-specific functionality of Conversation Cloud (shared inbox, agent routing, canned replies, analytics) moves cleanly to Go4whatsup's inbox. If you were using Conversation Cloud to unify WhatsApp with SMS, voice, or email channels, the non-WhatsApp channels need a separate decision:

• Keep Gupshup for SMS / voice on their channel-specific SKU, while WhatsApp moves to Go4whatsup
• Consolidate to a broader CPaaS (Twilio, MSG91, Infobip) and handle WhatsApp + other channels through Go4whatsup integrations
• Email → a dedicated tool like Intercom, Freshdesk, or Zendesk

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

Gupshup ships an integration marketplace that connects to CRMs, e-commerce platforms, and custom webhooks. The re-wire path depends on how each integration was set up:

Native Go4whatsup connectors (5-minute rewire)

For Odoo, Zoho CRM, Shopify, Google Sheets, and other native integrations, the install is a 5-minute OAuth + field-mapping job. Credentials re-entered once; standard use cases pre-configured; customisations exposed as optional mappings. This path often replaces more complex Gupshup integration setups with cleaner native alternatives.

Zapier / Make bridges

If you have Zapier zaps triggered by Gupshup webhooks, swap the trigger step to Go4whatsup's Zapier app. Event types (inbound message, template sent, status update, tag added) map directly. Allow 3–5 minutes per zap.

Custom API integrations

If your in-house code calls Gupshup's REST API, the re-point is primarily: update base URL and swap the auth mechanism (Gupshup's API key → Go4whatsup's bearer token). Request/response structures are broadly compatible at the message-send, template-send, and webhook-receive level. Our migration team supplies a one-page API mapping doc for custom integrations.

10. The parallel-week validation playbook

Because a WABA can only live on one BSP at a time, "true parallel" isn't possible — but a 48-hour validation window with Gupshup's subscription paused-but-active is the industry-standard safety net. Skipping it is the most common reason Gupshup migrations have post-cutover surprises.

48-hour cutover validation

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

Top five issues we see in Gupshup → Go4whatsup migrations, ordered most to least common:

12. Real cost of staying on Gupshup vs switching

The honest cost comparison requires three buckets: platform fee, Meta conversation fee (same regardless of BSP), and the softer operational cost of change velocity.

Worked example: mid-market brand, ~60,000 monthly conversations, ACE AI enabled

• Gupshup base platform + ACE AI: typically $900–1,500 USD / month depending on negotiated quote, plus Meta conversation fees (bundled into the invoice)
• Go4whatsup PRO plan: AED 499 / month (approximately $136 USD) with AI included, plus Meta conversation fees (pass-through at exact cost, separate line item)
• Monthly delta: typically $700–1,200 saved, or $8,000–14,000 per year
• Payback on migration effort: under one month

Always verify with live pricing on our pricing page and your current Gupshup quote — numbers shift as teams renegotiate.

13. How Go4whatsup runs Gupshup migrations

On PRO and Enterprise plans, the migration is a packaged service with a named owner and a shared tracker. Included:

14. Frequently asked questions