Question 1

What can Polytomic pull from Salesforce into Snowflake?

Accepted Answer

Every object visible to the connected user, standard and custom, with standard and custom fields, plus optional Tooling API metadata objects. In practice most teams start with Account, Contact, Opportunity, Lead and User, then add the history objects like OpportunityHistory and AccountHistory, which is where pipeline movement actually lives. Formula and rollup fields are materialized as columns, so a score computed in Salesforce is queryable without rebuilding the formula in SQL.

Question 2

How do incremental reads work?

Accepted Answer

Reads are tracking field based, normally on LastModifiedDate, with a ten minute lookback so records that settle late are not skipped. Full loads prefer the Salesforce Bulk export path, while incremental loads prefer REST and SOQL and fall back to Bulk or Composite when needed. One caveat worth planning around: formula and rollup recalculations do not always bump LastModifiedDate, so if you depend on those staying current, schedule a periodic full run rather than relying on incremental alone.

Question 3

Are deleted Salesforce records reflected in the data warehouse?

Accepted Answer

Yes, within the limits Salesforce imposes. Reads use queryAll, which includes soft deleted and archived records, and the IsDeleted flag is exposed as a column so you can filter or count them. Records that have been purged from the Recycle Bin are gone from Salesforce entirely and cannot be emitted afterwards, so a long gap between runs on a heavily purged org is the one case where reconciliation needs a full resync. Scheduling a periodic full ETL run alongside the incremental ones is the usual guard against that.

Question 4

Will a large sync exhaust our Salesforce API quota?

Accepted Answer

Read volume shares the same daily allowance as everything else in your org, so it is guarded. Polytomic caps its own consumption below the org limit and backs off rather than running the allowance down, and full loads route through the Bulk export path so a backfill does not burn per record calls. Object and field visibility is exactly the permission surface of the OAuth user, which is worth checking first because missing permissions look identical to missing connector support.

Question 5

Why replicate Salesforce into a data warehouse?

Accepted Answer

Because the questions people ask usually span systems Salesforce does not hold. Product usage, billing and support data sit elsewhere, and joining them to accounts and opportunities is the point of ETL into a data warehouse. A warehouse copy also gives you history that the CRM does not keep in a queryable form, so questions about how a pipeline moved over several quarters become SQL rather than guesswork.

Sync Salesforce to Snowflake

Sync Salesforce to Snowflake with Polytomic

Custom objects and formula fields

Soft deletes flagged, not dropped

Incremental with a lookback

Or sync Snowflake to Salesforce

Trusted by businesses worldwide

Step-by-step integration guide

Connect Salesforce in Polytomic

Connect Snowflake in Polytomic

Create a sync between Salesforce and Snowflake

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 Snowflake?