DatriseAI-first ETL

Dolibarr PlanetScale

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

How Datrise loads Dolibarr into PlanetScale

Datrise syncs Dolibarr's contacts, accounts, deals, activities, and lifecycle events 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

Dolibarr: Open-source CRM for customizable sales and customer workflows.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Dolibarr entities map to PlanetScale

Dolibarr entityPlanetScale objectNotes
contactsdolibarr_contactsid PK · custom fields → JSON columns
accountsdolibarr_accountsid PK · linked to dolibarr_contacts
dealsdolibarr_dealsid PK · linked to dolibarr_contacts
activitiesdolibarr_activitiesDATETIME events

FAQ

How does Datrise handle Dolibarr'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 Dolibarr 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 Dolibarr 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.