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.
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:
| Scenario | Recommended Object |
|---|---|
| New contact, new company, project not yet qualified | Lead |
| Known contact/account, project not yet qualified | Opportunity (low stage) |
| Known contact/account, project qualified and being pursued | Opportunity |
| Returning client with a new project, high confidence | Opportunity (skip lead) |
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.
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:
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].
Before relying on conversion to carry data forward, verify that all relevant custom fields have conversion mappings configured:
Key fields to map for most implementations:
- Prospect number
- Project name / opportunity name seed
- Source / referral information
- Any vetting scores or qualification flags
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.
If the business requires a formal approval before a lead becomes an opportunity, consider:
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.
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].