Salesforce Health Cloud to Neon Integration

How Datrise loads Salesforce Health Cloud into Neon

Datrise syncs Salesforce Health Cloud's patients, care plans, care teams, clinical encounters, cases, and consents into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

Salesforce Health Cloud: Patient and member relationship management on Salesforce.

Neon: Serverless Postgres destination with branching and autoscaling.

How Salesforce Health Cloud entities map to Neon

Salesforce Health Cloud entity	Neon object	Notes
patients	`salesforce_health_cloud_patients`	id PK · custom fields → jsonb 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 Neon?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

How does the Salesforce Health Cloud to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Salesforce Health Cloud to Neon 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.