Question 1

What can Polytomic pull from Salesforce into Redshift?

Accepted Answer

Any object the connected user can see, which covers the standard set of accounts, contacts, leads, opportunities, cases and campaigns, plus your custom objects. Formula and rollup summary fields come across as evaluated values rather than as formula definitions, so you do not have to rebuild the logic in SQL. Field level security applies, so if the connected user cannot see a field, it will not appear.

Question 2

What do we need to set up on the AWS side?

Accepted Answer

Redshift writes always stage through Amazon S3, so you need a bucket in the same region as your cluster. Polytomic needs PutObject, GetObject, GetObjectAttributes, ListBucket and DeleteObject on that bucket, and database rights covering TEMP, INSERT, UPDATE, DELETE, TRUNCATE, ALTER, CREATE and DROP on the destination objects. Provisioned clusters accept either an access key pair or an IAM role. Staged files are cleaned up after a successful run, but an S3 lifecycle rule is still worth adding.

Question 3

How do incremental reads work?

Accepted Answer

After the first full load, each run asks Salesforce for records changed since the last successful run and upserts them into Redshift, so ongoing ETL moves a small fraction of the data rather than rescanning every object. Salesforce does not broadcast schema changes, so new fields are found by polling rather than being pushed, and newly discovered columns can be added to the destination automatically.

Question 4

Are deleted Salesforce records reflected in Redshift?

Accepted Answer

Yes, within the limits Salesforce imposes. Reads include soft deleted and archived records and expose the deletion flag as a column, so a removed record is marked rather than silently vanishing. By default Redshift represents this as a soft delete timestamp. If you would rather the rows disappear, the propagate hard deletes option removes them physically. Records purged from the Recycle Bin are gone from Salesforce entirely and need a full resync to reconcile.

Question 5

Why replicate Salesforce into a data warehouse?

Accepted Answer

Because the questions people ask about pipeline usually need data Salesforce does not hold. Attaching product usage, billing or support history to an opportunity means joining across systems, and reporting limits inside the CRM make that awkward. ETL into a data warehouse lands the CRM next to everything else so those joins become ordinary SQL, and gives you a history you can query rather than a live view that overwrites itself.

Sync Salesforce to Redshift

Sync Salesforce to Redshift with Polytomic

Custom objects and formula fields

Soft deletes flagged, not dropped

Stays inside your API budget

Or sync Redshift to Salesforce

Trusted by businesses worldwide

Step-by-step integration guide

Connect Salesforce in Polytomic

Connect Redshift in Polytomic

Create a sync between Salesforce and Redshift

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