Question

Difficulty: HardLead Lifecycle and Lead Conversion

A financial services institution is auditing its Salesforce lead lifecycle process to ensure data integrity during lead conversion. Arrange the following execution events in the correct chronological sequence from the moment an administrator or sales rep clicks the 'Convert' button on a Lead record.

  1. 1Salesforce evaluates validation rules on the Lead record.
  2. 2Target Account, Contact, and optional Opportunity records are instantiated and saved.
  3. 3Custom Lead field values populate corresponding mapped custom fields on the created target records.
  4. 4The Lead record is set to converted status (`IsConverted = TRUE`) and becomes read-only.
  5. 5Triggers, Flow automations, and validation rules execute on the newly created Account, Contact, and Opportunity records.

Answer

The correct chronological sequence is: (1) Salesforce evaluates validation rules on the Lead record, (2) Target Account, Contact, and optional Opportunity records are instantiated and saved, (3) Custom Lead field values populate corresponding mapped custom fields on the created target records, (4) The Lead record is set to converted status (IsConverted = TRUE) and becomes read-only, and (5) Triggers, Flow automations, and validation rules execute on the newly created Account, Contact, and Opportunity records.
The correct order follows Salesforce's internal execution model for lead conversion: Lead validation rules evaluate first to verify source data; next, destination Account, Contact, and Opportunity records are created; mapped custom Lead fields populate those target records; the original Lead record updates to IsConverted = TRUE and becomes read-only; and finally, automations and validation rules on the newly created target objects execute.

Step-by-Step Solution

1
Identify the initial pre-conversion validation phase
Lead validation rules run first to prevent conversion if mandatory Lead fields fail validation.
Salesforce ensures data quality on the source record prior to generating downstream destination records.
2
Identify destination object instantiation
Target Account, Contact, and Opportunity records are created or linked.
Core relational structures must exist in the database before field values can be populated.
3
Trace data transfer via custom field mapping
Mapped Lead fields write their values to Account, Contact, or Opportunity custom fields.
Custom Lead Field Mapping executes during target record field assignment.
4
Determine source record status transition
The Lead record is marked as converted and locked from editing.
The system flags `IsConverted = TRUE` to complete the Lead lifecycle stage transition.
5
Determine post-conversion automation execution
Target object automations (Flows, triggers, and validation rules) execute.
Newly created destination records fire their respective object-level execution logic upon insertion.

Key Concept

Salesforce Lead Conversion Order of Execution
Rate this question