Salesforce Health Cloud → Azure Data Lake Storage
AI-first ETL from Salesforce Health Cloud into Azure Data Lake Storage. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce Health Cloud into Azure Data Lake Storage
Datrise syncs Salesforce Health Cloud's contacts, accounts, deals, activities, and lifecycle events into Azure Data Lake Storage as partitioned Parquet in ADLS Gen2 per source entity. Flexible or custom fields land in nested struct/map fields in Parquet, and timestamps such as created, updated, and status changes are typed as ISO-8601 timestamp columns.
Sync is incremental: Datrise uses writes new date partitions to the container and compacts on a schedule, so re-runs update only what changed. Hive-style partitioning by load date, readable by Synapse and Databricks. ADLS hierarchical namespace makes folder layout matter, so Datrise keeps a predictable entity/date path your Azure engines mount directly.
Ideal for Azure lakehouse storage shared across Synapse and Databricks.
Endpoints
Salesforce Health Cloud: Healthcare CRM for accounts, compliance, and field engagement.
Azure Data Lake Storage: ADLS Gen2 object storage for analytics workloads.
How Salesforce Health Cloud entities map to Azure Data Lake Storage
| Salesforce Health Cloud entity | Azure Data Lake Storage object | Notes |
|---|---|---|
| contacts | salesforce_health_cloud_contacts | id PK · custom fields → nested struct/map fields in Parquet |
| accounts | salesforce_health_cloud_accounts | id PK · linked to salesforce_health_cloud_contacts |
| deals | salesforce_health_cloud_deals | id PK · linked to salesforce_health_cloud_contacts |
| activities | salesforce_health_cloud_activities | ISO-8601 timestamp columns events |
FAQ
How does Datrise handle Salesforce Health Cloud's custom fields in Azure Data Lake Storage?
Flexible values are stored as nested struct/map fields in Parquet, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Data Lake Storage types.
How does the Salesforce Health Cloud to Azure Data Lake Storage sync stay up to date?
It runs incrementally — Datrise uses writes new date partitions to the container and compacts on a schedule.
Related pipelines
More destinations for Salesforce Health Cloud
- Salesforce Health Cloud → Azure Synapse
- 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
More sources for Azure Data Lake Storage
- DealerSocket → Azure Data Lake Storage
- VinSolutions → Azure Data Lake Storage
- JobNimbus → Azure Data Lake Storage
- Buildertrend → Azure Data Lake Storage
- ServiceTitan → Azure Data Lake Storage
- Housecall Pro → Azure Data Lake Storage
- Jobber → Azure Data Lake Storage
- Mindbody → Azure Data Lake Storage
- Clio → Azure Data Lake Storage
- MyCase → Azure Data Lake Storage
- Allbound → Azure Data Lake Storage
- Impartner → Azure Data Lake Storage
Early access
Connect Salesforce Health Cloud to Azure Data Lake Storage 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.