Salesforce Health Cloud to Azure Synapse Integration
AI-first ETL from Salesforce Health Cloud into Azure Synapse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce Health Cloud into Azure Synapse
Datrise syncs Salesforce Health Cloud's patients, care plans, care teams, clinical encounters, cases, and consents into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.
Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.
Ideal for Azure analytics estates feeding Power BI.
Endpoints
Salesforce Health Cloud: Patient and member relationship management on Salesforce.
Azure Synapse: Microsoft analytics workspace with SQL pools.
How Salesforce Health Cloud entities map to Azure Synapse
| Salesforce Health Cloud entity | Azure Synapse object | Notes |
|---|---|---|
| patients | salesforce_health_cloud_patients | id PK · custom fields → NVARCHAR(MAX) 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 Azure Synapse?
Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.
How does the Salesforce Health Cloud to Azure Synapse sync stay up to date?
It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.
Related pipelines
More destinations for Salesforce Health Cloud
- Salesforce Health Cloud → Spreadsheets
- Salesforce Health Cloud → Airtable
- Salesforce Health Cloud → CSV Files
- Salesforce Health Cloud → MongoDB
- Salesforce Health Cloud → Supabase
- Salesforce Health Cloud → Neon
- Salesforce Health Cloud → PlanetScale
- Salesforce Health Cloud → Amazon DynamoDB
- Salesforce Health Cloud → Looker
- Salesforce Health Cloud → Looker Studio
- Salesforce Health Cloud → Microsoft Power BI
- Salesforce Health Cloud → Tableau
More sources for Azure Synapse
- DealerSocket → Azure Synapse
- VinSolutions → Azure Synapse
- JobNimbus → Azure Synapse
- Buildertrend → Azure Synapse
- ServiceTitan → Azure Synapse
- Housecall Pro → Azure Synapse
- Jobber → Azure Synapse
- Mindbody → Azure Synapse
- Clio → Azure Synapse
- MyCase → Azure Synapse
- Allbound → Azure Synapse
- Impartner → Azure Synapse
Early access
Connect Salesforce Health Cloud to Azure Synapse 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.