Setting up contact exchange between Bitrix24 and 1C

Configuring Contact Exchange between Bitrix24 and 1C

Contacts in Bitrix24 CRM and counterparties/individuals in 1C are the same customer base split between two systems. Exchange eliminates duplication: a new client entered in one system automatically appears in the other.

What is synchronized

Contacts (individuals): Bitrix24 crm.contact ↔ 1C "Individual" or "Individual counterparty".

Companies: Bitrix24 crm.company ↔ 1C "Organization counterparty".

Fields for mapping:

Direction of synchronization

Option 1: Bitrix24 as main system. Managers work in Bitrix24. When creating a contact — it goes to 1C for accounting operations.

Option 2: 1C as main system. Customer base is maintained in 1C (accounting, contracts). Goes to Bitrix24 for manager work.

Option 3: bidirectional. Both directions with certain priority rules.

Implementation: Bitrix24 → 1C

When a contact is created in Bitrix24, an outgoing webhook triggers. Bitrix24 sends POST to the registered URL with event data.

Webhook handler (PHP script):

1. Receives data[FIELDS][ID] — contact ID
2. Calls crm.contact.get to get full data
3. Sends HTTP request to 1C HTTP service with JSON contact data
4. 1C creates counterparty, returns ID
5. Handler records 1C ID in contact's user field in Bitrix24 UF_CRM_1C_CONTACT_ID via crm.contact.update

Implementation: 1C → Bitrix24

In 1C, a handler is created (subscription to OnCounterpartySave event). When saving a new or modified counterparty:

// 1C pseudocode
Request = New HTTPRequest;
Request.SetBodyFromString(DataJSON);
Connection = New HTTPConnection("portal.bitrix24.ru");
Response = Connection.SendForProcessing(Request, "/rest/.../crm.contact.add");

The response contains the ID of the new contact in Bitrix24 — save it in 1C counterparty property for future identification.

Deduplication

The main problem of bidirectional exchange is duplicates. One client might be created in both systems independently. Duplicate prevention algorithm:

1. When receiving a new contact, check if a record with such email/phone exists in the other system.
2. If yes — update the existing one, don't create a new one.
3. If no — create and record mutual IDs.

For searching in Bitrix24: crm.duplicate.findbycomm — method for finding duplicates by phone and email.

Batch initial synchronization

When starting integration, need to synchronize existing databases. Order:

1. Export all contacts from Bitrix24 via crm.contact.list (pagination by 50 records).
2. For each, search for match in 1C by email.
3. Matched ones — update mutual IDs, don't duplicate.
4. Unmatched ones — create in 1C.
5. Contacts that exist in 1C but not in Bitrix24 — create in Bitrix24.

This is a one-time operation performed once before starting bidirectional exchange.

Common challenges

• Different phone formats. Bitrix24 stores phones as +7 (XXX) XXX-XX-XX, 1C in free format. Normalize before comparison.
• Multiple phones per contact. In Bitrix24 this is a multiple field, in 1C can be one field. Take first phone as primary.
• Responsible manager. Bitrix24 users and 1C users are different entities. Need a mapping table.