DatriseAI-first ETL

CommCare to PlanetScale Integration

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

How Datrise loads CommCare into PlanetScale

Datrise syncs CommCare's cases, forms, form submissions, users, locations, and case properties 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

CommCare: Mobile data collection for field programs.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How CommCare entities map to PlanetScale

CommCare entityPlanetScale objectNotes
casescommcare_casesid PK · custom fields → JSON columns
formscommcare_formsid PK · linked to commcare_cases
form submissionscommcare_form_submissionsid PK · linked to commcare_cases
userscommcare_usersid PK · linked to commcare_cases

FAQ

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