1C integration and custom solutions

1C and CRM Integration

A 1C–CRM integration connects sales and accounting: the CRM manages leads and communication, while 1C manages…

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

A 1C–CRM integration connects sales and accounting: the CRM manages leads and communication, while 1C manages contracts, invoices, and fulfilment. The two systems should not compete for the same customer record.

Scope covers entity mapping, duplicate keys, status ownership, CRM webhooks, 1C APIs, transformation, queues, and sync logs. Full sales-pipeline configuration or CRM migration is separate. Acceptance ensures one account per repeated deal event, permitted status flow, visible conflicts, and externalId on both sides.

Acceptance criteria

Done when

  • Agreed entities sync with externalId and no duplicates on retry
  • Exchange journal shows object, result, and attempt
  • Failure paths are visible to operators

Deliverables

  • API/contract notes + mapping table
  • Staging exchange runbook

Out of scope

  • 1C accounting-policy changes
  • Production 1C upgrades without change windows

Assumptions

  • Test infobase and a 1C contact for metadata

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Ballpark estimate

Scope size
Extras

FAQ

Tap a question to expand the answer.

How are duplicate customers merged?

Using agreed stable attributes such as tax ID, phone, email, and external ID with priorities. Ambiguous records should not be merged automatically.

Can every field be synchronised?

Technically yes, but a smaller shared contract is usually easier to maintain as the CRM and 1C configuration evolve.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

View full service page