SUMA CRM → GoodData
AI-first ETL from SUMA CRM into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads SUMA CRM into GoodData
Datrise syncs SUMA CRM's contacts, accounts, deals, activities, and lifecycle events 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
SUMA CRM: European CRM for SMB and mid-market sales teams.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How SUMA CRM entities map to GoodData
| SUMA CRM entity | GoodData object | Notes |
|---|---|---|
| contacts | sumacrm_contacts | id PK · custom fields → flattened columns |
| accounts | sumacrm_accounts | id PK · linked to sumacrm_contacts |
| deals | sumacrm_deals | id PK · linked to sumacrm_contacts |
| activities | sumacrm_activities | date dimensions events |
FAQ
How does Datrise handle SUMA 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 SUMA CRM to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for SUMA CRM
Early access
Connect SUMA 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.