Migrating from amoCRM (Kommo) to Bitrix24: What Changes and How

amoCRM vs Bitrix24: Core Concept Mapping

Every major amoCRM/Kommo entity has a direct counterpart in Bitrix24, but the naming and internal structure differ enough that a side-by-side map is essential before you touch any data.

The table below translates the Kommo mental model into Bitrix24 terminology. Keep it open during field-mapping and pipeline configuration.

amoCRM / Kommo concept	Bitrix24 equivalent	Notes
Lead	Lead	Direct match; Bitrix24 supports a "simple CRM" mode that skips leads if preferred
Contact	Contact	Direct match; field settings transfer
Company	Company	Direct match; field settings transfer
Deal	Deal	Direct match; funnel stages transfer
Pipeline / Funnel	Sales funnel (Deal pipeline)	Multiple pipelines supported in Bitrix24
Custom field	Custom field	Left-panel fields transfer; right-panel (activity feed) fields do not
Tag	Tag	Direct match
Task	Task	Transfers with caveats - some task metadata may be lost
Note / Activity	Activity feed entry	Timeline entries may be partially lost depending on transfer method
User / Manager	Employee / User	Access rights are remapped manually (≈ 2 hours)
Digital Pipeline	Automation rules + Robots + Triggers	No direct import; must be rebuilt - see section below
Salesbot	Bitrix24 chatbot / Business Process	No direct import; logic must be re-implemented
Product catalogue	Product catalogue	Transfers via Excel export from Kommo
Document template	Document template	Templates must be reconfigured - field IDs change on import
Webhook / Integration	Marketplace app / REST API webhook	All integrations must be reconnected from scratch

Key takeaway: structured data (fields, stages, records) migrates well; automation logic and right-panel activity data do not migrate automatically and requires manual rework.

---

Two Transfer Methods: CSV vs API Migration App

The API-based migration app is the more complete method and is the approach used in real projects; CSV export is a fallback that loses notes, tasks, and right-panel activity data.

CSV / Excel export

Kommo allows you to export leads, contacts, companies, and deals to Excel. You clean and reformat the spreadsheet, then import it into Bitrix24 via the built-in CSV importer. This approach:

• Transfers only the fields visible in the left panel of a Kommo card
• Loses notes, call logs, email threads, and task history
• Loses pipeline stage history
• Is faster to execute for small, clean datasets

API migration app (recommended)

Bitrix24 offers a dedicated migration application available in the Bitrix24 Market (Applications → Market → Import and export → Migration to Bitrix24). According to official Bitrix24 documentation, this tool supports structured migration from other CRM systems and is the preferred path.

In practice, based on real projects:

• The migration is run multiple times - an initial pass, then a delta run to capture changes made in Kommo while Bitrix24 was being configured
• The API method transfers entities, fields, and pipeline stages in full
• Timeline entries (call logs embedded in the activity feed, certain note types) may still be partially lost even with the API approach - this is a structural limitation of what Kommo exposes via its export API
• Total data transfer effort via API: approximately 5 days for a typical SMB dataset

The only way to know precisely what will and won't transfer is to run a test migration first - which is the approach described in the next section.

---

The Test-Portal Approach: How to Validate Before Committing

Running the migration into a demo or trial Bitrix24 portal first - before your team touches production - is the single most effective way to eliminate data-loss surprises on cutover day.

The recommended workflow from real project plans:

1. Deploy a Bitrix24 trial portal (cloud, free tier or trial mode)
2. Run the full API migration from Kommo into this test portal - typically takes around 5 working days for an average dataset
3. Client review period - the team inspects transferred records, checks field completeness, tests filters and reports (approximately 10 days)
4. Go/no-go decision - if the result is acceptable, the same portal is upgraded to the target plan and full configuration begins; if not, no commitment has been made
5. Configuration on the confirmed portal - pipeline setup, user access, integrations, automation

This approach carries no financial risk for the client during the validation phase and surfaces any structural data issues before a production cutover.

---

What Has No Direct Equivalent: Digital Pipeline and Salesbot

amoCRM's Digital Pipeline and Salesbot have no one-click import path into Bitrix24 - they must be rebuilt using Bitrix24 Robots, Triggers, and Business Processes, which are functionally richer but structurally different.

Digital Pipeline → Automation Rules and Robots

