1С:CRM → Azure Synapse
AI-first ETL from 1С:CRM into Azure Synapse. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into Azure Synapse
Datrise syncs 1С:CRM's contacts, accounts, deals, activities, and lifecycle events into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.
Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.
Ideal for Azure analytics estates feeding Power BI.
Endpoints
1С:CRM: CRM with strong adoption in CIS markets for sales and operations.
Azure Synapse: Microsoft analytics workspace with SQL pools.
How 1С:CRM entities map to Azure Synapse
| 1С:CRM entity | Azure Synapse object | Notes |
|---|---|---|
| contacts | 1c_crm_contacts | id PK · custom fields → NVARCHAR(MAX) JSON columns |
| 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 | datetime2 events |
FAQ
How does Datrise handle 1С:CRM's custom fields in Azure Synapse?
Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.
How does the 1С:CRM to Azure Synapse sync stay up to date?
It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.
Related pipelines
More destinations for 1С:CRM
More sources for Azure Synapse
Early access
Connect 1С:CRM to Azure Synapse 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.