Salesforce Field Mapping on LeadGenius

Christine Espiritu
Christine Espiritu
  • Updated

This document will explain how to map LeadGenius fields to Salesforce fields, as well as the overwrite logic that we will use when exporting records to Salesforce.

When exporting new data to Salesforce (net-new segments), we will create new records in Salesforce, in the format that you select (Leads or Accounts & Contacts). When exporting CRM Enrichment segments to Salesforce, we will update your existing records in Salesforce with updated data using the format of the report you used for that segment. Appended contacts will be exported as per your chosen settings.

These instructions assume that you have connected your Salesforce account to LeadGenius. If you have not already connected your Salesforce account to LeadGenius, follow these instructions to do so.


Confirming Your Field Mappings

After you have connected Salesforce to LeadGenius, you will be brought to the Configure Mappings screen. This is where you will choose which Salesforce fields correspond to the LeadGenius fields on your lists. You will need to confirm these mappings before you are able to import or export data, to or from Salesforce.


On the left, we have a toggle, so that you are able to turn fields on or off for export. To the right of that, we have the LeadGenius fields that are present on your lists. The center column shows the Salesforce fields that will be used for Accounts in your Salesforce. The right column shows the rules for when we write to those fields in Salesforce. 

There are separate tabs for Account fields, Contact fields, and Lead fields that can be found on the left navigation panel. In addition, each of these tabs has a drop-down to set up mapping for Standard, Advanced, and Custom (if created) fields.

Note: Fields that are in gray and have a muted toggle are required fields and cannot be unmapped or changed. Additionally, once a Salesforce field has been mapped to a LeadGenius field, it cannot be mapped to another LeadGenius field unless you unmap your original selection.

Overwrite Logic

The Configure screen also determines how we handle the data being exported back to Salesforce from LeadGenius. 

  • Always means that we will always update this field when exporting.
  • ​Blank means that we will only update that field if it is blank in your Salesforce.

Data Types and Field Types

When mapping LeadGenius fields to Salesforce fields, the data types for those fields must match. For example, the Employee Range field in LeadGenius is a string field. The Employees field in Salesforce is an integer field. So, the Employee Range would have to be mapped to a string field or be left unmapped. 

Another way to correct this issue is to have your Salesforce Administrator change the data type of the field. 


Lead Source & Data Format

You will see the option to choose what you would like the Lead Source to be set to for your exported LeadGenius data, and how you would like that to be updated.

You will also have the option to either export your LeadGenius data as Leads or as Accounts & Contacts. Once you have selected one of these options, if you decide to change it later, you will not be able to re-export any data previously exported in the other format, to avoid duplicate data in Salesforce. 

You can set the writeback rule for Lead Source to Always or Blank.



I noticed that some of the fields in my Salesforce are not showing up in LeadGenius for mapping. How do I fix this?

Sometimes, due to settings within Salesforce, some fields may be hidden for some users but are visible to others. In order for Salesforce fields to show in LeadGenius, they must be visible to the user whose account is connected to the LeadGenius integration.

In order to correct this issue, your Salesforce Administrator will need to go under Setup → Build → Leads → Fields, find the field that is not showing in LeadGenius, and then Set Field Security Level and make that field visible to the user.