To access Field Mapping, go to Integrations → Salesforce → Configure → Step 2: Field Mapping.
Important: Salesforce requires field types to match exactly. Every mapping must use the correct field type — otherwise the export will fail.
Understanding the Status Icons
Icon | Status | What it means |
✓ Blue | Compatible | The field types match. No action needed. |
! Yellow | Warning | The field types may be incompatible. Review this mapping carefully before saving. |
✕ Red | Error | The mapping cannot be applied. The export will fail for any record using this mapping. |
Warning: Do not save a configuration with red icons. Exports will fail for all records using that field mapping.
Which Salesforce Field Type Should I Use?
Use this table as a reference when selecting the destination Salesforce field for each Enginy field.
Enginy field | Recommended Salesforce field type | Notes |
First name, Last name, Job title, Email, Phone | Text / Long Text Area | Standard text fields. Fully compatible. |
Number of employees, Years in role, Growth % | Number / Integer / Decimal | Map to a Salesforce numeric field. |
Created at, Last activity at CRM | DateTime | Must be ISO 8601 format with timezone. Never map to a Text field. |
Outreach Stage, Sequence Status | Picklist (single) | Value must match an existing picklist option exactly — case-sensitive. |
Languages, Sub-industries | Multi-select Picklist | Values must be separated by |
LinkedIn URL, Domain, Website | Text / URL | Both types are compatible in Salesforce. |
Personal emails, Other phones | Multi-select or Text | Use Professional email and Mobile phone instead where possible to avoid sending arrays. |
Boolean fields (e.g. verified) | Checkbox | Map to a Salesforce Checkbox field. |
Yellow Warning: What to Do
Salesforce requires field types to match exactly. A yellow warning means the mapping is likely to fail and must be reviewed before saving.
1.Text mapped to a Picklist field
If you map an Enginy text field to a Salesforce picklist, Salesforce will reject the value if it does not match one of the configured picklist options exactly. Salesforce returns INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST in this case.
The match is case-sensitive — "Replied" and "replied" are treated as different values.
How to fix it:
Create an AI Variable with output type One off and define the tag options to exactly match the Salesforce picklist values.
For Fixed Value or Engagement fields: enter the exact picklist value directly in the field mapping configuration.
For Manual Export fields: enter the exact picklist value at the time of export.
Note: Multi-select picklist values must be separated by ; — for example: option_one;option_two. Using commas will cause Salesforce to store the entire string as a single unrecognised value.
2.Date field mapped to a Text or Date field
Enginy stores date fields (such as Created at or Last activity at CRM) as full date-time values.
If the destination is a Salesforce Date field: Salesforce only accepts
YYYY-MM-DD. Enginy removes the time portion before sending — the value will sync but the time information will be lost.If the destination is a Salesforce Text field: Salesforce will reject the value with a validation error.
How to fix it: Map Enginy date fields to a Salesforce DateTime field to preserve the full value.
Red Error: What to Do
A red icon means the mapping will always fail. There are two reasons this happens:
Incompatible field types
The field types on both sides are incompatible and Salesforce cannot convert them.
How to fix it: Remove the mapping and select a Salesforce field with a compatible type. Use the reference table above to choose the correct type.
Read-only Salesforce field
The destination field in Salesforce is read-only and cannot be updated by Enginy. This typically affects system fields such as record IDs, formula fields, or roll-up summary fields.
How to fix it: Remove the mapping and choose a writable Salesforce field, or contact your Salesforce administrator to confirm field permissions.
Common Salesforce Mapping Mistakes
Mistake | What happens | How to fix it |
Mapping a Company field in the Contacts tab (or vice versa) | Export fails with a field mapping error | Verify that only Contact fields appear under Contacts, and only Company fields under Companies |
Mapping an Enginy date field to a Salesforce Text field | Salesforce returns a validation error | Map to a Salesforce DateTime field instead |
Mapping an Enginy date field to a Salesforce Date field | Time information is lost | Map to DateTime if you need the full value |
Mapping an Enginy text field to a Salesforce Picklist without matching values | Salesforce returns INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST | Use an AI Variable (One off) with values that match the Salesforce picklist exactly — case-sensitive |
Using commas instead of semicolons for multi-select picklist values | Salesforce stores the entire string as a single unrecognised value | Use |
Mapping to a Salesforce formula or read-only field | Export fails | Choose a writable field instead |
All exports are failing | Connection issue | Try reconnecting your Salesforce integration — go to Integrations → Salesforce and reconnect |
Saving mappings with red icons | All records using that mapping fail to export | Fix or remove any red-icon mappings before saving |
Need More Help?
If you have reviewed your mapping configuration and the export still fails, contact our support team with:
The name of the Enginy field and the Salesforce field you are trying to map
The error message or icon you are seeing
A screenshot of the Field Mapping configuration if possible