Configuring 1C:CRM and Bitrix24 Exchange
1C:CRM and Bitrix24 are two CRM systems sometimes used simultaneously within one company. Exchange between them allows synchronizing the customer base, deals, and documents without duplicating data entry.
Typical usage pattern
Companies often turn to such integration when:
- Sales and customer communication are conducted in Bitrix24 (convenient interface, telephony, email)
- Accounting, invoicing, and document workflow are in 1C (including 1C:CRM as an extension of 1C:UT or ERP)
In this case, exchange direction is: Bitrix24 → 1C:CRM (deals and contacts for further processing) and 1C:CRM → Bitrix24 (deal statuses, invoices).
What is synchronized
| Entity | Direction | Details |
|---|---|---|
| Contacts/Counterparties | Bidirectional | Individuals and companies |
| Leads | B24 → 1C | Transmission on qualification |
| Deals | B24 → 1C | At a certain pipeline stage |
| Invoices | 1C → B24 | Attachment to B24 deal |
| Deal statuses | 1C → B24 | On status change in 1C |
Integration mechanism
There is no standard exchange protocol between 1C:CRM and Bitrix24. Implemented via:
-
Bitrix24 REST API (methods
crm.deal.*,crm.contact.*,crm.company.*) - HTTP services or Web services of 1C:CRM — for receiving data from Bitrix24
- Bitrix24 webhooks — for sending events to 1C when deal status changes
Counterparty synchronization
Counterparties in 1C:CRM → Companies/Contacts in Bitrix24. Matching key — TIN (for legal entities) or email (for individuals).
When a counterparty is created in Bitrix24 (via website form or manually by manager) — the OnCrmContactAdd event triggers a webhook that sends data to 1C:CRM. A counterparty is created in 1C, its ID is written back to the contact's user field in Bitrix24 (UF_CRM_1C_ID).
Transmitting deal from Bitrix24 to 1C
When a certain pipeline stage is reached in Bitrix24 (e.g., "Contract signed") — a business process or automation sends deal data to 1C:CRM:
POST /rest/{userId}/{token}/crm.deal.get → deal data
→ HTTP POST to 1C HTTP service with JSON
→ In 1C, a Customer Order / CRM Deal is created
We transmit: deal composition (products), amount, counterparty data, responsible manager.
Invoices from 1C to Bitrix24
When an invoice is issued in 1C:CRM — the handler sends invoice data to Bitrix24 via crm.invoice.add (or smart processes if new CRM is used). The manager in Bitrix24 sees the invoice attached to the deal and can send it to the client.
"Source of truth" logic
In bidirectional exchange, always define which system has more current data:
- Customer phone and email — source of truth is Bitrix24 (managers update there)
- Details (TIN, KPP, address) — source of truth is 1C:CRM (accounting verifies)
On conflict — priority goes to the "source of truth," the second system receives data without ability to overwrite.
1C:CRM specifics
1C:CRM is not a standalone program but an extension for 1C:UT, 1C:CA, 1C:ERP. Availability of HTTP services, their parameters and capabilities — depend on configuration version. Before starting integration, clarify version and availability of needed methods with 1C developers.