EspoCRM → PlanetScale
AI-first ETL from EspoCRM into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads EspoCRM into PlanetScale
Datrise syncs EspoCRM's pipeline entities, custom objects, and process automation 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
EspoCRM: Open-source CRM for pipeline management and custom entity modeling.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How EspoCRM entities map to PlanetScale
| EspoCRM entity | PlanetScale object | Notes |
|---|---|---|
| pipeline entities | espocrm_pipeline_entities | id PK · custom fields → JSON columns |
| custom objects | espocrm_custom_objects | id PK · linked to espocrm_pipeline_entities |
| process automation events | espocrm_process_automation_events | DATETIME events |
FAQ
How does Datrise handle EspoCRM'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 EspoCRM 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
More destinations for EspoCRM
Early access
Connect EspoCRM 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.