Two-Way Sync Between 1C:CRM and Bitrix24 via REST API

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

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.

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

1. Audit of current 1C and Bitrix24 configuration (versions, permissions, load)
2. Agreement on the exchange scheme and assignment of a source of truth for each entity
3. Development of REST handlers in 1C and webhooks in Bitrix24
4. Testing on live data—checking 100+ deals and contacts
5. Documentation on the exchange (entities, mapping, conflict logic)
6. Training for responsible employees (3–5 people, 1–2 hours)
7. Post-release support: 30 days of stable operation guarantee

Comparison of REST API and CommerceML

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.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.