1С:CRM → Yellowfin
AI-first ETL from 1С:CRM into Yellowfin. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into Yellowfin
Datrise syncs 1С:CRM's contacts, accounts, deals, activities, and lifecycle events into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.
Ideal for dashboards with automated data storytelling.
Endpoints
1С:CRM: CRM with strong adoption in CIS markets for sales and operations.
Yellowfin: BI suite with dashboards, automated insights, and data storytelling.
How 1С:CRM entities map to Yellowfin
| 1С:CRM entity | Yellowfin object | Notes |
|---|---|---|
| contacts | 1c_crm_contacts | id PK · custom fields → flattened 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 | date/time dimensions events |
FAQ
How does Datrise handle 1С:CRM's custom fields in Yellowfin?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Yellowfin types.
How does the 1С:CRM to Yellowfin sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for 1С:CRM
Early access
Connect 1С:CRM to Yellowfin 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.