DatriseAI-first ETL

Salesforce Marketing Cloud MySQL

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

How Datrise loads Salesforce Marketing Cloud into MySQL

Datrise syncs Salesforce Marketing Cloud's records, events, and configuration objects 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

Salesforce Marketing Cloud: SaaS or API data source for analytics and warehouse sync.

MySQL: Widely used OSS relational engine (InnoDB).

How Salesforce Marketing Cloud entities map to MySQL

Salesforce Marketing Cloud entityMySQL objectNotes
recordssalesforce_marketing_cloud_recordsid PK · custom fields → JSON columns
eventssalesforce_marketing_cloud_eventsDATETIME/TIMESTAMP events
configuration objectssalesforce_marketing_cloud_configuration_objectsid PK · linked to salesforce_marketing_cloud_records

FAQ

How does Datrise handle Salesforce Marketing Cloud'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 Salesforce Marketing Cloud 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 Salesforce Marketing Cloud 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.