DatriseAI-first ETL

Nutshell Sisense

AI-first ETL from Nutshell into Sisense. Governed entities, incremental sync, typed landing tables.

How Datrise loads Nutshell into Sisense

Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

Nutshell: Sales CRM for teams that need simple reporting and pipeline velocity.

Sisense: Analytics platform with elastic data models and embedded analytics.

How Nutshell entities map to Sisense

Nutshell entitySisense objectNotes
pipeline recordsnutshell_pipeline_recordsid PK · custom fields → flattened columns for the cube
activity historynutshell_activity_historydate/time fields events
conversion-focused sales metricsnutshell_conversion_focused_sales_metricsid PK · linked to nutshell_pipeline_records

FAQ

How does Datrise handle Nutshell's custom fields in Sisense?

Flexible values are stored as flattened columns for the cube, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Sisense types.

How does the Nutshell to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect Nutshell to Sisense 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.