Data Replication

Hevo loads all the objects associated with your Salesforce account. By default, Hevo ingests all the columns available in an object. However, you can select the columns to load on the Object Configuration page.

• Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it to the Destination. Hevo utilizes Salesforce’s Bulk API for data replication and falls back to the REST API when the Bulk API is unsupported for an object.

• Incremental Data: Once the historical load is complete, data is ingested according to the specified sync frequency. Hevo fetches only the data that has been modified since the last sync by checking for updates in the timestamp fields, in the following order: SystemModstamp, LastModifiedDate, CreatedDate, and LoginTime. These fields allow Hevo to identify the records that have been modified or created since the last sync. If the selected object does not contain any of these timestamp fields, Hevo fetches all records from the object during each incremental run.

If the number of requests made to the Salesforce Bulk API exceeds the allowed rate limit, a rate limit exception occurs. In such cases, Hevo retries the request based on its internal retry logic. To understand how Hevo handles these exceptions, read Handling Rate Limit Exceptions.

Note: Hevo creates a Destination table for an object after the first successful API call, even if that call returns no records. Once created, the table is updated with new data from subsequent API calls. However, if the initial API call fails due to issues such as missing permissions or incompatible field configurations, the table is not created.

Handling Compound Fields

In Salesforce, compound fields combine multiple related values into a single field. They can be of different types, such as address, geolocation, or name. Each type defines the group of subfields it contains. For example, the BillingAddress field in the Accounts object represents an address and includes subfields such as city, state, and country.

Hevo does not replicate compound fields as a single column in the Destination. Instead, it ingests each subfield separately and replicates it to individual columns. If a Salesforce object contains multiple compound fields of the same type, Hevo adds a prefix to each subfield name to indicate its parent field. For example, the Account object includes multiple compound fields of Address type, such as BillingAddress and ShippingAddress. In this case, Hevo ingests the subfields from the respective compound field as BillingCity, BillingCountry, and ShippingState. If the Salesforce object contains only one compound field, Hevo replicates the subfields without adding a prefix. For example, the Address field in the Lead object is ingested as City, State, and Country.

Although compound fields are replicated as separate fields, all underlying data is retained. You can recreate the original structure by combining the relevant columns using SQL or other transformations in the Destination.

When filtering data, you must use the subfields, as compound fields cannot be used to filter rows.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

Click to view ERD

Data Model

Hevo supports ingesting data from more than 100 standard Salesforce objects, as well as custom objects that you may have created in your Salesforce account. Hevo also supports associated objects that relate to the standard objects.

The following table lists the most frequently used objects along with their descriptions: