5 reasons the Fivetran Salesforce connector just works

Salesforce is where your business lives — pipeline, accounts, contacts, opportunities, cases, custom objects your admin built specifically for how your team works. It's also notoriously difficult to extract data from reliably. The API is powerful but complex. Formula fields don't behave like regular fields. Custom objects need to be discovered, not assumed. And Salesforce enforces daily API limits that a carelessly built pipeline can exhaust before lunchtime.

Fivetran's Salesforce connector was designed to remove every one of these problems. You connect with OAuth, Fivetran discovers your schema automatically, formula fields are handled through translated SQL views, files are replicated alongside structured data, and the connector manages your API budget as carefully as your data team would. 

Here are the five things that make it genuinely production-ready.

[CTA_MODULE]

1. No API knowledge required

Connecting to the Salesforce API directly means understanding OAuth flows, Bulk API versus REST API trade-offs, pagination strategies, cursor management, and session token refresh. For a data engineer, doing it once is a week of reading documentation. For a RevOps analyst who just wants their opportunity data in Snowflake, it's a complete non-starter.

Fivetran's Salesforce connector requires exactly one thing from you: authorize access with your Salesforce credentials via standard OAuth. From that point, Fivetran handles everything. It discovers all accessible objects in your org and knows how to extract each selected one. It paginates results correctly, manages session tokens automatically, and switches between the Bulk API and REST API depending on what each object requires for optimal throughput. You never write a line of code. You never read a Salesforce API changelog.

 2. Full coverage, including custom objects

A Salesforce org is not just Accounts, Contacts, Leads, and Opportunities. Every team customizes Salesforce to fit their workflows. Sales teams add custom fields to Opportunities. Service teams build custom objects for escalation tracking. Marketing ops creates custom objects for campaign attribution. By the time a data team needs to analyze the full picture, a typical mid-market Salesforce org has dozens of custom objects and hundreds of custom fields that no generic connector catalog will list by name.

Fivetran syncs every object and field that your Salesforce user has permission to access — standard and custom, without you naming them in advance. Custom objects appear as tables in your destination. Custom fields appear as columns. When your admin adds a new field to the Opportunity object, it shows up in your warehouse after the next sync. When a new custom object is created, Fivetran detects it automatically and begins replicating it. The schema in your destination mirrors your Salesforce org as it actually is, not as a connector vendor assumed it would be.

3. dbt Quickstart and formula fields

Formula fields are Salesforce's most useful — and most annoying — data feature. A formula field like ARR = MRR * 12, or a lookup field that pulls the Account Name onto an Opportunity, is calculated dynamically by Salesforce and never stored as a discrete value. Because Salesforce doesn't update an object's SystemModStamp when a formula field's underlying data changes, standard incremental syncing cannot reliably capture formula field changes. Fivetran excludes formula fields from direct replication by default — not as a limitation, but as a deliberate choice to protect data integrity.

The solution is Fivetran's dbt Quickstart package for Salesforce, which translates your Salesforce formula definitions into standard SQL and creates views in your destination that compute the correct formula field values from the replicated base data. The Quickstart package runs automatically after each sync on an integrated schedule — no separate dbt project required, no coding, and no CLI. Formula fields appear in a dedicated Quickstart schema alongside your standard Salesforce tables, always reflecting current values. The FIVETRAN_FORMULA_MODEL table stores every translated formula definition.

4. Unstructured data — files included

Salesforce isn't just a CRM for structured records. Sales teams attach contracts, proposals, and signed agreements to Opportunities. Support teams attach screenshots and diagnostic files to Cases. Marketing attaches brand assets and approved content to Campaigns. These files live in Salesforce Files — the ContentVersion object — and, until recently, they were stranded there, inaccessible to the analytics and AI workflows that need them alongside the structured data they're linked to.

Fivetran's Salesforce connector now supports unstructured file replication. When enabled, it syncs the latest version of each file from ContentVersion — PDFs, images, Word documents, spreadsheets, and more — to your destination, prefixed with the ContentVersion record ID for reliable linkage. The ContentDocument and ContentDocumentLink objects are synced alongside each file so the relationship between the file and its parent record (the Opportunity, Case, or Account it's attached to) is preserved. Files of the SNOTE type are stored as plain text. Metadata — file name, created date, file type, the _fivetran_file_path reference — is maintained in the ContentVersion table.

5.  Set up in minutes, built for production

The Salesforce API operates on a daily request limit tied to your org's edition and user count. A connector that hammers the API without awareness of this limit can exhaust your daily budget before business hours end — blocking Salesforce users from the platform while the connector catches up. Most teams that have built their own Salesforce extraction pipelines have experienced this at least once. It's the kind of production failure that gets a data engineer paged on a Monday morning.

Fivetran manages your Salesforce API budget as a first-class concern. It automatically switches between the Bulk API — which is far more efficient for large object syncs and doesn't count against the same daily limit — and the REST API for smaller, more targeted queries. You can configure the maximum percentage of your daily API allocation that Fivetran is allowed to consume (between 50% and 90%, defaulting to 90%). When the limit approaches, Fivetran automatically reschedules the sync rather than failing. Objects that haven't changed in 7 days are promoted to a once-daily check to reduce unnecessary API calls. The connector currently runs on Salesforce REST API version 65.0, maintained and upgraded by Fivetran as Salesforce releases new versions.

Salesforce data in your warehouse without the complexity

No API expertise required, full custom object coverage, formula fields solved through automatic dbt translation, files replicated alongside structured data, and an intelligent API budget manager that keeps production syncs running smoothly — the Fivetran Salesforce connector handles every technical complexity of Salesforce data extraction so your team can focus on the analysis.

Connect with OAuth, point it at your destination, and your entire Salesforce org — structured, formulaic, and unstructured — starts flowing in minutes.

[CTA_MODULE]