Lead-to-Opportunity Conversion Workflow

Overview

The lead-to-opportunity conversion process in Salesforce requires careful design to preserve data continuity, avoid duplicate records, and ensure that identifiers like prospect numbers carry forward correctly. This article captures best practices surfaced during implementation work with ^[1] and applies broadly to any Salesforce org where leads serve as a pre-qualification stage before formal pipeline entry.

When to Use Leads vs. Opportunities

The lead object is best used as a lightweight vetting stage — a place to record awareness of a potential project without triggering pipeline activity, estimating workflows, or reporting pressure. The key distinction:

Quarra Stone context: Lincoln Durham wanted leads used as a formal vetting gate — salespeople log early-stage awareness as leads, and Lincoln approves conversion to opportunity before estimating resources are engaged. However, because opportunities can also be created directly (for known clients with qualified projects), the system must support both paths.

The standard Salesforce lead object assumes a new person at a new company. When the incoming contact is already in the system, creating an opportunity at a low stage is generally preferable to creating a duplicate lead. If a pre-qualification gate is still needed for known accounts, consider using a very early opportunity stage (e.g., "Awareness" or "Vetting") rather than forcing a lead.

Prospect Number Continuity

A common requirement is a unique prospect number that follows a record from lead through opportunity (and potentially into a downstream project object). The correct implementation:

1. Generate the prospect number at lead creation. An automation (Flow or Apex trigger) assigns a unique number when a lead record is created.
2. Carry the prospect number on conversion. When the lead is converted, the prospect number field maps to the corresponding field on the opportunity. Salesforce lead conversion field mapping must be configured explicitly for custom fields.
3. Generate at opportunity if no lead preceded it. If an opportunity is created directly (no lead conversion), the same automation logic runs on opportunity creation to assign a prospect number — ensuring uniqueness across both objects.

The prospect number must be unique across the entire system, spanning both leads and opportunities. A shared custom number sequence (e.g., via a custom metadata counter or an Apex-managed sequence) achieves this.

Quarra Stone context: Prospect number generation was already working correctly on the opportunity object. The gap was that leads had no prospect number, meaning any lead-first workflow produced a gap in the numbering sequence until conversion. Sergei Logvin (Twistellar) was assigned to implement lead-level prospect number generation. See ^[2].

Lead Conversion Field Mapping

Before relying on conversion to carry data forward, verify that all relevant custom fields have conversion mappings configured:

• Go to Setup → Object Manager → Lead → Fields & Relationships
• For each custom field, check "Map Lead Fields" to ensure it maps to the correct opportunity (or account/contact) field
• Fields that are not mapped are silently dropped on conversion

Key fields to map for most implementations:
- Prospect number
- Project name / opportunity name seed
- Source / referral information
- Any vetting scores or qualification flags

Handling Existing Accounts in the Lead Object

Out-of-the-box, the Lead Company field is a plain text field — it does not look up existing account records. This creates a risk of duplicate accounts being created on conversion when the company already exists in Salesforce.

Options:
- Add a custom lookup field (e.g., "Existing Account") alongside the standard Company text field. Populate it when the lead is known to relate to an existing account. On conversion, Salesforce will use the matched account rather than creating a new one.
- Rely on conversion matching: Salesforce's conversion dialog offers the option to match to an existing account by name. This works but depends on the user recognizing the duplicate — it is not automated.
- Prefer opportunities for known accounts (see above): if the account already exists, skip the lead entirely and create an opportunity directly.

Quarra Stone context: The team identified that the Company field on leads was a required text field with no lookup capability, making it impossible to reliably associate a new lead with an existing account like a repeat architect client. Serge Koczanowski (Twistellar) noted that the standard lead model assumes a net-new company; for returning clients, creating an opportunity at a low stage is the cleaner path.

Vetting and Qualification Gates

If the business requires a formal approval before a lead becomes an opportunity, consider:

1. A vetting score or assessment section on the lead (or on an early-stage opportunity). Salesforce supports custom scoring fields that can roll up to a total score.
2. An approval process triggered when a lead is submitted for conversion, routing to the designated approver before the conversion is allowed.
3. A stage-gate on opportunities — a required field or validation rule that prevents advancing past a certain stage until a vetting checklist is complete.

Quarra Stone context: A "Project Assessment and Vetting Scores" feature was already built into the Quarra Stone org but had never been activated, because the intended approvers (Lincoln Durham, Alex Marshall, Jim Durham) had not been onboarded to Salesforce at the time of initial setup. Reactivating this feature was identified as a potential solution to Lincoln's vetting requirement without needing to restructure the lead/opportunity model. See action item assigned to Mark Hope.

Future State: Lead → Opportunity → Project

For organizations planning to extend Salesforce into project management post-sale, the full intended flow is:

Lead  →  (convert)  →  Opportunity  →  (win/close)  →  Project object
         prospect #                     prospect #        job number
         prospect folder                                   job folder

At each conversion point, relevant data and file references should carry forward. The Salesforce Project Management Tool (PMT) can be used within the Project object for post-sale execution tracking.

Quarra Stone context: A custom Project object and PMT integration are planned but not yet implemented. The immediate priority is stabilizing the lead → opportunity conversion and automating folder creation on the iDrive network share. See ^[2] and ^[3].

Related

• ^[4]
• ^[5]
• ^[6]
• ^[7]