1С:CRM to MongoDB Integration

How Datrise loads 1С:CRM into MongoDB

Datrise syncs 1С:CRM's counterparties, deals, interactions, orders, tasks, and business processes into MongoDB as a collection per source entity. Flexible or custom fields land in native nested documents, and timestamps such as created, updated, and status changes are typed as BSON Date.

Sync is incremental: Datrise uses upserts by stable id with updateOne(upsert) on the source primary key, so re-runs update only what changed. Optional sharding on the entity id for large collections. Mongo has no fixed schema, so Datrise keeps field types consistent across documents to avoid mixed-type query surprises.

Ideal for document-oriented apps that want CRM data in their existing Mongo store.

Endpoints

1С:CRM: CRM built on the 1C platform for sales and back-office.

MongoDB: Document database for flexible schemas.

How 1С:CRM entities map to MongoDB

1С:CRM entity	MongoDB object	Notes
counterparties	`1c_crm_counterparties`	id PK · custom fields → native nested documents
deals	`1c_crm_deals`	id PK · linked to 1c_crm_counterparties
interactions	`1c_crm_interactions`	id PK · linked to 1c_crm_counterparties
orders	`1c_crm_orders`	id PK · linked to 1c_crm_counterparties

FAQ

How does Datrise handle 1С:CRM's custom fields in MongoDB?

Flexible values are stored as native nested documents, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MongoDB types.

How does the 1С:CRM to MongoDB sync stay up to date?

It runs incrementally — Datrise uses upserts by stable id with updateOne(upsert) on the source primary key.

Related pipelines

Early access

Connect 1С:CRM to MongoDB the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.