How to Migrate From Kommo to Tenashi

Kommo (formerly amoCRM) is a mature CRM with a long track record. It added WhatsApp as one of many channels — alongside email, Instagram, Telegram, Facebook Messenger and others. The CRM and pipeline features are genuinely strong; that's Kommo's heritage and where it's earned its reputation.

The mismatch for WhatsApp-first teams is structural: Kommo is a multi-channel CRM that added WhatsApp, not a WhatsApp inbox that added a CRM. The WhatsApp integration requires the official Business API and BSP provisioning before your team can start, the shared inbox experience inside a CRM designed for many channels isn't always smooth, and the catalog and support ticketing exist as integrations or add-ons rather than first-class features.

If WhatsApp is your primary channel and you want a tool designed around that — with a built-in CRM, pipeline, tickets and catalog — here's the migration path from Kommo to Tenashi.

What Kommo genuinely does well

Fair framing first: Kommo's CRM is strong. The sales pipeline, lead management and multi-channel inbox breadth — managing WhatsApp, Telegram, email and Instagram in one place — is its genuine value. If you use multiple channels substantially and you've invested in Kommo's pipeline and automation setup, weigh the switch carefully.

Teams move to Tenashi when:

• WhatsApp is the dominant or only channel. Managing eight channels at a surface level costs more in setup and maintenance than managing one channel deeply.
• The WhatsApp connection is friction-heavy. Kommo's WhatsApp integration uses the official Business API and BSP provisioning — a verification process that needs to happen before your team can reply to the first message.
• The inbox experience for WhatsApp conversations isn't clean. A CRM designed for many channels treats WhatsApp as one data source. A tool designed for WhatsApp treats it as the primary surface — the difference shows in daily use.

What changes when you switch to Tenashi

Honest trade-off: Kommo's CRM depth across multiple channels is a genuine strength. If you use email, Telegram and Instagram alongside WhatsApp and want deal history across all of them in one record, that's Kommo's speciality. Tenashi's CRM is purpose-built around WhatsApp conversations — deep within that channel, not across many.

Step-by-step: migrating from Kommo to Tenashi

1. Export your CRM data

Kommo has decent export tools. Export your contacts and companies (CSV/XLS), including all custom fields, pipeline stages and deal data. Export open deals with their current stages and owners. Download any saved reply templates and note key automation logic.

This export is the most important step — Kommo's CRM data is where the value is, and you want it all before you start.

2. Decide on your WhatsApp number

• Same number. The number connected to Kommo via BSP/API needs to be released from the WhatsApp Business API before linking it to Tenashi. Work with your BSP or through Meta Business Manager to deregister the number (step 3).
• New number. Link a different existing WhatsApp number to Tenashi now and migrate contacts gradually.

3. Release the number from the WhatsApp Business API

Kommo's WhatsApp integration uses the official Business API through a BSP (Business Solution Provider). A number on the API cannot simultaneously be a linked device. Contact your BSP or go to Meta Business Manager to deregister the number. This may involve coordination with your BSP's support team. Plan for a quiet window for the transition.

4. Connect to Tenashi

Start your Tenashi trial and scan the QR code with the WhatsApp app on the phone holding your number. Done in under a minute. WhatsApp groups now appear in the shared inbox — the API that Kommo's integration used couldn't access them.

5. Import your CRM data and rebuild the workspace

Upload the contacts CSV, then map your Kommo fields to Tenashi's CRM:

• Contact fields — source, industry, company size, lead stage, region.
• Company records — create company contacts and link individual contacts to them.
• Deal pipeline — recreate your Kommo pipeline stages in Tenashi, recreate open deals with the correct stage and owner.
• Product catalog — add your products so agents can share cards in conversation.
• Support ticket settings — set up SLA targets and issue categories.
• Canned replies — your most-used message templates.
• Automations — keyword routing, auto-assign, after-hours messages.

6. Move your team in

Invite your agents, assign open deals and conversations. Run a full test: reply to an incoming message, push a deal through the pipeline, share a product from the catalog, raise a support ticket. Give Kommo notice once you've validated the setup.

Where Tenashi fits

Tenashi is the answer for teams where WhatsApp is the primary channel and they want it to feel like a first-class workspace rather than an add-on to a multi-channel CRM.

What you gain from Kommo:

• A WhatsApp-first inbox where the shared inbox, CRM and pipeline are designed around the chat, not around email and CRM records with a chat tab bolted on.
• A product catalog included in the plan for sharing products directly in conversation.
• Support tickets with SLA — not an integration, built in.
• Groups in the inbox — the API can't access them; a linked device does.
• No BSP provisioning — link your existing number with a QR scan.

Pricing: Starter $18/mo, Growth $27/mo, Scale $56/mo, 3-day Growth trial, no card.

Start your free trial → · See every feature

FAQ

Can I keep my WhatsApp number from Kommo?

Yes. Work with your BSP or Meta Business Manager to deregister the number from the WhatsApp Business API, then scan the QR code in Tenashi. Your customers keep messaging the same number.

How does Tenashi's CRM compare to Kommo's?

Kommo's CRM is mature and feature-rich, especially for multi-channel pipeline management. Tenashi's CRM is purpose-built around WhatsApp conversations: contact records, company history, deal pipeline, custom fields and a product catalog all designed for a WhatsApp-first workflow. For teams where WhatsApp is the primary channel, Tenashi's CRM is more relevant in daily use. For teams that genuinely work across many channels, Kommo's breadth is a real advantage.

Can I migrate my Kommo pipeline data to Tenashi?

Yes, by exporting your contacts and deals from Kommo and importing the contacts CSV into Tenashi. Deals can be recreated manually or in bulk — Tenashi doesn't have an automated Kommo migration tool, but a clean CSV export from Kommo makes the process straightforward.

What do I lose by leaving Kommo?

Primarily Kommo's multi-channel breadth — email, Telegram, Instagram and other channels in the same CRM alongside WhatsApp. If you actively use multiple channels and want a unified pipeline across them, that's Kommo's genuine strength. Tenashi trades that breadth for WhatsApp depth.

Does Tenashi have a catalog?

Yes. Tenashi's product catalog lets you add products and share product cards directly in WhatsApp conversations. It's built into the platform — no integration required.

---

WhatsApp is your primary channel and it deserves to be the primary surface, not an add-on tab. Start a free trial and move to a workspace designed around the way you actually work — conversations first, CRM attached, pipeline and tickets built in.