1С:CRM to GoodData Integration
AI-first ETL from 1С:CRM into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into GoodData
Datrise syncs 1С:CRM's counterparties, deals, interactions, orders, tasks, and business processes into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
1С:CRM: CRM built on the 1C platform for sales and back-office.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How 1С:CRM entities map to GoodData
| 1С:CRM entity | GoodData object | Notes |
|---|---|---|
| counterparties | 1c_crm_counterparties | id PK · custom fields → flattened 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 GoodData?
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 GoodData types.
How does the 1С:CRM to GoodData 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 GoodData 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.