DatriseAI-first ETL

Salesflare MySQL

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

How Datrise loads Salesflare into MySQL

Datrise syncs Salesflare's B2B account intelligence, interactions, and automated relationship timelines 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

Salesflare: B2B CRM focused on automation and relationship timeline data.

MySQL: Widely used OSS relational engine (InnoDB).

How Salesflare entities map to MySQL

Salesflare entityMySQL objectNotes
B2B account intelligencesalesflare_b2b_account_intelligenceid PK · custom fields → JSON columns
interactionssalesflare_interactionsid PK · linked to salesflare_b2b_account_intelligence
automated relationship timelinessalesflare_automated_relationship_timelinesDATETIME/TIMESTAMP events

FAQ

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