Overview
Map Apollo fields to Salesforce ones to ensure that contact, lead, and account data from Salesforce syncs properly to Apollo. You can also set data writing rules to define how and when Apollo updates data in your CRM.
Check out the following sections to learn how to map Apollo fields and configure data writing rules.
Map Fields to Salesforce
After you connect Salesforce to Apollo, map Apollo's default fields to the fields in Salesforce. If you have custom fields, you can link custom Apollo fields to custom Salesforce fields as well.
When mapping fields, map each Apollo phone type, such as primary, mobile, work, or other, to its own Salesforce field. Apollo only pushes the phone types you map.
To sync consent data, map Apollo's do not call field to sync a contact's stored DNC status. Apollo doesn't run a live DNC check during CRM sync. You can also map Apollo's call opted out field to Salesforce for contacts and leads. This mapping syncs in both directions, isn't enabled by default, and requires the standard DoNotCall field or another checkbox field. Text, dropdown, and picklist fields aren't supported.
Field mapping changes don't backfill existing records. To apply Salesforce values to existing Apollo contacts, use a manual pull.
To map Apollo fields to Salesforce ones:
- Launch Apollo and go to Settings > Integrations > All integrations > Salesforce, then click Contacts, Leads, Accounts, or Deals, depending on the type of record you want to map. The process to map Apollo fields to Salesforce fields is the same for contacts, accounts, leads, and deals, so repeat these steps for all record types.
- Click Fields.
- Map Apollo fields to their corresponding Salesforce fields. Fields that Apollo can enrich are marked with ⟳ next to the field type.
- Click Add field mapping to map any additional non-default fields.
- Click Delete to remove a field mapping.
- When finished, click Save.
You have now mapped fields between Apollo and Salesforce.
To update your existing records to match the mapping, go to Settings > Integrations > All integrations > Salesforce and select contacts, accounts, leads, or deals. Click Push all to apply Apollo stage data to existing Salesforce records or Pull all to apply Salesforce stage data to existing Apollo records.
If you update or add fields or stages in Salesforce, update the mapping in Apollo to reflect these changes. If you delete a stage in Salesforce, move the lead, contact, account, or deal into an active stage. Check out Automatically Create and Map Stages Between Salesforce and Apollo for more best practices.
Apollo sends a default source value, such as "Apollo," when it creates contacts or leads in Salesforce. This setting is separate from field mapping. To change it, go to Settings > Integrations > All integrations > Salesforce > Contacts or Leads, then update Source for contacts and leads that are pushed to Salesforce. Only single-line text fields are supported.
Map Creator Attribution to Salesforce
A Salesforce admin must enable Set Audit Fields upon Record Creation and grant that permission to the Salesforce user that Apollo uses for syncing. If the permission isn't enabled for the connected Salesforce user, Salesforce rejects new records when Apollo tries to create them and the sync fails.
By default, records created by Apollo in Salesforce show the team sync user in the Salesforce created by field. If your team uses Salesforce's creator field to represent record ownership, individual Apollo users can connect their personal Salesforce accounts, and then you can use this mapping to preserve creator attribution when records sync to Salesforce. When Apollo's created_by field is mapped to Salesforce CreatedById, Apollo syncs the Apollo user who originally created a supported new record as the Salesforce creator.
This mapping uses the Apollo user who originally created the record. For example, if Rep A creates a contact in Apollo and Rep B later pushes it to Salesforce, Apollo uses Rep A as the Salesforce creator when Apollo can match Rep A to a Salesforce user. If your team uses Salesforce creation as its ownership signal, this allows Rep A to retain or claim creator attribution even though someone else synced the record.
Apollo can only send a Salesforce CreatedById value when Apollo can match the Apollo record creator to a Salesforce user. If Apollo can't match the user, Salesforce may use the connected Salesforce sync user as the creator instead. Salesforce doesn't allow this field to be changed after a record is created, so existing Salesforce records aren't backfilled, and updates to existing records won't change the Salesforce creator value.
This mapping can be applied to new Salesforce contacts, leads, accounts, or deals/opportunities.
To map creator attribution to Salesforce:
- In Salesforce, confirm that set audit fields upon record creation is enabled and assigned to the Salesforce user Apollo uses for syncing to Salesforce.
- Next, launch Apollo and go to Settings > Integrations > All integrations > Salesforce.
- Click Contacts, Leads, or Accounts, depending on the type of record you want to map.
- Click Fields > Add field mapping.
- Check Apollo's
Created byuser lookup field under Activity.
- Click Add field.
- Map the field to Salesforce's
CreatedByIdfield.
- When finished, click Save.
You have now mapped the created by field.
Configure Data Writing Rules
After you map fields, set data writing rules for contacts, leads, and accounts. These settings define how Apollo manages Salesforce data when you enrich it with Apollo. Data writing rules are required for you to use real-time or scheduled enrichment.
Manual actions always take precedence over your data writing rules. If you manually enrich a field with CRM enrichment, Apollo pushes the update to your CRM regardless of data writing rules.
To configure data writing rules:
- Launch Apollo and navigate to Settings > Integrations > All integrations > Salesforce, then click Contacts, Leads, or Accounts.
- Click Data writing rules.
- Select whether to overwrite or auto-fill your Salesforce CRM fields with Apollo data:
- Check Auto-fill to automatically use Apollo data to fill in a Salesforce field. Apollo only autofills if the Salesforce field is empty and Apollo has relevant data available.
- Check Overwrite to automatically overwrite the existing information in a Salesforce field with data from Apollo. Apollo only overwrites field data if relevant information is available that differs from the record data already in Salesforce.
Salesforce only updates the address fields Apollo sends during a sync. If Apollo sends an updated country but not an updated city or state, existing Salesforce values may remain and create an incorrect address. Update the city and state in Salesforce manually, or update the corresponding address fields in Apollo and sync the record again.
- When finished, click Save.
You have now configured data writing rules.
You're ready to configure Salesforce push and pull settings.
Next Steps
Here are a few Salesforce resources you can use to keep your Apollo ↔ Salesforce sync running smoothly.
| Integrate Salesforce with Apollo | If your team's still wiring things together, integrate Salesforce with Apollo to turn your field map plans into a live, two-way sync between both systems. |
|---|---|
| Manage Salesforce Integration Credentials | Tighten your foundation by having an admin manage Salesforce integration credentials so Apollo always syncs with the right permissions and ownership rules in place. |
| Configure Salesforce Push Settings | You can configure Salesforce push settings to decide exactly which Apollo updates write back to Salesforce so your mapped fields don't flood the CRM with noise. |
| Map Default Apollo Fields to Salesforce | Make sure the basics are rock solid by having your team map default Apollo fields to Salesforce so core contact, account, and deal data always lands in the right place. |
| Link Custom Salesforce Fields to Custom Apollo Fields | If you rely on extra data points, you can link custom Salesforce fields to custom Apollo fields to keep all your unique attributes enriched and perfectly aligned across both platforms. |