Gupshup to Ominiflow Migration Checklist (Free)

Name: Ominiflow WhatsApp Business Platform
Brand: Ominiflow
Availability: InStock

Gupshup to Ominiflow
Migration Checklist

40+ tasks in five phases. Tick them off in your browser, then print or save as PDF for your team and agency.

0 of 40 tasks completed

Phase 1 — Pre-migration (Week before switch)

Phase 2 — Ominiflow setup

Complete Meta Business verification on Ominiflow

Connect WhatsApp Business Account (WABA) to Ominiflow

Submit or sync existing message templates to Meta

Import contact list (dedupe against opt-out numbers)

Recreate chatbot flows in Ominiflow visual builder

Configure team inbox, agent roles, and assignment rules

Recreate Gupshup API send-message calls as Ominiflow webhooks or SDKs (Node/PHP/Python)

Set up CRM integration (Zoho, HubSpot, or webhook)

Reconnect Shopify / e-commerce triggers if applicable

Phase 3 — Number migration

Request number migration from Gupshup (or release number from Gupshup BSP)

Initiate number port on Ominiflow with Meta Cloud API

Do NOT delete number from Meta Business Manager

Wait for Meta approval (typically 1–3 business days)

Confirm display name and business profile carry over

Verify green tick / verified badge status if applicable

Phase 4 — Testing (before go-live)

Send test utility template to internal team numbers

Send test marketing template to opted-in test list

Verify inbound messages hit Ominiflow inbox

Test chatbot keyword triggers and button replies

Confirm CRM sync logs conversations correctly

Test webhook payloads to your backend

Run a small broadcast (50–100 contacts) as dry run

Check delivery, read receipts, and failure reports

Phase 5 — Go-live & post-migration

Pause active Gupshup campaigns and automations

Switch live traffic to Ominiflow (update CTAs, QR codes if needed)

Notify agents of new inbox URL and login credentials

Monitor first 48 hours for delivery issues

Cancel Gupshup WhatsApp (keep SMS/RCS contract if you still need those channels)

Update website WhatsApp chat widget links

Document new SOPs for agents on Ominiflow

Schedule 7-day check-in with Ominiflow support

Need help leaving Gupshup?

We handle contact import, template review, and number porting on paid plans. Compare pricing or book a migration call when you are ready.

Email checklist to your inbox

Migration FAQ

Will I lose my approved WhatsApp templates when leaving Gupshup?

No. Templates belong to your Meta Business Manager, not Gupshup. When you connect the same WhatsApp Business Account (WABA) to Ominiflow, existing approved templates remain available. You may need to re-sync or re-submit if names or languages changed during export.

How long does Gupshup to Ominiflow migration take?

WhatsApp-only SMB cutovers typically take 5–7 business days with complete Business Manager documents. Enterprise CPaaS stacks (custom APIs, SMS/RCS coexistence, SI-built bots) can take 2–4 weeks. Recreate API traffic on Ominiflow webhooks or SDKs before you release the number.

Can I keep Gupshup for SMS and move only WhatsApp?

Yes. Many teams keep Gupshup (or another SMS aggregator) for DLT SMS fallback and move WhatsApp inbox, bots, and broadcasts to Ominiflow. Document which channels stay where before you cut over the WABA.

Is there downtime during migration?

With proper sequencing, downtime is minimal. Build and test on Ominiflow before pausing Gupshup WhatsApp traffic. Number porting may have a short window where inbound messages queue — our team advises on timing and cutover order.

Does Ominiflow help with migration for free?

Yes on paid annual plans: contact import, template assistance, agent training, and porting support are included in onboarding. Trial accounts can use this checklist self-serve; book a migration call when you are ready to switch.

Gupshup → Ominiflow Migration Checklist

Gupshup to OminiflowMigration Checklist