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.