Mapping custom lead fields for lead conversion
Key Takeaway
Standard lead fields convert on their own, but each custom lead field needs a mapping to a compatible custom account, contact, or opportunity field. A field in a mapping can't be deleted or have its field type changed until you remove the mapping.
When a rep converts a qualified lead, Salesforce copies the lead's information onto new account, contact, and opportunity records. Standard lead fields carry over without any setup. Custom lead fields need a mapping, which tells Salesforce which custom field on each target object receives the value. Good mappings keep important lead details after conversion and can flag converted records for use in flows.
What carries over when a lead converts
When a rep converts a lead, standard lead fields map to standard contact, account, person account, and opportunity fields. Custom lead fields work differently. An admin must specify which custom account, contact, or opportunity field each custom lead field converts into.
Here are examples of standard mappings:
- Company becomes the Account Name.
- Lead Owner becomes the owner of the new account, contact, and opportunity.
- Address fills these fields:
- Billing Address on an account
- Mailing Address and Billing Address on a person account
- Mailing Address on a contact
Some standard mappings don't update records that already exist. Do Not Call and Email Opt Out aren't updated when a lead converts to an existing contact. Partner Account isn't updated when a lead converts to an existing opportunity.