Front to PlanetScale Integration

How Datrise loads Front into PlanetScale

Datrise syncs Front's conversations, messages, contacts, inboxes, tags, and teammates 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

Front: Shared inbox for team email and messaging.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Front entities map to PlanetScale

Front entity	PlanetScale object	Notes
conversations	`frontapp_conversations`	id PK · custom fields → JSON columns
messages	`frontapp_messages`	id PK · linked to frontapp_conversations
contacts	`frontapp_contacts`	id PK · linked to frontapp_conversations
inboxes	`frontapp_inboxes`	id PK · linked to frontapp_conversations

FAQ

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