---
name: salesforce-lead-conversion
slug: salesforce-lead-conversion
description: This skill should be used when the user asks to "convert leads in Salesforce", "set up lead conversion", "Salesforce lead to contact conversion", "design lead conversion process", "when to convert leads in Salesforce", "lead conversion mapping Salesforce", "configure lead conversion in SFDC", "lead to account conversion rules", "Salesforce lead conversion best practices", or any variation of designing and configuring lead conversion processes in Salesforce for B2B SaaS.
category: general
---

# Salesforce Lead Conversion

Lead conversion in Salesforce transforms a Lead record into a Contact, Account, and optionally an Opportunity. It's the moment a prospect transitions from marketing-qualified to sales-accepted. Done well, lead conversion preserves all data, creates proper associations, and triggers the right downstream processes. Done poorly, it creates orphan records, loses data, and breaks reporting.

The principle: lead conversion should happen at a single, well-defined moment in the sales process. Not too early (you lose the ability to track marketing engagement on the lead). Not too late (you create deals on a Lead record, which breaks pipeline reporting). Define the conversion trigger, map the fields, and automate what you can.

## When to Convert

### The conversion trigger

| Approach | Convert when | Best for |
|----------|-------------|---------|
| Upon meeting booked | SDR books a meeting with the prospect | High-velocity sales. Quick cycles |
| Upon SQL acceptance | AE accepts the lead as sales-qualified | Mid-market. More qualification before conversion |
| Upon opportunity creation | AE creates an opportunity | Enterprise. Longer qualification. Fewer false positives |

### Conversion timing rules

- **Convert before creating an opportunity.** Opportunities must associate to Contacts and Accounts, not Leads. If you create opportunities on unconverted leads, pipeline reporting breaks
- **Convert after basic qualification.** Don't convert every MQL. Convert when a human (SDR or AE) confirms the lead is worth pursuing. This keeps your Contact database clean
- **One conversion point, enforced consistently.** All reps should convert at the same trigger. If some convert at meeting booked and others at opportunity creation, your conversion metrics are meaningless
- **Never leave a lead unconverted with an active deal.** If there's an opportunity, the lead must be converted. Period. Unconverted leads with deals are invisible in pipeline reporting

---

## Field Mapping

### Standard field mapping

| Lead field | Maps to | Object |
|-----------|---------|--------|
| First Name, Last Name | First Name, Last Name | Contact |
| Email | Email | Contact |
| Phone | Phone | Contact |
| Title | Title | Contact |
| Company | Account Name | Account |
| Industry | Industry | Account |
| Website | Website | Account |
| Lead Source | Lead Source | Contact (and/or Opportunity) |
| Description | Description | Contact |

### Custom field mapping

```
Setup → Object Manager → Lead → Fields & Relationships
→ Map Lead Fields

For each custom lead field:
  1. Select the lead field
  2. Select the target object (Contact, Account, or Opportunity)
  3. Select or create the matching field on the target
  4. Save

Example mappings:
  Lead: ICP_Fit__c → Contact: ICP_Fit__c
  Lead: Lead_Score__c → Contact: Lead_Score__c
  Lead: Self_Reported_Source__c → Contact: Self_Reported_Source__c
  Lead: SDR_Notes__c → Contact: SDR_Notes__c
```

### Field mapping rules

- **Map every custom field.** Unmapped fields lose their data on conversion. If a lead has `ICP_Fit__c = Tier 1` and the field isn't mapped, that data disappears. Map every custom lead field to a corresponding contact, account, or opportunity field
- **Create matching fields on target objects before mapping.** The target field must exist before you can map to it. Create the contact/account field first, then configure the mapping
- **Map lead source carefully.** Lead Source should map to the Contact's Lead Source field AND optionally to the Opportunity's Source field. This enables attribution reporting at both levels
- **Test the mapping with a real conversion.** Convert a test lead. Check every field on the resulting Contact, Account, and Opportunity. If any data is missing, the mapping is incomplete

---

## Account Matching

### Handling existing accounts

| Scenario | What happens | Configuration |
|----------|-------------|--------------|
| Lead's company matches an existing account | Salesforce suggests the existing account. User confirms | Built-in. Salesforce matches on Account Name |
| Lead's company doesn't match any account | A new Account is created | Default behavior |
| Lead's email domain matches an existing account's website | Can be configured to match on domain | Requires custom matching logic or AppExchange tool |

### Account matching rules

- **Always check for existing accounts.** Converting a lead from "Acme Corp" when an "Acme Corporation" account already exists creates a duplicate. Train reps to check and select existing accounts
- **Match on email domain, not just company name.** "john@acme.com" should match the account with website "acme.com." Standard Salesforce matches on company name, which misses domain matches. Use a matching tool or Flow
- **Merge duplicate accounts after conversion.** If a duplicate account is accidentally created, merge it immediately. Duplicate accounts split deal history and engagement data across two records

---

## Conversion Automation

### Automating the conversion process

