Question 1

What Salesforce data can I load into BigQuery?

Accepted Answer

Whatever the connected user can see. That covers accounts, contacts, leads, opportunities, cases and campaigns, along with any custom objects you have built. Formula and rollup summary fields arrive as calculated values rather than as formulas, so you do not have to rebuild that logic in SQL. Field level security still applies, so a field hidden from the connected user will not appear in your tables.

Question 2

Do I need a Cloud Storage bucket to load Salesforce into BigQuery?

Accepted Answer

No, and this is where BigQuery is simpler than most warehouses. Records are staged inside Polytomic and then pushed through a BigQuery load job, so there is no bucket for you to create, no bucket policy to write and no cross service permissions to line up. Setup is a service account and nothing else. A bucket only becomes relevant if you later read out of BigQuery using the extract option, which is a separate thing.

Question 3

How does Polytomic keep Salesforce data fresh in BigQuery?

Accepted Answer

After the first full load, each run asks Salesforce only for records that changed since the last successful run. Those land in a temporary table and then merge into your destination table on the key you configured, so existing rows update in place rather than being duplicated. Salesforce does not announce schema changes, so new fields are found by checking rather than being pushed, and new columns can be added to BigQuery automatically once discovered.

Question 4

Will deleted Salesforce records disappear from BigQuery?

Accepted Answer

They get marked rather than vanishing, which is usually what you want. Reads include archived and soft deleted records and expose the deletion flag, and the merge sets a deleted at timestamp on the row so you can still count what used to exist. If you would rather they were physically removed, the propagate hard deletes option runs a delete against the flagged rows afterwards. Note that hard deletes need the Polytomic timestamp columns left enabled, since that is what the delete keys off.

Question 5

Why load Salesforce into BigQuery rather than reporting inside Salesforce?

Accepted Answer

Because the interesting questions need data Salesforce does not hold. Tying an opportunity to product usage, support load or invoice history means joining across systems, and CRM reporting was never built for that. ETL into a data warehouse also gives you a history you can query rather than a set of fields that overwrite themselves. This is the most used pairing we see into BigQuery, which suggests most teams reach the same conclusion.

Sync Salesforce to BigQuery

Sync Salesforce to BigQuery with Polytomic

No bucket to configure

Custom objects included

Keyed merge on each run

Or sync BigQuery to Salesforce

Trusted by businesses worldwide

Step-by-step integration guide

Connect Salesforce in Polytomic

Connect BigQuery in Polytomic

Create a sync between Salesforce and BigQuery

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