DatriseAI-first ETL

Nectar CRM GoodData

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

How Datrise loads Nectar CRM into GoodData

Datrise syncs Nectar 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

Nectar CRM: CRM widely used in Latin America for sales pipeline and customer ops.

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

How Nectar CRM entities map to GoodData

Nectar CRM entityGoodData objectNotes
contactsnectar_crm_contactsid PK · custom fields → flattened columns
accountsnectar_crm_accountsid PK · linked to nectar_crm_contacts
dealsnectar_crm_dealsid PK · linked to nectar_crm_contacts
activitiesnectar_crm_activitiesdate dimensions events

FAQ

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

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

Related pipelines

Early access

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