Salesforce is a cloud-based CRM platform.
We pull all the underlying data from Salesforce (SFDC) into a SQL-enabled environment to allow you to get a more in-depth analysis of your CRM data.
|Capture Deletes||check||Only for replicateable objects|
|Data Blocking||check||Column level, table level, and schema level|
|Re-sync||check||Table level and connector level|
|dbt Package||check||Get the package: source / transform|
|Financial Services Cloud|
|Service Cloud||Including Salesforce Knowledge|
|Marketing Cloud||Using our Marketing Cloud Connector|
|Engagement||Using our Heroku Postgres or Heroku Kafka connectors|
|Industries||Industry-specific like finance and healthcare|
Follow our step-by-step Salesforce setup guide to connect Salesforce with your destination using Fivetran connectors.
The number of API calls that we use varies from company to company. Our Salesforce connector is optimized to use the fewest API calls possible. In practice, customers find that Fivetran is not a significant API consumer.
Rolling API quota
Each Salesforce account has a rolling 24-hour API quota. Fivetran automatically reschedules syncs by one hour whenever 90% of the Salesforce API call quota has been consumed. This ensures there is always API quota available for other business-critical applications.
Monitoring the API usage
The system table FIVETRAN_API_CALL tracks information about API calls made to sync data into the warehouse.
REST and Bulk API usage
We use both the Salesforce REST API and the Salesforce Bulk API to sync your Salesforce data. Fivetran uses the Bulk API for historical syncs and the REST API for incremental syncs. We choose the sync strategy depending on the size of the data to be synced and the number of records changed since the last sync. We use multiple techniques to minimize the total number of API calls, specifically the Bulk API calls, because Salesforce limits the number of Bulk API calls.
We disable syncing formula field values by default. However, we can enable them at your request.
NOTE: Formula fields can cause subtle problems in your data. Before you decide to sync formula field values, read our detailed documentation about formula fields and lookup fields, which explains the risks and our recommended solution.
Salesforce Field History Trackinglink
Salesforce has native functionality that lets you define specific fields for which you want to track history. This functionality is distinct from Fivetran’s history mode. Read our blog post comparing Fivetran history mode to the alternatives to learn if Salesforce field tracking or Fivetran history mode is better for your analytical needs.
If you decide to use Salesforce field history tracking to track and capture all changes in the selected fields, you will need to enable it in Salesforce. Enabling it will create additional tables in Salesforce that will track and store the changes.
Fivetran will then import these history objects as separate tables during incremental updates. To learn how to enable field history tracking, see the Salesforce Field History Tracking documentation.
IMPORTANT: We have disabled Fivetran history mode for native Salesforce history objects associated with standard objects. The standard objects are listed in the Salesforce StandardObjectNameHistory documentation. The history object names have the following format:
We do not capture hard deletes for history objects but use the
is_deleted field from Salesforce to capture deletes.
Fivetran follows a one-to-one mapping with all objects in Salesforce. If you can’t find something that you’re looking for, your Salesforce user may have limited access to the information. Fivetran tries to sync all possible objects, except for formula fields.
This schema diagram illustrates how objects relate to one another. It is not a complete Entity Relationship Diagram. It shows relationships for some central entities and workflows. Many standard and all custom entities that are delivered by the Fivetran Salesforce connector are omitted for brevity.
We also offer you information about the connector in the
Unsupported data typeslink
Our Salesforce connector does not support the following data types and object types:
- base64 type
- complexvalue type
- Compound fields, for example, address and location
- Deprecated and hidden objects
- Objects that don’t support limit
- BigObject, or objects whose names end with
- Non-queryable objects
- Object whose names end with