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|
|API configurable||check||API configuration|
|Fivetran data models||check||Get the models: source / transform / formula utils; Supports Quickstart data models|
|Private networking||check||AWS PrivateLink|
|Financial Services Cloud|
|Service Cloud||Including Salesforce Knowledge|
|Marketing Cloud||Using our Marketing Cloud Connector|
|Engagement||Using our Heroku PostgreSQL or Heroku Kafka connectors|
|Industries||Industry-specific like finance and healthcare|
Our two Salesforce connectors, Salesforce and Salesforce Sandbox, support the following environments:
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.
REST and Bulk API usagelink
We use both the Salesforce REST API and the Bulk API to sync your Salesforce data. The Bulk API works better with high-volume data. We choose between the Bulk and REST APIs depending on the volume of data we need to sync for a table. For historical syncs or high-volume incremental syncs, we use the Bulk API; otherwise, the REST API.
Bulk API quotalink
Each Salesforce account has a rolling 24-hour Bulk API quota. If 90% of the bulk jobs quota has been consumed, to continue the sync we fall back to the REST API.
REST API quotalink
Each Salesforce account has a rolling 24-hour REST API quota. We automatically postpone 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 usagelink
The system table FIVETRAN_API_CALL tracks information about API calls made to sync data into the destination.
Salesforce objects often include automatically populated fields called formula fields. Their values are derived from formulas created by your Salesforce administrators. Due to Salesforce limitations, these fields cannot be synced incrementally with reliable integrity. Fivetran automatically detects formula fields and excludes them from the tables synced to your destination.
Replicating formula fields in your destination requires a downstream transformations-based approach. Fivetran helps with this by maintaining SQL translations of the Salesforce formulas in your destination. The detailed documentation about formula fields explains the Salesforce limitations that make this approach necessary as well as explains how to make use of Fivetran's formula translations to add formula fields to your tables.
Delete capture limitationlink
We don't capture deletes of the field tracking history objects because we don't have dedicated endpoints to fetch deleted records for each object. To capture deletes for a specific history object, we can't use the
getDeleted() because the call returns all the records deleted during the specified date range for all the history objects.
Deleted records are retained in the Recycle Bin for 15 days. After 15 days, deleted items are purged from the Recycle Bin, and we can't use the
getDeleted() to fetch them.
We trigger table re-syncs to capture deletes if:
- We are unable to capture deleted records of a specific table for more than 15 days.
- We receive exceptions like
TooMuchDataExceptionwhen fetching deleted records.
(Optional) AWS PrivateLink Private Previewlink
IMPORTANT: You must have a Business Critical plan to use AWS PrivateLink.
If you select PrivateLink as a connection method, Fivetran uses AWS PrivateLink to move your data securely between Salesforce and your destination. You must have a Salesforce Private Connect license to use AWS PrivateLink.
To set up AWS PrivateLink for your Salesforce source, follow the instructions in the Salesforce setup guide.
We sync most tables using incremental syncs. To run incremental syncs, Fivetran requires reliable timestamp fields. Timestamp fields allow us to detect which rows have changed since the last sync and sync only new or modified data. In Salesforce, we use one of the following timestamp fields to track when data was last updated in the source:
LoginTimeIf none of these fields are available in a table, then we re-import the table.
NOTE: Salesforce does not update the incremental column
SystemModstamp/LastModifiedfor objects when there is an update in derived fields. Salesforce derived field values are never actually stored nor modified. As a result, your incremental syncs will not include updated data from these fields. To learn more about derived fields, see Salesforce's documentation.
We also re-import the
OpportunityTeamMember tables because Salesforce does not update the
SystemModstamp column for these tables if you change their access settings by modifying the organization-wide sharing defaults.
The re-import frequency depends on the time it takes for a table to re-sync.
|Table Import Duration||Import frequency|
|3 seconds or less||every sync|
|between 3 seconds and 5 minutes||once a day if the sync frequency is 24 hours; otherwise, twice a day|
|more than 5 minutes||once a week on Saturday|
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, which must be replicated using transformations to ensure integrity.
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.To zoom, open the ERD in a new window.
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
- 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
Although Fivetran does not sync compound fields as is, we sync all fields of a compound field in a Salesforce object as the corresponding individual fields in their respective tables corresponding to the object. For example, the Address compound field may appear as
BillingAddress in the
User object in Salesforce. In that case, the subfields of the Address compound field are synced to the
USER table in your destination as individual columns that have the
billing_ prefix (for example,
billing_postal_code, etc.). You can reconstruct the compound field downstream using these individual fields.
We convert empty strings (
Syncing empty tables and columnslink
Fivetran can sync empty tables and columns for your Salesforce connector. For more information, see our Features documentation.