1С:CRM to MySQL Integration
AI-first ETL from 1С:CRM into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into MySQL
Datrise syncs 1С:CRM's counterparties, deals, interactions, orders, tasks, and business processes into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.
Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.
Ideal for operational reporting and app databases already standardized on MySQL.
Endpoints
1С:CRM: CRM built on the 1C platform for sales and back-office.
MySQL: Widely used OSS relational engine (InnoDB).
How 1С:CRM entities map to MySQL
| 1С:CRM entity | MySQL object | Notes |
|---|---|---|
| counterparties | 1c_crm_counterparties | id PK · custom fields → JSON columns |
| 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 MySQL?
Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.
How does the 1С:CRM to MySQL sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.
Related pipelines
More destinations for 1С:CRM
Early access
Connect 1С:CRM to MySQL 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.