DatriseAI-first ETL

Salesforce GoodData

AI-first ETL from Salesforce into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Salesforce into GoodData

Datrise syncs Salesforce's accounts, opportunities, contacts, tasks, and pipeline stage history 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

Salesforce: Enterprise CRM and Customer 360 platform.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Salesforce entities map to GoodData

Salesforce entityGoodData objectNotes
accountssalesforce_accountsid PK · custom fields → flattened columns
opportunitiessalesforce_opportunitiesid PK · linked to salesforce_accounts
contactssalesforce_contactsid PK · linked to salesforce_accounts
taskssalesforce_tasksid PK · linked to salesforce_accounts

FAQ

How does Datrise handle Salesforce'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 Salesforce to GoodData sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Salesforce 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.