DatriseAI-first ETL

Salesloft MySQL

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

How Datrise loads Salesloft into MySQL

Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution 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

Salesloft: Revenue workflow platform for cadences, conversations, and coaching signals.

MySQL: Widely used OSS relational engine (InnoDB).

How Salesloft entities map to MySQL

Salesloft entityMySQL objectNotes
cadence activitysalesloft_cadence_activityDATETIME/TIMESTAMP events
conversation signalssalesloft_conversation_signalsid PK · linked to salesloft_cadence_activity
revenue workflow executionsalesloft_revenue_workflow_executionid PK · linked to salesloft_cadence_activity

FAQ

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