Salesforce Health Cloud to MySQL Integration

How Datrise loads Salesforce Health Cloud into MySQL

Datrise syncs Salesforce Health Cloud's patients, care plans, care teams, clinical encounters, cases, and consents 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 Health Cloud: Patient and member relationship management on Salesforce.

MySQL: Widely used OSS relational engine (InnoDB).

How Salesforce Health Cloud entities map to MySQL

Salesforce Health Cloud entity	MySQL object	Notes
patients	`salesforce_health_cloud_patients`	id PK · custom fields → JSON columns
care plans	`salesforce_health_cloud_care_plans`	id PK · linked to salesforce_health_cloud_patients
care teams	`salesforce_health_cloud_care_teams`	id PK · linked to salesforce_health_cloud_patients
clinical encounters	`salesforce_health_cloud_clinical_encounters`	id PK · linked to salesforce_health_cloud_patients

FAQ

How does Datrise handle Salesforce Health 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 Health 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 Health 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.