DatriseAI-first ETL

Nutshell CSV Files

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

How Datrise loads Nutshell into CSV Files

Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics into CSV Files as one CSV per source entity. Flexible or custom fields land in JSON-encoded strings for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 timestamp columns.

Sync is incremental: Datrise uses writes a fresh, fully-typed CSV per entity each run, so re-runs update only what changed. Optional date-suffixed files for change tracking. CSV has no types, so Datrise emits a companion schema and quotes/escapes consistently so downstream loaders don't misparse commas and newlines.

Ideal for portable hand-off into any tool that ingests delimited files.

Endpoints

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

CSV Files: Flat-file destination for exports and lightweight data sharing.

How Nutshell entities map to CSV Files

Nutshell entityCSV Files objectNotes
pipeline recordsnutshell_pipeline_recordsid PK · custom fields → JSON-encoded strings for nested fields
activity historynutshell_activity_historyISO-8601 timestamp columns 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 CSV Files?

Flexible values are stored as JSON-encoded strings for nested fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native CSV Files types.

How does the Nutshell to CSV Files sync stay up to date?

It runs incrementally — Datrise uses writes a fresh, fully-typed CSV per entity each run.

Related pipelines

Early access

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