| Automation | How | Purpose |
|-----------|-----|---------|
| Auto-convert on status change | Flow: when Lead Status = "Qualified," trigger conversion | Removes manual step. Ensures consistent conversion point |
| Post-conversion workflow | Flow: after conversion, create tasks, update fields, send notifications | Ensures onboarding steps happen immediately |
| Auto-create opportunity | Conversion setting: check "Create Opportunity" | Creates a deal automatically on conversion |
| Assignment on conversion | Flow: assign the Contact's owner based on territory or round-robin | Routes the converted contact to the right AE |

### Automation rules

- **Auto-convert is powerful but dangerous.** Only auto-convert after a human qualification step (SDR marks as qualified). Auto-converting all MQLs floods your Contact database with unqualified records
- **Always create a task after conversion.** Post-conversion Flow: create a task for the AE to "Review converted lead and schedule first call." This prevents converted leads from sitting unworked
- **Don't auto-create opportunities for every conversion.** Only create an opportunity if the conversion represents a real deal. If conversion happens at "meeting booked" but not every meeting becomes a deal, let the AE create the opportunity manually after discovery

---

## Reporting Across the Lead-Contact Divide

### The reporting gap

Leads and Contacts are separate objects. Before conversion, engagement is on the Lead. After conversion, engagement is on the Contact. Without connecting them, you can't report on the full lifecycle.

### Solving the gap

| Method | How | Limitation |
|--------|-----|-----------|
| Converted Lead reports | Use "Leads with Converted Lead Information" report type | Limited cross-object capability |
| Campaign Member | Track leads and contacts in campaigns. Campaign member spans both | Requires campaign-based tracking |
| Custom field: Original Lead ID | Stamp the Lead ID on the Contact at conversion | Enables manual linking for analysis |
| Custom field: Lead Created Date | Copy Lead Created Date to Contact at conversion | Preserves lead creation timing |

### Reporting rules

- **Copy Lead Created Date to Contact.** Without this, you lose the original lead creation date. The Contact's created date becomes the conversion date, not the original lead date. Map this field
- **Copy lead scoring data.** Lead score at conversion should be preserved on the Contact. This enables analysis of "what lead score converts to pipeline?"
- **Use Campaign Members for lifecycle reporting.** Campaign Members track both leads and contacts. A "Q1 Inbound" campaign shows the lead before conversion and the contact after, in one report

---

## Measurement

| Metric | Definition | Target | Frequency |
|--------|-----------|--------|-----------|
| Conversion rate | % of leads converted to contacts | Depends on lead quality (20-40% for MQLs) | Monthly |
| Time to convert | Average days from lead creation to conversion | Decreasing over time | Monthly |
| Data loss on conversion | % of custom fields that lose data during conversion | 0% (all fields mapped) | Quarterly audit |
| Duplicate accounts created on conversion | Accounts created that match existing accounts | 0 | Monthly |
| Post-conversion follow-up rate | % of converted leads with AE activity within 48 hours | > 90% | Weekly |

---

## Pre-Configuration Checklist

- [ ] Conversion trigger defined (what event triggers conversion?)
- [ ] Conversion trigger enforced consistently across all reps
- [ ] Every custom lead field mapped to a Contact, Account, or Opportunity field
- [ ] Lead Source field mapped to both Contact and Opportunity
- [ ] Lead Created Date copied to Contact on conversion
- [ ] Lead Score copied to Contact on conversion
- [ ] Account matching configured (check existing accounts before creating new)
- [ ] Post-conversion automation in place (task creation, notifications)
- [ ] Test conversion run with all fields verified on resulting records
- [ ] Reps trained on when to convert and how to check for existing accounts
- [ ] Reporting configured to span lead and contact lifecycle

---

## Anti-Pattern Check

- Never converting leads. 10,000 leads in Salesforce. 200 active opportunities. The opportunities are associated with leads, not contacts. Pipeline reporting doesn't work. Convert leads before creating opportunities. Always
- Converting too early. Every form fill auto-converts to a contact. Your contact database has 50,000 records, 80% of which are unqualified. Contacts should be qualified leads. Convert after human qualification
- Unmapped custom fields. Lead has ICP_Fit = Tier 1, Lead_Score = 82, and SDR_Notes = "Strong interest, budget confirmed." After conversion, all three fields are blank on the contact. Map every custom field before going live
- Not checking for existing accounts. Rep converts a lead from "Ramp." Salesforce creates a new account called "Ramp." There's already an account called "Ramp, Inc." Now you have duplicate accounts with split deal history. Train reps to search for existing accounts
- Creating opportunities on leads. An AE creates a $50K opportunity associated with a Lead record instead of converting first. The pipeline report doesn't show it. The forecast is wrong. Convert, then create the opportunity
- No post-conversion process. Lead is converted. Contact exists. Nobody follows up. The converted lead sits idle for 2 weeks. Build a post-conversion Flow: create a task, notify the AE, set a follow-up deadline
- Conversion timing varies by rep. SDR A converts at first response. SDR B converts at meeting booked. SDR C converts at opportunity creation. Conversion metrics are meaningless. One trigger, enforced consistently