1С:CRM to Domo Integration
AI-first ETL from 1С:CRM into Domo. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into Domo
Datrise syncs 1С:CRM's counterparties, deals, interactions, orders, tasks, and business processes into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.
Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.
Ideal for all-in-one cloud BI with built-in ETL.
Endpoints
1С:CRM: CRM built on the 1C platform for sales and back-office.
Domo: Cloud BI platform combining data integration and executive dashboards.
How 1С:CRM entities map to Domo
| 1С:CRM entity | Domo object | Notes |
|---|---|---|
| counterparties | 1c_crm_counterparties | id PK · custom fields → flattened columns for Magic ETL |
| 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 Domo?
Flexible values are stored as flattened columns for Magic ETL, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Domo types.
How does the 1С:CRM to Domo sync stay up to date?
It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.
Related pipelines
More destinations for 1С:CRM
Early access
Connect 1С:CRM to Domo 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.