Question 1

What Salesforce data can I load into ClickHouse?

Accepted Answer

Whatever the connected user can see, covering accounts, contacts, leads, opportunities, cases and campaigns plus your custom objects. Formula and rollup summary fields arrive as calculated values rather than definitions, so the logic does not need rebuilding downstream. Field level security applies, so anything hidden from the connected user simply will not appear in the table.

Question 2

Do I need to query with FINAL?

Accepted Answer

For accurate current state on a keyed table, usually yes, and this is the main thing to understand about ClickHouse as a CRM target. Updates are written as new versions of a row rather than modifying the existing one, and ReplacingMergeTree collapses them during background merges that happen on their own schedule. Until that merge runs, a plain SELECT can see more than one version. Querying with FINAL, or building views that do, gives you settled state without forcing merges by hand.

Question 3

How does Polytomic keep Salesforce current?

Accepted Answer

After the first full load, each run asks Salesforce only for records changed since the last successful run. Those are written out as Parquet, staged in your cloud storage, loaded into a temporary table, then inserted into the target where the version logic takes over. Salesforce does not broadcast schema changes, so new fields are found by polling rather than being pushed, and newly discovered columns are added with an ALTER TABLE.

Question 4

Are deleted Salesforce records reflected?

Accepted Answer

Yes, within Salesforce's own limits. Reads include archived and soft deleted records and expose the deletion flag, and Polytomic writes tombstone versions carrying a deleted at timestamp so removals become part of the version history rather than vanishing quietly. Hard delete runs a mutation afterwards to remove them for real. Records purged from the Recycle Bin are gone at source and need a full resync to reconcile.

Question 5

Why put CRM data in ClickHouse rather than a general warehouse?

Accepted Answer

Usually because ClickHouse is already there for something else. Teams commonly stand it up for event or product data and then want CRM records beside those events so a funnel can be built without crossing systems. ETL into a data warehouse makes that possible, and it is worth being honest that if CRM reporting is your only use case, a conventional warehouse is the more natural fit.

Sync Salesforce to ClickHouse

Sync Salesforce to ClickHouse with Polytomic

Custom objects included

Updates become versions

Stays inside your API budget

Or sync ClickHouse to Salesforce

Trusted by businesses worldwide

Step-by-step integration guide

Connect Salesforce in Polytomic

Connect ClickHouse in Polytomic

Create a sync between Salesforce and ClickHouse

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Salesforce with ClickHouse?