Vtiger → PlanetScale
AI-first ETL from Vtiger into PlanetScale. Governed entities, incremental sync, typed landing tables.
How Datrise loads Vtiger into PlanetScale
Datrise syncs Vtiger's sales, support, and lifecycle workflows in a unified CRM model 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
Vtiger: Unified CRM for sales, help desk, and customer lifecycle workflows.
PlanetScale: Serverless MySQL platform with safe schema workflows.
How Vtiger entities map to PlanetScale
| Vtiger entity | PlanetScale object | Notes |
|---|---|---|
| sales | vtiger_sales | id PK · custom fields → JSON columns |
| support | vtiger_support | id PK · linked to vtiger_sales |
| lifecycle workflows in a unified CRM model | vtiger_lifecycle_workflows_in_a_unified_crm_model | id PK · linked to vtiger_sales |
FAQ
How does Datrise handle Vtiger'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 Vtiger 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 Vtiger
Early access
Connect Vtiger 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.