DatriseAI-first ETL

Bigin by Zoho PlanetScale

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

How Datrise loads Bigin by Zoho into PlanetScale

Datrise syncs Bigin by Zoho's SMB leads, contacts, deals, and day-to-day activity tracking 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

Bigin by Zoho: SMB CRM source for leads, deals, and activity tracking.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Bigin by Zoho entities map to PlanetScale

Bigin by Zoho entityPlanetScale objectNotes
SMB leadsbigin_by_zoho_smb_leadsid PK · custom fields → JSON columns
contactsbigin_by_zoho_contactsid PK · linked to bigin_by_zoho_smb_leads
dealsbigin_by_zoho_dealsid PK · linked to bigin_by_zoho_smb_leads
day-to-day activity trackingbigin_by_zoho_day_to_day_activity_trackingDATETIME events

FAQ

How does Datrise handle Bigin by Zoho'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 Bigin by Zoho 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 Bigin by Zoho 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.