Field Mapping defines what information Enginy sends to Salesforce and which field it should be stored in.
The screen has three tabs:
Contacts, for the Contact object.Leads, for the Lead object.Companies, for the Account object.
Configure each tab you are going to use. Choosing Contact or Lead as the default object does not automatically copy the mapping from one tab to another.
Mapping types
Field Mapping
Connects an existing Enginy field with a Salesforce field.
Enginy field | Usual Salesforce field |
Professional email | |
First name | FirstName |
Last name | LastName |
Job title | Title |
Company name | Name, in the Companies tab |
Use Add field to add a row. The same Salesforce field cannot be used twice within the same mapping.
Custom fields
Custom fields are additional Salesforce fields you want to store in Enginy. They can be used as columns and during imports.
Creating this mapping does not create the field inside Salesforce. The field must already exist and the integration user must be able to access it.
Fixed value fields
Fixed value fields always send the same value.
For example, you can set every record exported from Enginy to receive a specific value in a Source field. If the Salesforce field is a Picklist, select one of the available values.
Manual export fields
Manual export fields appear in the manual export form. Whoever runs the export must fill in the value before starting the operation.
These fields are only requested in manual exports. If Salesforce requires the field in other kinds of export too, use Field Mapping or Fixed value fields.
Engagement fields
Engagement fields set a value when Enginy logs an activity in Salesforce. You can configure one field in the Contacts tab and another in Companies. This section is not available for Leads.
Choosing the right direction
Every Field Mapping row has a direction selector.
Enginy overwrites Salesforce
When Enginy exports or updates an existing record, the Enginy value replaces the value already in Salesforce.
Use this option when Enginy should be the source for that field.
Sync with Salesforce
On an existing record, Enginy keeps the Salesforce value when that field already contains information. If it is empty, Enginy can fill it in with the available value.
The name of this option can be misleading: it does not turn on a continuous two-way sync. Changes made in Salesforce are not automatically imported into Enginy.
On new records, Enginy can send the mapped value during creation.
Field type compatibility
Enginy shows warnings when the types look different, but Salesforce decides whether it accepts the value at export time.
Information in Enginy | Recommended Salesforce type |
Text, email, phone or URL | Text, Text Area, Email, Phone or URL |
Amounts | Number, Currency or Percent |
Dates | Date or Date/Time |
Yes or no | Checkbox |
Values from a controlled list | Picklist or Multi-Select Picklist |
For Picklist and Multi-Select Picklist, the values sent must match the options allowed in Salesforce. A restricted Picklist can reject any value that is not among its options.
Avoid mapping free text to a Lookup or Reference. Salesforce expects the identifier of another record, not its visible name.
What the icons mean
The blue check means that field is selected. It does not confirm that the types are compatible.
The yellow warning flags a possible incompatibility. You can save the mapping, but it is worth testing.
A disabled field cannot be selected. It may already be in use or have been identified as read-only.
Enginy cannot anticipate every restriction in a Salesforce organization. Field-Level Security, Validation Rules, Flows, triggers and restricted Picklists can cause an error even when no warning appears.
Required fields
Salesforce requires at least these standard fields when creating records:
Object | Required field |
Contact |
|
Lead |
|
Account |
|
Your organization may require other fields through custom fields, Validation Rules or automations.
If one of those fields does not always have a value in Enginy:
Add it as a
Fixed value fieldif it should always receive the same value.Add it as a
Manual export fieldif someone should choose it on each manual export.Use a different Enginy field that always contains information.
Important: Review the Country mapping in the Leads tab before your first export. It must point to the country field your Lead object actually uses.
Checking the mapping
After saving:
Export a single test record for each object you are going to use.
Check the values received in Salesforce.
Verify which fields were kept and which were overwritten.
Review the Enginy export report if any error appears.
If Salesforce rejects the record, check required fields, permissions, Validation Rules and Picklist values first.
Which records Enginy may create
Two settings decide whether Enginy creates a record in Salesforce that it could not match. They are the most common reason a contact "never arrived".
The creation toggles
In Sync configuration you will find two switches, both on by default:
Create contacts in Salesforce when no match is foundCreate companies in Salesforce when no match is found
Turn one off and Enginy updates what it matches and skips the rest. Nothing new is created for that entity.
Required fields for creation
Each row in the Field mapping table has a checkbox in the Required column. Tick it and a record missing that field is skipped instead of created.
Good to know: This never blocks an update. A record that already exists in Salesforce keeps being updated as usual, because the rule only gates creation.
Three things worth knowing before you use it:
One configuration covers every CRM. The check runs on the Enginy values, before they are translated into Salesforce field names. If you connect a different CRM later, the same rules apply.
0andfalsecount as filled in. A field is only missing when it is empty, contains nothing but spaces, or is an empty list.Turning creation off does not erase your selection. The list stops applying while the toggle is off, and comes back untouched when you turn it on again.
The checkbox is disabled while creation is off for that entity. Enable the matching toggle in Sync configuration first.
Important: There is one list for contacts, not one per object. "Contact" here means the Enginy entity, so the same required fields apply whether your contacts export to Salesforce Contact or to Lead.
The rule that always applies
Always: A contact with no email, no phone, no LinkedIn URL and no CRM ID cannot be exported at all, whatever you configure here. Enginy would have no way to match or identify it in Salesforce.
Where you see the effect
Export to CRM checks your selection before running and tells you how many records are missing required fields. If every record in the selection would be skipped, it blocks the export with None of these contacts will be created in your CRM.
These rules also apply to automatic campaign syncs, not just manual exports.