You are here:
Guidelines for Mapping Custom Lead Fields for Lead Conversion
Learn the best practices for mapping custom lead fields to custom fields in contacts, accounts, and opportunities. Mapping custom fields helps your sales reps retain that important information when they convert qualified leads to track new potential deals.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Starter, Essentials, Group, Professional, Enterprise, Performance, Unlimited, Pro Suite, and Developer Editions with Sales |
- The following Lead custom field types can only be mapped to custom fields of the same data type.
- Checkbox
- Currency
- Date
- Date/Time
- Geolocation
- Encrypted (Classic)
- Number
- Percent
- Phone
- Multi-select Picklist
- Long Text
- Rich Text
- URL
- Each target field can have only one source field mapped to it.
- You can map auto-number fields to field types text or text area.
- You can map text and text area fields to custom field types of text, text area, long text, and picklist. If you map to a picklist field, the picklist must be unrestricted.
- You can map custom picklist fields to custom field types of text, text area, and picklist (unrestricted), but not long text.
- When mapping between picklist and text fields, your data truncates if the source field value is longer than the target field allows.
- Custom lookup fields can be mapped to a lookup field pointing to the same object. For example, a lead custom lookup field pointing to the Account object can be mapped to a contact custom lookup field that also points to the Account object.
- When mapping custom lead fields, the selected account, contact, or opportunity field must be of equal or greater length.
- You can’t delete lead, account, contact, or opportunity fields included in Lead Custom Field Mapping. To delete a field, first remove its mapping.
- You can’t change the field type of a field that’s included in Lead Custom Field Mapping. To change a field’s type, remove its mapping first.
- When you uninstall a package that references fields included in Lead Custom Field Mapping, those custom field mappings are deleted automatically.
- When mapping lead custom number, currency, or percent fields, the target field must have the same length and number of decimal places.
- If you have more than 2000 lead, account, contact, or opportunity fields in total, the lead field mapping page can become unresponsive. To improve performance, delete fields that aren’t in use. You can also use Metadata API, Salesforce CLI, or VS Code Extensions to manage your lead mappings.
- Dependent picklist fields on leads can’t have a default value assigned. These fields are driven from the value selected in the controlling picklist field. Field mappings defined between a controlling and dependent picklist are validated during lead conversion. These mappings don’t allow any values other than the current value of the controlling picklist to be assigned to the dependent picklist.
- In Lightning Experience and Salesforce Classic, custom field mapping for lead conversion is available in orgs that use APEX Lead Convert. Custom field mapping for lead convert is not available in orgs that use the older PLSQL Lead Convert.
- In orgs that use APEX Lead Convert, contact, account, and opportunity fields with field-level security settings are populated from mapped lead fields.
Note Don’t map custom formula fields to other formula fields or any other type of field.
Did this article solve your issue?
Let us know so we can improve!
