On this page
In short
- Your WhatsApp Business Account, number and template library are Meta's, not the old platform's, so a switch is a reconnection, not a rebuild from zero
- What genuinely does not transfer is the old platform's own chat history and any automation logic built inside it; both need a plan before you cancel
- A one-week parallel run, both platforms connected where possible, or the old one kept read-only, catches gaps before customers notice them
A WhatsApp Business Account, its phone number, its message history with Meta, and its approved templates belong to your own Meta Business Portfolio, not to whichever platform happens to be connected to them. That single fact is what makes switching WhatsApp platforms fundamentally different from switching, say, email marketing tools: the hardest part of most SaaS migrations, moving your actual customer relationship and its history, is largely a non-issue here, because Meta already owns that layer regardless of which CRM you use on top of it. What genuinely takes work is everything built inside the old platform's own walls: its chat history (if you never ran the WhatsApp Business app on that number), its chatbot flows, and its team's habits. This guide walks through the full switch, step by step, with a specific note for each of eight platforms people most often migrate from.
Before you start: confirm what you actually own
Two questions determine how straightforward your switch will be, and both are worth confirming before you touch anything else.
Who owns the WhatsApp Business Account? If your business signed up directly with your current platform as a Tech Provider (the same relationship VGraple CRM uses), the WABA sits in your own Meta Business Manager, and you can confirm this yourself: log into business.facebook.com, and check that your WhatsApp Business Account, its phone number, and its connected apps are all visible and editable from your own account. If instead your platform intermediated the account on your behalf (an older-style BSP arrangement, still used by some vendors), ownership can be murkier, and it is worth asking the vendor directly, in writing, whether the WABA is registered under your business's Meta Business Manager or theirs.
Does a vendor hold your two-step verification PIN? Meta requires a 6-digit PIN to register or migrate a WhatsApp number directly on the Cloud API. If your current vendor registered your number on your behalf during onboarding (common when a business does not go through Embedded Signup itself), they may hold this PIN rather than you. Ask for it now, before you need it: without it, Meta's own recovery path, a wait period followed by re-registration with a new PIN through Meta Business Manager, is the only way forward, and that adds days to a migration that otherwise takes minutes. See the two-step verification PIN explained for exactly what it protects and why VGraple CRM never stores it in a way that could be used to move your number without your involvement.
The full migration, step by step
1. Confirm WABA ownership and gather access
Log into business.facebook.com and confirm you (not your outgoing vendor) have admin access to the Business Manager holding your WhatsApp Business Account. If you do not, request it from whoever set up the account originally, or from your outgoing vendor if they hold admin rights on your behalf. This is the single most important step, since every later step depends on being able to authorise a new app (VGraple CRM) against this WABA.
2. Decide: coexistence first, or a direct switch
If your team still answers from the WhatsApp Business app on a phone day to day, or you simply want to see VGraple CRM working against your real number and real contacts before committing, connect through coexistence instead of disconnecting your old platform immediately. Coexistence runs the phone app and VGraple CRM on the same number at once, importing up to 180 days of existing chat history and your phone's address book automatically within 24 hours of connecting. This is the lowest-risk path: nothing about your old platform's connection has to change yet, and you can evaluate VGraple CRM against live traffic before deciding.
If your team already works entirely through your old platform's inbox rather than the phone app, coexistence is not the relevant path; go straight to Embedded Signup in the next step.
3. Reconnect through Meta's Embedded Signup
From VGraple CRM's Settings, then Channels, then WhatsApp, choose Connect via Embedded Signup. This opens Meta's own popup, the same flow used by every Tech Provider, where you log into the Facebook account with access to your business, confirm the existing Business Manager, and select your existing WhatsApp Business Account and phone number rather than creating a new one. Grant every permission Meta's popup requests; declining any of them causes the connection to fail with a specific reason. See connecting your WhatsApp number for the full walkthrough, including what to do if the popup session expires partway through.
This step does not remove your old platform's access by itself. A WhatsApp Business Account can have several connected apps at once, so completing Embedded Signup with VGraple CRM does not automatically disconnect your outgoing vendor; that happens separately, deliberately, at the end of your parallel-run week (step 9).
4. If a vendor holds your PIN: get it, or plan for Meta's recovery path
If step 1 revealed that your outgoing vendor registered your number and holds the two-step verification PIN, request it in writing now. If they will not provide it, or you genuinely do not know it, Meta's recovery path applies: after a wait period, the number can be re-registered with a new PIN, or reset through Meta Business Manager directly. Build this into your migration timeline; it is the one step in an otherwise same-day switch that can take longer, and it is worth starting early rather than discovering it mid-cutover.
5. Export contacts, with consent status intact
Export your contact list from your outgoing platform as a CSV, including whatever consent or opt-in status field it tracks, before disconnecting anything. When importing into VGraple CRM, map the Phone, Name, Email, Language and Tags columns; only mark a batch as opted in if you genuinely have consent for every contact in that file, since VGraple CRM requires a separate consent attestation checkbox before it lets a batch be marked opted in, and sending without consent risks a number restriction under Meta's Business Messaging Policy. See importing contacts from CSV for the full column-mapping and duplicate-handling walkthrough; imports are capped at 5,000 rows per file, so a large list needs multiple passes.
Do not assume "everyone in my old platform's contact list is opted in" just because they were reachable there. Carry over the actual consent status your old platform tracked, not a blanket assumption, and when in doubt, leave a contact unmarked rather than guessing.
6. Resubmit templates only if you created a new WABA
In the common case, where your WhatsApp Business Account itself does not change, your approved templates carry over automatically and are visible in VGraple CRM immediately after connecting, since templates belong to the WABA, not to the platform. Only if your migration involves creating a genuinely new WhatsApp Business Account, unusual, and worth avoiding if at all possible, do templates need to be recreated from scratch and resubmitted to Meta for approval in the new WABA, which can take anywhere from minutes to a day depending on Meta's review queue.
7. Rebuild chatbot flows and automation rules
This is the one piece of real manual work in a migration, and it exists regardless of which two platforms are involved: chatbot logic, automation rules, and sequence triggers are built inside each platform's own tooling and never export between systems. Recreate your core flows (welcome message, FAQ deflection, lead capture, appointment booking, any category-specific automation) in VGraple CRM's flow builder. Most businesses find a handful of flows cover the bulk of their automated volume; rebuilding those typically takes a day or two, not weeks, since the flow builder's node types (message, condition, template, CRM action, webhook, WhatsApp Flow form, AI, human handoff) map closely to what most platforms in this category already offer.
8. Reconnect integrations
If your outgoing platform fed data to or from Zapier, Make, Pabbly Connect, or your own systems via webhooks or a direct API integration, these need to be rebuilt against VGraple CRM's own connections, not migrated automatically, since each platform's Zap or webhook configuration is specific to that platform's API. VGraple CRM's Zapier app covers six common triggers (new message, new contact, new lead, lead stage changed, form submission, contact opted out) and three actions (send template, create or update contact, create lead) without writing code. For anything more custom, outbound webhooks deliver 15 event types with HMAC-SHA256 signing to Make, n8n, Pabbly Connect or your own endpoint, and the REST API is open directly to any developer with an API key for cases neither Zapier nor webhooks cover cleanly.
9. Run both platforms in parallel for about a week
Keep your old platform's inbox accessible (read-only if you have already reconnected the number to VGraple CRM through Embedded Signup, since both platforms cannot both actively send from the same number once you have moved past coexistence) for roughly a week while your team gets comfortable with VGraple CRM's inbox, and while at least one full cycle of your recurring automations (reminder sequences, scheduled broadcasts, follow-up flows) runs in the new platform. This is when gaps surface: a flow not yet rebuilt, a template category mismatched, a webhook integration silently not firing. A week is enough time to catch these before a customer notices a missed message, without dragging the transition out so long that the team reverts to old habits.
10. Disconnect the old platform
Once the parallel week confirms VGraple CRM is handling everything correctly, disconnect the old platform's access to your WhatsApp Business Account from Meta Business Manager (its connected-apps list), or from the old platform's own settings if it offers a disconnect option. This does not affect your WABA, number, template library, or Meta's own message history; it only removes that platform's authorisation to use the account, exactly the same relationship VGraple CRM itself holds and can be revoked from your side at any time.
What does not transfer, stated plainly
- Chat history inside your old platform's own database. Unless it came from the WhatsApp Business app itself (recoverable via coexistence's 180-day import), conversation history that only ever lived inside another CRM's database does not move to VGraple CRM. Export it from the old platform if it offers an export, and keep that export archived for reference even after switching.
- Chatbot flows and automation logic. These are rebuilt, not migrated, in every switch between every pair of platforms in this category, without exception.
- Custom fields, tags and pipeline stages specific to the old platform's data model. Contacts and their phone-based identity carry over cleanly through a CSV export/import; a custom pipeline structure or field set built specifically around the old platform's UI needs to be recreated to match how VGraple CRM's own leads pipeline and custom fields work.
- Historical analytics and reporting. Delivery rates, campaign performance and agent productivity numbers recorded inside the old platform stay there; VGraple CRM's own reporting starts fresh from the point of connection, the same way Meta's own message history is unaffected but a platform's internal analytics database is not something Meta holds on your behalf.
Per-platform migration notes
Wati. Confirm your WhatsApp Business Account sits in your own Meta Business Portfolio (standard for a direct Wati signup); Wati's own help centre documents number-porting steps if you are unsure. Templates carry over automatically since they belong to the WABA. Wati's chatbot flows and its add-on automation triggers do not export; budget a day or two to rebuild your core flows in VGraple CRM's flow builder.
Interakt. If you use Interakt's separate Sales CRM product alongside its messaging plans, export your leads and pipeline data from that product specifically, since it is a distinct system from the WhatsApp messaging side. Interakt's Instagram-only free tier and any Instagram automation built there also need reconstructing if you rely on it, since VGraple CRM covers Instagram DMs including story replies and mentions but the automation logic itself is rebuilt, not imported.
AiSensy. AiSensy's chatbot builder and AI agent are separate paid add-ons; export or document their flow logic before cancelling, since that subscription (and its logic) ends when you stop paying for it, not when you disconnect the WhatsApp number. AiSensy's per-message rate (stated at Rs 1.09 for marketing) is above Meta's own published India rate, so switching alone removes that markup at the same send volume, independent of any feature difference.
Gallabox. If you use Gallabox's pipeline management (available on its Advanced tier) or its AI voice agents, these are Gallabox-specific products with no direct export path; recreate the pipeline structure in VGraple CRM's own Kanban leads pipeline, and rebuild AI-handled call flows as WhatsApp-side automation if voice was not core to your use case. Gallabox's channel add-ons (Instagram, voice, web) are billed and configured separately per channel; reconfirm which channels you actually need in VGraple CRM rather than assuming a like-for-like mapping.
DoubleTick. DoubleTick's AI-governance features (irritation detection, SLA-breach alerts, refund-request flagging) and its analytics views (Agent Productivity, Campaign Funnels, CX Topic Charts) are DoubleTick-specific and do not have a direct export; if these were central to your workflow, plan how VGraple CRM's own SLA tracking and analytics cover the same operational need before cancelling. Since DoubleTick publishes no self-serve pricing, confirm your actual current monthly cost from your own invoice before comparing it against VGraple CRM's published plans.
Zoko. If your WhatsApp catalogue is tied to Shopify through Zoko, confirm your Shopify product feed and catalogue setup separately, since VGraple CRM does not have a native Shopify listing; the practical route is Zapier's Shopify trigger feeding into VGraple CRM's Send Template Message or Create Lead action. Zoko's named AI agents (FAQ, order-status, sales) and its cart-recovery automation are rebuilt as flows in VGraple CRM's flow builder, not migrated directly.
Respond.io. If you use Respond.io specifically for its wide channel coverage (Telegram, Line, Viber, TikTok alongside WhatsApp), confirm which of those channels VGraple CRM actually needs to replace for your business; VGraple CRM covers WhatsApp, Instagram, Messenger and web chat, a narrower set. Respond.io's Monthly Active Contacts billing model does not map directly to VGraple CRM's contact-and-conversation-cap plans, so compare your actual monthly MAC count against VGraple CRM's plan tiers rather than assuming a direct price equivalence.
SleekFlow. SleekFlow's AgentFlow AI product (its four agent types: Inbound, Data Analyst, Copilot, Outbound) is a SleekFlow-specific system; document what each configured agent actually does before cancelling, so the equivalent logic can be rebuilt using VGraple CRM's AI chatbot and flow automation. Like Respond.io, SleekFlow bills by Monthly Active Contacts, so compare against your real contact-reach numbers rather than seat count.
A parallel-run checklist for the final week
| Check | Why it matters |
|---|---|
| Every recurring automation (reminders, sequences) has run at least once in VGraple CRM | Catches a flow that looks right in testing but fails against real data |
| Templates used by active campaigns show as approved in VGraple CRM | Confirms the WABA connection carried templates correctly |
| Contact count and consent status match your export | Confirms the CSV import mapped correctly, especially opted-in status |
| Every Zapier zap or webhook that fed the old platform now points at VGraple CRM | A silently broken integration is the easiest gap to miss |
| At least one team member has sent and received a real message from each channel in use | Confirms Instagram, web chat and WhatsApp are all actually connected, not just WhatsApp |
| The old platform's access is still visible in Meta Business Manager, ready to revoke | Confirms you have not lost the ability to roll back if something is wrong |
Why this is easier than switching most other business software
Most SaaS migrations are hard because your data lives inside the vendor's own system and has to be extracted, cleaned and reloaded before the new tool is usable. A WhatsApp platform switch is structurally different: Meta, not any vendor, is the system of record for your WhatsApp Business Account, its number, its message history with Meta, its quality rating, and its approved templates. Reconnecting a new Tech Provider to an account you already own is a reconnection, not a rebuild. The parts that do require real work, chat history that only ever lived inside the old platform, flow logic, and integrations, are exactly the parts that would need rebuilding no matter which two platforms were involved, which is why the checklist above, and the platform-specific notes before it, focus there rather than on the WhatsApp connection itself.