folk → MySQL
AI-first ETL from folk into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads folk into MySQL
Datrise syncs folk'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
folk: AI-native CRM for relationship data, enrichment, and workflow automation.
MySQL: Widely used OSS relational engine (InnoDB).
How folk entities map to MySQL
| folk entity | MySQL object | Notes |
|---|---|---|
| contacts | folk_contacts | id PK · custom fields → JSON columns |
| accounts | folk_accounts | id PK · linked to folk_contacts |
| deals | folk_deals | id PK · linked to folk_contacts |
| activities | folk_activities | DATETIME/TIMESTAMP events |
FAQ
How does Datrise handle folk'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 folk 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
More destinations for folk
Early access
Connect folk 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.