Kommo's Digital Pipeline fires actions (send message, create task, change responsible, move stage) when a deal enters a stage. Bitrix24 handles the same logic through:

• Triggers - detect an event (stage change, field value change, incoming message)
• Robots - execute an action in response (assign task, send notification, change field, launch a business process)
• Business Processes (Workflow Designer) - for complex branching logic

There is no automated conversion tool. Each Digital Pipeline rule must be reviewed, understood, and rebuilt in Bitrix24 terms. Based on project data, a portfolio of around 40-41 automatic tasks, 20 field-change rules, and 15 deal-copy rules took approximately 30 hours to adapt.

See Bitrix24 Business Process Automation: Robots, Triggers and the Workflow Designer for a detailed breakdown of the toolset.

Salesbot → Bitrix24 Chatbot / Business Process

Kommo's Salesbot handles conversational routing, segmentation, and auto-messages within deal cards. In Bitrix24, equivalent logic is implemented via:

• Open Channel chatbots for inbound messaging automation
• Business Processes for segmentation and routing
• CRM Marketing for automated message sequences

Complex Salesbot scenarios (multi-condition segmentation, responsible-user assignment logic, auto-messaging) require full redesign. A set of 20 complex Salesbot scenarios is included in the 30-hour automation estimate above.

---

What Transfers, What Breaks: Field-Mapping Discipline

Field mapping is where most data quality issues originate - specifically, amoCRM's right-panel activity section does not export, and document template field IDs change on import, breaking all existing print forms.

What transfers cleanly (left-panel fields)

• Text, number, date, list (dropdown), checkbox fields
• Multi-pipeline stage configurations
• Contact and company record field values
• Deal amounts and currency fields
• Product catalogue items (via Excel)
• User-to-record assignments

What requires rework

• Document templates - field identifiers change when records are imported into Bitrix24, so every print form template must be reconfigured against the new field IDs. Effort: 2-6 hours depending on template count.
• Right-panel activity data - call logs, email correspondence threads, and certain note types stored in the Kommo activity feed are not accessible via standard export. Accept partial loss or plan a manual archive.
• Integration webhooks - because the server/portal URL changes, every third-party integration (telephony, WhatsApp connector, website forms, etc.) must be fully reconnected from scratch. Credentials and access tokens must be supplied by the client. Effort: approximately 8 hours for a typical stack of 4-5 integrations.
• Access rights - Kommo's permission model does not map 1:1 to Bitrix24. Rights must be manually replicated. Effort: approximately 2 hours.

---

Effort Ranges by Work Block

Based on real migration projects, the total effort for a mid-size Kommo-to-Bitrix24 migration ranges from roughly 20 to 60+ hours depending on automation complexity - data transfer itself is a small fraction of total effort.

Work blocks feed into each other during a migration.

The migration consists of four phases: Bitrix24 setup runs in parallel with data transfer; integration reconnection and automation rebuild happen after the test migration is confirmed; then cutover, training, and a support period follow.

flowchart TD
    A[Kommo / amoCRM audit\nField map + automation inventory] --> B[Deploy Bitrix24 trial portal]
    B --> C[API migration - initial run\n~5 working days]
    C --> D[Client review\n~10 days]
    D --> E{Go / No-go}
    E -->|Proceed| F[Upgrade portal to target plan]
    F --> G[Reconnect integrations\n~8 hrs]
    F --> H[Rebuild automations\n~30 hrs for complex set]
    F --> I[Reconfigure document templates\n2-6 hrs]
    G --> J[Cutover day: delta migration\nFreeze Kommo writes]
    H --> J
    I --> J
    J --> K[Team training]
    K --> L[Go-live + 1 month support]

Work block	Effort range
User accounts + access rights	~2 hours
Deal migration (fields + stages + records)	2-15 hours (volume-dependent)
Contact migration	2-4 hours
Company migration	2-4 hours
Product catalogue migration	2-4 hours
Document template reconfiguration	2-6 hours
Integration reconnection (per integration stack)	~8 hours
Automation rebuild (Robots / Business Processes)	10-30+ hours (complexity-dependent)
Training	varies by team size
Typical total (simple setup)	~20-30 hours
Typical total (complex automations)	50-70+ hours

For broader context on how effort scales across a full Bitrix24 implementation, see Bitrix24 Implementation Hours by Module: A Data Reference for Budgeting.

---

Pre-Migration Checklist

Complete this checklist before the API migration run starts - gaps discovered mid-migration add days of delay and may require re-running the full transfer.

Kommo / Kommo side

• Export a full list of active pipelines and their stages
• List all custom fields per entity type (lead, contact, company, deal) - note left-panel vs. right-panel
• Document all Digital Pipeline rules (trigger condition + actions)
• Document all Salesbot scenarios (decision trees, conditions, message templates)
• Export product catalogue to Excel
• Collect all document templates (Word/PDF source files)
• List all active integrations with credentials: telephony, WhatsApp connector, website/landing page forms, email accounts, any ERP/accounting connections
• Identify any custom API integrations built in-house

Bitrix24 side (pre-migration)

• Confirm target Bitrix24 plan (cloud or self-hosted) and user count
• Decide CRM mode: simple (no leads) or classic (leads + deals)
• Map Kommo pipelines to Bitrix24 funnels - confirm stage names
• Agree field naming convention for custom fields
• Identify which automations will be rebuilt vs. deprecated

Cutover day protocol

• Announce freeze date - no new records or edits in Kommo from the agreed time
• Run delta migration to capture changes since the initial pass
• Reconnect all integrations in Bitrix24
• Send user access credentials
• Confirm test calls, test messages, test deal creation before declaring go-live
• Keep Kommo in read-only access for at least 2 weeks post-cutover

---

Why Companies Moving from Kommo Choose Bitrix24

The primary reasons Kommo users migrate to Bitrix24 are per-portal pricing (not per-user), built-in telephony, native task and project management, and - for data-sensitive teams - the availability of a self-hosted edition.

Pricing model

Kommo charges per user per month. Bitrix24 cloud charges per portal (flat fee regardless of user count within the plan's included users), which reduces per-head cost as teams grow. Cloud plans are listed at bitrix24.com. For teams that require on-premise deployment, Bitrix24's self-hosted Business edition starts at $3,590/year including 50 users; Enterprise at $24,990/year covers 1,000+ users with multi-branch and cluster support - details at bitrix24.com/prices/self-hosted.php. The core argument for self-hosted is data residency and source-code access, not price - at smaller user counts cloud is often cheaper when you do the arithmetic.

Built-in capabilities not in Kommo

• Native VoIP telephony with call recording and AI call analysis
• Full task and project management with Gantt, Scrum boards, and workload planning - see Project Management in Bitrix24
• Internal intranet, document storage, and HR tools on the same portal
• Omnichannel contact center with SLA management
• Self-hosted / on-premise option for data residency requirements (relevant for UAE PDPL, Brazil LGPD, EU GDPR)

For a full feature comparison, see Bitrix24 vs HubSpot: An Honest Comparison for SMBs - many of the capability trade-offs apply equally to the Kommo comparison.

---

What Typically Goes Wrong (and How to Prevent It)

The most common failure modes in Kommo-to-Bitrix24 migrations are editing records in Kommo after the initial migration run, broken integrations on cutover day, and assuming automation rules will "just work" without a full rebuild.

Risk	Root cause	Prevention
Duplicate or out-of-date records	Team kept using Kommo after initial migration	Hard-freeze Kommo writes before delta run; communicate the cutover date clearly
Broken document templates	Field IDs change on import	Rebuild templates against new field IDs post-migration
Lost activity history	Right-panel data not exported by Kommo API	Accept partial loss; export what's available to a static archive file
Integration failures on day one	New portal URL invalidates all webhook URLs	Block time to reconnect all integrations on cutover day; collect credentials in advance
Automation gaps	Digital Pipeline logic assumed to transfer automatically	Inventory every rule before migration; schedule dedicated rebuild time
Scope creep from automation rebuild	Complexity underestimated	Audit automation count and complexity before signing off on a timeline

For a broader view of how migration timelines vary across CRM projects, see CRM Migration Timeline Benchmarks: What the Data from Real Bitrix24 Projects Shows.

---

Ready to move off amoCRM/Kommo? ACP Group INT is a Bitrix24 (Alaio) Gold Partner in Dubai - see Bitrix24 implementation in the UAE and Middle East, including data migration from your current CRM.