1С:CRM → MongoDB
AI-first ETL from 1С:CRM into MongoDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into MongoDB
Datrise syncs 1С:CRM's contacts, accounts, deals, activities, and lifecycle events 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 with strong adoption in CIS markets for sales and operations.
MongoDB: Document database for flexible schemas.
How 1С:CRM entities map to MongoDB
| 1С:CRM entity | MongoDB object | Notes |
|---|---|---|
| contacts | 1c_crm_contacts | id PK · custom fields → native nested documents |
| accounts | 1c_crm_accounts | id PK · linked to 1c_crm_contacts |
| deals | 1c_crm_deals | id PK · linked to 1c_crm_contacts |
| activities | 1c_crm_activities | BSON Date events |
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
More destinations for 1С:CRM
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.