DatriseAI-first ETL

Twenty CRM MySQL

AI-first ETL from Twenty CRM into MySQL. Governed entities, incremental sync, typed landing tables.

How Datrise loads Twenty CRM into MySQL

Datrise syncs Twenty CRM's contacts, accounts, deals, activities, and lifecycle events into MySQL 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/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Twenty CRM: Open-source CRM for customizable sales and customer workflows.

MySQL: Widely used OSS relational engine (InnoDB).

How Twenty CRM entities map to MySQL

Twenty CRM entityMySQL objectNotes
contactstwenty_contactsid PK · custom fields → JSON columns
accountstwenty_accountsid PK · linked to twenty_contacts
dealstwenty_dealsid PK · linked to twenty_contacts
activitiestwenty_activitiesDATETIME/TIMESTAMP events

FAQ

How does Datrise handle Twenty CRM's custom fields in MySQL?

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 MySQL types.

How does the Twenty CRM to MySQL 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 Twenty CRM to MySQL 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.