When a company has two CRMs simultaneously—1C:CRM and Bitrix24—does the sales department enter contacts in one system while accounting creates invoices in the other?
Without integration, managers waste up to 3 hours a day manually transferring data, and discrepancies in deal statuses lead to missed shipments. Integration eliminates this, but there is no standard protocol between them. We set up exchange via REST API and HTTP services, define a source of truth, and implement bidirectional synchronization of key entities. Turnkey, with documentation and training. Our team has 7+ years in Bitrix24 and 1C integrations, with over 30 synchronization projects. We guarantee stable exchange even under peak loads. Typical scenario: a manager creates a deal in Bitrix24, and an accountant issues an invoice in 1C—data flows automatically, without errors or delays. For example, on one project we synchronized 50,000 contacts and 10,000 deals without a single duplicate, saving the client about 200,000 RUB per year on manual entry.
How is typical exchange between 1C:CRM and Bitrix24 structured?
Most often, companies come to this integration where:
- Sales and customer communication are conducted in Bitrix24 (convenient interface, telephony, email)
- Accounting, invoicing, and document flow are in 1C (including 1C:CRM as an add-on over 1C:Trade Management or ERP)
In this case, the 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 | Transfer upon qualification |
| Deals | B24 → 1C | At a specific pipeline status |
| Invoices | 1C → B24 | Linked to B24 deal |
| Deal statuses | 1C → B24 | When status changes in 1C |
Why CommerceML is not suitable for 1C:CRM?
CommerceML is an XML protocol for exchange with 1C:Trade Management, but it is not adapted for CRM entities: deals, pipeline stages, statuses. A real case: when trying to transfer deals via CommerceML, links to contacts and change history were lost. The REST API of Bitrix24 (crm.deal.*, crm.contact.*) gives full control over fields, events, and access rights. Result: REST API processes data arrays 3 times faster and does not require XML-to-JSON conversion.
More about CommerceML
CommerceML is designed for batch exchange of goods and orders but does not support CRM entities. For 1C:CRM (an add-on over Trade Management/ERP), the standard exchange does not transmit deals, pipeline statuses, or custom fields. REST API solves these limitations.How do we synchronize counterparties without duplicates?
Counterparties in 1C:CRM → Companies/Contacts in Bitrix24. The matching key is TIN (for legal entities) or email (for individuals). When a contact is created in Bitrix24 (via a website form or manually by a manager), the OnCrmContactAdd event triggers a webhook that sends data to 1C:CRM. In 1C, a counterparty is created, and its ID is written back to the Bitrix24 contact's custom field (UF_CRM_1C_ID). For individuals without a TIN, we use email + phone as a composite key. This approach eliminates duplicates even with active input in both systems.
Transferring a deal from Bitrix24 to 1C
When a certain pipeline stage is reached in Bitrix24 (e.g., "Contract signed")—a business process or automation sends the 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 line items (products), amount, counterparty data, responsible manager.
Invoices from 1C to Bitrix24
When an invoice is issued in 1C:CRM, a handler sends the invoice data to Bitrix24 via crm.invoice.add (or smart processes, if using the new CRM). The manager in Bitrix24 sees the invoice linked to the deal and can send it to the client.
Source of truth logic
For bidirectional exchange, we definitely determine which system's data is more current:
- Client phone and email—source of truth is Bitrix24 (managers update there)
- Requisites (TIN, KPP, address)—source of truth is 1C:CRM (accounting verifies)
In case of conflict, the "source of truth" takes priority; the second system receives data without the ability to overwrite it.
Peculiarities of 1C:CRM
1C:CRM is not a standalone program, but an extension for 1C:Trade Management, 1C:Complex Automation, 1C:ERP. The availability of HTTP services, their parameters, and capabilities depend on the configuration version. Before starting integration, we clarify the version and availability of required methods with the 1C developers.
What's included in the exchange setup
- Audit of current 1C and Bitrix24 configuration (versions, permissions, load)
- Agreement on the exchange scheme and assignment of a source of truth for each entity
- Development of REST handlers in 1C and webhooks in Bitrix24
- Testing on live data—checking 100+ deals and contacts
- Documentation on the exchange (entities, mapping, conflict logic)
- Training for responsible employees (3–5 people, 1–2 hours)
- Post-release support: 30 days of stable operation guarantee
Comparison of REST API and CommerceML
| Parameter | REST API | CommerceML (limited) |
|---|---|---|
| Exchange type | Real-time / scheduled | Batch / once a day |
| Deal support | Full | None |
| Error handling | Retries + logs | Fatal block error |
| Custom field flexibility | Any custom fields | Only standard fields |
Contact us for an evaluation of your project—get a proposal within 1-2 days. We use proven certified solutions and guarantee stable exchange even under peak load. Request a consultation now.