Convert
Convert in Salesforce refers to the Lead Conversion process: the action that takes a qualified Lead record and turns it into one Account, one Contact, and optionally one Opportunity in a single transaction.
Definition
Convert in Salesforce refers to the Lead Conversion process: the action that takes a qualified Lead record and turns it into one Account, one Contact, and optionally one Opportunity in a single transaction. The Lead is marked Converted and locked from further edits; the new records inherit the Lead field values through the Lead Field Mapping defined in Setup. Convert is the bridge between the Lead world (where marketing tracks prospects) and the Account/Contact/Opportunity world (where sales runs the pipeline).
The process exists because Salesforce treats Leads as suspects (unqualified prospects) and Accounts, Contacts, and Opportunities as known entities (qualified prospects and active customers). The Convert action moves data between the two models without requiring a manual copy. Sales orgs that follow this lifecycle religiously have clean handoff metrics; orgs that skip Convert and instead create Accounts directly tend to have data hygiene problems.
How Lead Conversion works
What happens at the moment of Convert
When a user clicks Convert on a Lead, Salesforce checks for matching Accounts (based on Company name on the Lead), creates or updates the Account, creates a new Contact tied to that Account, and optionally creates an Opportunity. All of this happens in a single transaction. The Lead Field Mapping in Setup decides which Lead fields land on which target objects.
The matching logic for existing Accounts
Salesforce searches for existing Accounts that match the Lead Company name. If a match is found, the user can pick to attach to the existing Account rather than create a new one. The match is case-insensitive but exact-string by default; orgs with fuzzy duplicate concerns add a Duplicate Rule or a custom Apex match step.
Field mappings: standard and custom
Standard fields like Name, Email, Phone, and Address map automatically. Custom Lead fields require explicit mapping in Setup, Object Manager, Lead, Fields and Relationships, Map Lead Fields. Map custom Lead fields to Account, Contact, or Opportunity fields explicitly. Unmapped custom Lead data is lost on conversion unless you write Apex to handle it.
What happens to the original Lead
The original Lead is marked IsConverted = true and locked from editing. The user can still see it through the Converted Leads list view or by following the ConvertedAccountId, ConvertedContactId, ConvertedOpportunityId pointers. Lead activities (Tasks, Events, Emails, Campaign Members) are moved to the new Account and Contact, retaining the activity history.
Skip the Opportunity option
Convert has a Do Not Create Opportunity checkbox. Useful when the Lead is being qualified for relationship building rather than a specific deal. The Account and Contact get created, but no Opportunity. Many B2B sales teams turn this off by default; many B2C teams turn it on.
Custom Convert action and Apex overrides
The standard Convert button covers basic cases. For complex requirements (auto-create Account team members, write to a custom object, run a fuzzy match across multiple fields, trigger an external API call), build a custom Convert button or Flow that wraps the standard convert behavior. The Database.convertLead Apex method lets you do this programmatically.
Reporting on conversion
Common reports include Lead-to-Conversion-Rate (how many Leads convert to Accounts), Lead-to-Closed-Won (how many of those Opportunities close), and time-to-convert (days between Lead creation and conversion). These reports drive funnel optimization. The Converted Lead History fields (ConvertedDate, ConvertedAccountId, and others) make the joins straightforward.
How to configure and use Lead Conversion
The standard Convert action ships enabled. The configuration work is mapping custom fields and deciding the duplicate handling. The user-facing action is one click.
- Map custom Lead fields
Setup, Object Manager, Lead, Fields and Relationships, Map Lead Fields. Map each custom Lead field to its target Account, Contact, or Opportunity field. Unmapped fields lose their data on conversion.
- Configure Duplicate Rules and Matching Rules
Setup, Duplicate Management. Build Matching Rules for Accounts and Contacts so that conversion matches existing records rather than creating duplicates. Tune the match scope to balance false positives and false negatives.
- Customize the Convert button if needed
For complex conversion requirements, build a custom Lightning Web Component or Flow that wraps the standard Database.convertLead Apex call. Add the custom component to the Lead page layout.
- Train sales reps on when to convert
Convert should happen at the moment of qualification (typically MQL to SQL or SAL). Document the criteria; do not let reps convert prematurely (creates ghost Opportunities) or too late (loses Lead data).
- Build conversion reports
Create reports on Leads with Conversion Info, grouped by Created Date and Conversion Date. Track conversion rate by Source, by Owner, and by Campaign for marketing attribution.
- Set up post-conversion automation
Build Flows triggered on Account or Opportunity creation that handle post-conversion tasks: assign sales team members, create welcome Tasks, send notifications to the new Account Manager.
- Custom Lead field data is lost on conversion if not explicitly mapped. The data goes nowhere; recovery requires querying the Lead record after the fact.
- Convert is a one-way operation. Once a Lead is converted, you cannot un-convert it; recovery means re-creating a new Lead from the converted Account and Contact data.
- Lead activities migrate, but Lead-related custom object records do not migrate automatically. If you have custom objects linked to Lead, write Apex to migrate them at conversion.
- Account matching is case-insensitive but exact-string by default. Acme Corp and Acme Corporation create separate Accounts unless you add a Matching Rule or fuzzy match.
- Database.convertLead does not honor record types automatically. If you have custom record types on Account or Opportunity, pass them explicitly in the LeadConvert object.
Trust & references
Cross-checked against the following references.
- Convert Qualified LeadsSalesforce Help
- Database Apex Class MethodsSalesforce Developers
Straight from the source - Salesforce's reference material on Convert.
- Map Custom Lead Fields for Lead ConversionSalesforce Help
- Duplicate Management OverviewSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Lead Conversion do?
Q2. What happens to the original Lead after conversion?
Q3. What's a good practice during Lead conversion?
Discussion
Loading discussion…