Salesforce Commerce Cloud to ClickHouse Integration
AI-first ETL from Salesforce Commerce Cloud into ClickHouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce Commerce Cloud into ClickHouse
Datrise syncs Salesforce Commerce Cloud's orders, products, customers, baskets, promotions, and inventory records into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.
Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.
Ideal for high-volume event analytics that need sub-second aggregation.
Endpoints
Salesforce Commerce Cloud: Salesforce storefront, catalog, and order management.
ClickHouse: Columnar OLAP engine for fast aggregations.
How Salesforce Commerce Cloud entities map to ClickHouse
| Salesforce Commerce Cloud entity | ClickHouse object | Notes |
|---|---|---|
| orders | salesforce_commerce_cloud_orders | id PK · custom fields → JSON or Map columns |
| products | salesforce_commerce_cloud_products | id PK · linked to salesforce_commerce_cloud_orders |
| customers | salesforce_commerce_cloud_customers | id PK · linked to salesforce_commerce_cloud_orders |
| baskets | salesforce_commerce_cloud_baskets | id PK · linked to salesforce_commerce_cloud_orders |
FAQ
How does Datrise handle Salesforce Commerce Cloud's custom fields in ClickHouse?
Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.
How does the Salesforce Commerce Cloud to ClickHouse sync stay up to date?
It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.
Related pipelines
More destinations for Salesforce Commerce Cloud
- Salesforce Commerce Cloud → DuckDB
- Salesforce Commerce Cloud → Amazon Athena
- Salesforce Commerce Cloud → Amazon S3 Data Lake
- Salesforce Commerce Cloud → Azure Data Lake Storage
- Salesforce Commerce Cloud → Azure Synapse
- Salesforce Commerce Cloud → Spreadsheets
- Salesforce Commerce Cloud → Airtable
- Salesforce Commerce Cloud → CSV Files
- Salesforce Commerce Cloud → MongoDB
- Salesforce Commerce Cloud → Supabase
- Salesforce Commerce Cloud → Neon
- Salesforce Commerce Cloud → PlanetScale
More sources for ClickHouse
Early access
Connect Salesforce Commerce Cloud to ClickHouse 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.