DatriseAI-first ETL

Freshsales MySQL

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

How Datrise loads Freshsales into MySQL

Datrise syncs Freshsales's leads, contacts, deals, calls, and email activity telemetry 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

Freshsales: CRM by Freshworks with built-in phone and email.

MySQL: Widely used OSS relational engine (InnoDB).

How Freshsales entities map to MySQL

Freshsales entityMySQL objectNotes
leadsfreshsales_leadsid PK · custom fields → JSON columns
contactsfreshsales_contactsid PK · linked to freshsales_leads
dealsfreshsales_dealsid PK · linked to freshsales_leads
callsfreshsales_callsid PK · linked to freshsales_leads

FAQ

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