waplyGuide
Checklist: migrate Wazzup or Radist to WhatsApp Cloud API in Kommo
·
You can move a WhatsApp number used with Wazzup, Radist, or a similar connector onto Meta’s official Cloud API in Kommo — but treat it as a planned cutover, not a one-click swap. Confirm WABA ownership and Meta Business verification, inventory templates and automations, migrate through Meta’s transfer path (do not disconnect the old host early), then reconnect with Waply on official Cloud API. History, bots, and templates do not always transfer 1:1 — do not assume anything your current vendor or Meta does not guarantee.
Wazzup (Wazzup24) and Radist (Radist.Online) are popular third-party WhatsApp connectors for Kommo. Teams leave them for official Cloud API when they want Meta-native stability, clearer template and compliance paths, or eligibility toward WhatsApp Calling API on platform-only numbers. For a feature matrix, see the integrations comparison. For path selection (new number vs coexistence vs migration), see the connect guide.
Free 3-day trial of AI 24/7, then pick a plan.
Who this is for
Use this checklist if you already run WhatsApp inside Kommo through Wazzup, Radist, or another third-party connector and you want Meta’s official Cloud API — typically with Waply installed in Kommo.
- Kommo admins and sales ops who own the number and Meta Business Portfolio.
- Agencies migrating client numbers without promising “zero downtime / full history forever.”
- Teams on unofficial QR / “grey” sessions who need a different path toward Cloud API (see WhatsApp Lite and integrations guides).
Why move to the official WhatsApp API (Cloud API)
Third-party connectors can be a good fit for messaging-first Kommo teams. Moving to official Cloud API is usually about platform alignment — not “your vendor is bad.” Common reasons teams switch:
- Stability and support paths tied to Meta’s Cloud API and Business Manager.
- Template lifecycle and category rules managed in Meta WhatsApp Manager.
- Clearer compliance posture for business messaging (still follow Meta policies).
- Eligibility path toward WhatsApp Calling API on platform-only numbers (coexistence numbers: messaging yes, calls no — Meta).
Waply connects WhatsApp only through Meta’s official Cloud API — not unofficial QR/session connectors. Waply AI runs on third-party models and is independent of Kommo native AI.
Pre-migration checklist
Finish this list before you revoke partner access or delete a channel. Skipping ownership or verification is the most common cause of multi-day downtime.
- WABA ownership: confirm the WhatsApp Business Account is under your Meta Business Portfolio (customer-owned / shared), not only partner-held On-Behalf-Of if that model still applies to your setup — Kommo notes OBO-owned WABAs are not supported for some migrate paths.
- Meta Business verification: business verified (or understand pending states) before expecting automatic migration.
- Number ownership: you can receive SMS/voice OTP on the number; two-step verification can be disabled when Meta’s migrate path requires it.
- Templates inventory: export or screenshot approved template names, languages, categories, and quality; note which are critical for campaigns.
- Automations map: list Salesbots, triggers, broadcast sources, and routing rules tied to the current WhatsApp source in Kommo — many need reconfiguration after cutover.
- Payment method: know who pays Meta conversation fees today and where the Billing Hub / payment method will live after partner change (Kommo documents possible send delays until a new method is set).
- Rollback plan: who can re-enable the old channel if inbound fails; do not delete historical leads in Kommo during cutover.
Exact automatic vs manual prerequisites can change. Use Kommo’s “connect from different integrations or providers” and “migrate your numbers” articles plus Meta’s partner migration docs as the live checklist.
Steps to migrate to the official WhatsApp API in Kommo
This is the decision sequence — UI clicks live in Waply docs. Coordinate Meta transfer with reconnecting the number in Waply; do not disconnect the old host “to fix a pending state” until the path is clear.
- Install Waply in Kommo (or open an existing install) and keep the old connector active until Meta migration requirements are confirmed.
- In Meta Business Manager, confirm Portfolio, WABA status, payment method, and phone-number two-step settings per Meta/Kommo migrate docs.
- Start Numbers → Connect WhatsApp number in Waply and complete Meta Embedded Signup for the Business Portfolio, WABA, and phone number (migration or register path as offered).
- Wait until Waply shows the number as connected before turning Salesbot, broadcasts, or AI back on.
- Send a permitted test template (or customer-care reply inside the open window) and verify inbound webhooks land in the Kommo lead.
- Only then disconnect or pause the old Wazzup/Radist channel so you do not dual-send or drop ownership mid-transfer.
- Docs: connect a number
- Docs: numbers, coexistence, migration
- Guide: Connect WhatsApp to Kommo
- Guide: WhatsApp API pricing 2026
What may not carry over
Do not promise full history, bots, or every template “automatically.” Outcomes depend on Meta’s migrate rules and whether you use a Kommo-documented source-merging path versus a clean reconnect.
- Chat history / media: may stay in the old CRM source or only partially sync. Do not count on “keeps all chats” unless your exact path documents it.
- Salesbot and triggers: Kommo’s own migration articles often say automations reset and must be reconfigured — budget time to rebuild.
- Templates: Meta may duplicate eligible approved templates into the destination WABA on partner migration; duplicated templates can be re-checked and some may become rejected. Manual paths may require recreate + re-approval. To check which messages need a template outside the 24-hour window and how to get one approved again, see the WhatsApp templates in Kommo guide.
- Display name, quality-related messaging limits, and Official Business Account status: Meta describes what can retain on phone-number migration among solution partners — confirm in Meta docs for your case.
- Grey / unofficial sessions: not the same as Cloud API migrate; plan a proper Cloud API onboard (and read the Lite guide).
Partner blogs sometimes compress migration into “one click.” Use Meta + Kommo checklists, then prove send/receive before you cancel the old vendor.
Coexistence note
If the number must stay on the WhatsApp Business app and Cloud API together, that is Meta coexistence — a different path from migrating off a BSP onto a platform-only WABA.
- Messaging: coexistence can sync 1:1 chats between the Business app and Cloud API / CRM (per Meta + Kommo).
- Calls: Meta does not enable WhatsApp Calling API on coexistence-onboarded numbers. Waply can use coexistence numbers for messaging; calls need an eligible platform-only number.
- If your goal after leaving Wazzup/Radist includes Calling API, recordings in the lead, or Voice AI on calls, plan platform-only — not coexistence.
Onboard WhatsApp Business app users: requirements
According to Meta’s documentation on onboarding WhatsApp Business app users (checked October 14, 2026), this is what a coexistence connection needs:
- The number’s WhatsApp Business app must be on version 2.24.17 or higher.
- During signup you enter the app’s number, receive a verification code, tap Connect in the app and confirm; you also choose whether to share your chat history.
What changes once connected, according to the same Meta page:
- The number gets a fixed throughput of 20 messages per second on Cloud API.
- Contacts and 1:1 chats from the last 6 months can be synced; group chats are not synced.
- In the app, disappearing messages, view once messages and live location are turned off; broadcast lists become read-only.
- Messages you send from the app stay free; messages sent through Cloud API follow Cloud API pricing.
Calls: Meta does not support voice or video calls on Cloud API for coexistence numbers, so those numbers cannot make WhatsApp calls with Waply (a Meta restriction). Messaging and the other Waply features that do not depend on calls can work on those numbers.
After go-live checks
- Quality rating in WhatsApp Manager: watch Green / Yellow / Red trends after cutover; spikes in blocks or low-quality templates hurt deliverability.
- Messaging limits: Meta applies portfolio/number limits that scale with quality and usage. Exact tiers vary (teams often see starting limits and higher steps such as on the order of ~250 or ~2,000 unique users in a rolling window) — confirm live in WhatsApp Manager; they change.
- Template statuses: verify critical templates are Approved on the destination WABA before campaigns.
- Kommo pipeline: spot-check that new inbound creates/updates the expected lead source and that agents reply from the new channel.
- Calls (if in scope): confirm the number is platform-only and Calling is enabled before testing human calls or Voice AI.
Treat Meta limit numbers as illustrative of the quality ladder, not a Waply SLA. Recheck WhatsApp Manager after go-live.
How Waply fits after you migrate
Waply is an independent product in Kommo on official Cloud API: messaging, human WhatsApp calls on eligible numbers, call intelligence, and text/voice AI on third-party models (not Kommo native AI credits).
Waply plans (USD, waply.online/pricing)
| Plan | Monthly | WhatsApp-relevant inclusions |
|---|---|---|
| Basic | USD 18 | Official-API messaging; human WhatsApp calls and recordings (90-day retention) |
| AI 24/7 | USD 39 | Everything in Basic + text AI agents, call intelligence allowances, 365-day retention |
| Voice AI | USD 89 | Everything in AI 24/7 + Voice AI agents on WhatsApp calls (managed/BYOK minutes) |
- Free 3-day trial of AI 24/7, then pick a plan.
- Coexistence numbers: messaging can work; WhatsApp calls do not (Meta restriction).
- Meta message and call charges are separate from the Waply subscription.
Frequently asked questions
How do I migrate Wazzup or Radist to WhatsApp Cloud API in Kommo?
Confirm WABA ownership and Meta verification, inventory templates and automations, follow Meta’s number/WABA transfer path without disconnecting early, then connect the number in Waply via Embedded Signup and test send/receive before turning off the old connector.
Will my WhatsApp chat history transfer?
Not always, and nothing here is guaranteed. Some Kommo-documented paths describe source merging that can continue conversations; other reconnects leave history on the old source. Export or screenshot anything critical before cutover.
Do templates need Meta re-approval?
It depends. On many partner phone-number migrations Meta can duplicate eligible approved templates; they may be re-checked and some can end up rejected. Manual recreates need fresh approval. Inventory first.
Will Salesbot and automations keep working?
Often they need reconfiguration. Kommo’s migration articles commonly note that bots and triggers reset — map them before cutover and rebuild after the new source is live.
Should I disconnect Wazzup or Radist first?
Usually no. Waply and Kommo both warn not to disconnect or delete an active number until the migration path is clear. Dual-running briefly is safer than orphaning the number.
Can I keep the WhatsApp Business app (coexistence) and still call from Kommo?
Messaging can work under coexistence. Meta does not enable Calling API on coexistence-onboarded numbers. For calls, recordings in the lead, or Voice AI on calls, use an eligible platform-only number.
Does Waply use unofficial QR WhatsApp?
No. Waply connects only through Meta’s official Cloud API.
What does Waply cost and is there a trial?
Basic is USD 18/month, AI 24/7 is USD 39/month, Voice AI is USD 89/month. The free 3-day trial is AI 24/7; then pick a plan. Meta and BYOK charges are separate when applicable.
Migrate with a checklist, then prove messaging
Own the WABA, inventory templates and bots, follow Meta’s transfer path, connect with Waply on official Cloud API, and only then retire Wazzup or Radist. Try AI 24/7 free for 3 days when you are ready.
Free 3-day trial of AI 24/7, then pick a plan.