Get the most out of records created from converted leads when you map custom lead
fields to fields on the records they’re converted to. Using custom fields can provide more
context about the opportunity, and provide ways to highlight records for use in flows and other
means.
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
User Permissions
Needed
To map lead fields:
Customize Application
When sales reps convert qualified leads, the information
from the standard lead fields appears in standard fields for contact, account, and
opportunity records. If you set up custom lead fields, you specify how that custom
information converts to custom fields in accounts, contacts, and opportunities.
From the object management settings for leads, go to the fields section, then click
Map Lead Fields.
For each custom lead field, select a custom account, contact, or opportunity field into
which you want the information inserted when you convert a lead. In Lightning Experience,
a custom lead field can map to account, contact, and opportunity fields at the same
time.
Save your work.
Example For example, you want to indicate that an opportunity was created from a lead. To do
that, create a custom checkbox on the Lead object, defaulting it to selected. Create a custom
checkbox on the Opportunity object called Created from Lead. Optionally, you can make these
fields read only. Map the custom lead field to the custom opportunity field. When a lead is
converted to an opportunity, the Created from Lead custom field will be checked. From here,
you can use the Created from Lead field value to trigger a flow to update default opportunity
values, such as Stage Name, Description, or Next steps.
Note 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 isn’t
available in orgs that use the older PLSQL (Procedural Language for SQL) Lead Convert.
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.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
