DatriseAI-first ETL

Nutshell PlanetScale

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

How Datrise loads Nutshell into PlanetScale

Datrise syncs Nutshell's pipeline records, activity history, and conversion-focused sales metrics into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

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

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Nutshell entities map to PlanetScale

Nutshell entityPlanetScale objectNotes
pipeline recordsnutshell_pipeline_recordsid PK · custom fields → JSON columns
activity historynutshell_activity_historyDATETIME 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 PlanetScale?

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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