DatriseAI-first ETL

Crelate to PlanetScale Integration

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

How Datrise loads Crelate into PlanetScale

Datrise syncs Crelate's contacts, jobs, opportunities, activities, workflow stages, and placements 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

Crelate: Recruiting CRM for agency pipelines and candidate sourcing.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Crelate entities map to PlanetScale

Crelate entityPlanetScale objectNotes
contactscrelate_contactsid PK · custom fields → JSON columns
jobscrelate_jobsid PK · linked to crelate_contacts
opportunitiescrelate_opportunitiesid PK · linked to crelate_contacts
activitiescrelate_activitiesDATETIME events

FAQ

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