Nutshell → GoodData
AI-first ETL from Nutshell into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Nutshell into GoodData
Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics 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
Nutshell: Sales CRM for teams that need simple reporting and pipeline velocity.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Nutshell entities map to GoodData
| Nutshell entity | GoodData object | Notes |
|---|---|---|
| pipeline records | nutshell_pipeline_records | id PK · custom fields → flattened columns |
| activity history | nutshell_activity_history | date dimensions events |
| conversion-focused sales metrics | nutshell_conversion_focused_sales_metrics | id PK · linked to nutshell_pipeline_records |
FAQ
How does Datrise handle Nutshell'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 Nutshell to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Nutshell
Early access
Connect Nutshell 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.