Salesforce Health Cloud → Google BigQuery
AI-first ETL from Salesforce Health Cloud into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce Health Cloud into Google BigQuery
Datrise syncs Salesforce Health Cloud's contacts, accounts, deals, activities, and lifecycle events into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
Salesforce Health Cloud: Healthcare CRM for accounts, compliance, and field engagement.
Google BigQuery: Serverless analytics warehouse on GCP.
How Salesforce Health Cloud entities map to Google BigQuery
| Salesforce Health Cloud entity | Google BigQuery object | Notes |
|---|---|---|
| contacts | salesforce_health_cloud_contacts | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| 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 | TIMESTAMP events |
FAQ
How does Datrise handle Salesforce Health Cloud's custom fields in Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the Salesforce Health Cloud to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for Salesforce Health Cloud
- Salesforce Health Cloud → Amazon Redshift
- Salesforce Health Cloud → Databricks SQL Warehouse
- Salesforce Health Cloud → ClickHouse
- Salesforce Health Cloud → DuckDB
- Salesforce Health Cloud → Amazon Athena
- Salesforce Health Cloud → Amazon S3 Data Lake
- Salesforce Health Cloud → Azure Data Lake Storage
- Salesforce Health Cloud → Azure Synapse
- Salesforce Health Cloud → Spreadsheets
- Salesforce Health Cloud → Airtable
- Salesforce Health Cloud → CSV Files
- Salesforce Health Cloud → MongoDB
More sources for Google BigQuery
- DealerSocket → Google BigQuery
- VinSolutions → Google BigQuery
- JobNimbus → Google BigQuery
- Buildertrend → Google BigQuery
- ServiceTitan → Google BigQuery
- Housecall Pro → Google BigQuery
- Jobber → Google BigQuery
- Mindbody → Google BigQuery
- Clio → Google BigQuery
- MyCase → Google BigQuery
- Allbound → Google BigQuery
- Impartner → Google BigQuery
Early access
Connect Salesforce Health Cloud to Google BigQuery 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.