Salesforce and Snowflake integration
Warehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
Both waysSalesforce and Snowflake
Led by a SnowPro Core and Salesforce Platform Data Architect certified consultant.
What moves between them
- Into SalesforceUsage, revenue and product metrics per account, refreshed on a schedule and written as fields reps can report, filter and automate on.
- Out of SalesforceAccounts, deals and activity for the BI team, through a connector or Data Cloud zero copy, with renames and deletes planned with the data team.
How we build it
- The definition comes firstThe BI team’s SQL is the source. We reproduce their numbers exactly in a sample before anything is written to Salesforce, so the CRM and the dashboard never argue.
- A dedicated integration userA Salesforce Integration user signs in with a certificate through an External Client App. It can edit only the fields it owns, and no person’s login sits behind the sync.
- A key both systems shareAn external ID on the account, compared as a number where IDs carry leading zeros, so 0744 and 744 match.
- Changed values onlyEach run writes only what changed. Field history stays readable and automation does not fire on unchanged records.
- Checks after every runRow counts reconciled against the warehouse, and an alert to the owner when a run is silent or a count drifts.
What goes wrong, and the fix
Problems we have found and fixed in production.
- Salesforce and the BI dashboard show different numbersTwo definitions of the same thing, often “active” or “live”. We adopt the BI team’s definition word for word, in one function every field uses.
- A renamed Salesforce field breaks warehouse reportsConnectors pick up the new column, but views downstream still reference the old name, and deletes arrive days late. Renames go through a short plan agreed with the data team.
- Restoring deleted records creates duplicates in the warehouseAn undelete restores the external ID too, and the next poll copies it within hours. Restores clear the ID in the same step, and a nightly duplicate check runs instead of a unique constraint, which would also collide with records in the recycle bin.
- Salesforce will not let you create the connected appNewer orgs block new connected apps. External Client Apps are the supported path, and we build the integration on one.
Questions
Should we use Data Cloud zero copy or a sync?
Zero copy suits reading warehouse data inside Data Cloud without copying it. A sync suits the common case where the sales team needs the numbers as fields on the account, for reports, list views and automation. Many orgs use both.
Do we need a paid connector?
No. A scheduled job with certificate sign-in can write to Salesforce directly. A reverse ETL tool is a good choice when you already own one; the definitions and checks matter more than the tool.
Other Salesforce integrations
- Salesforce and DocuSignAgreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
- Salesforce and Adobe Commerce (Magento)Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.
- Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
- Salesforce and Microsoft Dynamics 365Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.
- Salesforce and Apollo.ioProspects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.
- Salesforce and IntercomSupport chats logged on the right contact and account, credited to the person who answered, and the account owner and region visible to the support team.
Talk to us about Salesforce and Snowflake.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.
hello@feldtgroup.com