At Albany Freight, a custom Lead field called Referral Source holds data that sales reps rely on. After leads are converted, the reps complain that the Referral Source value never appears on the resulting Account, even though a matching custom Account field already exists. What should the administrator configure so the value carries across during conversion?
- ABuild a record-triggered flow on the Account object that copies the value from the converted Lead after save.
- BAdd the Referral Source field to the Account page layout so the converted value is displayed.
- CMap the custom Lead field to the custom Account field using Map Lead Fields in the Lead object's field settings. Correct
- DCreate a validation rule on the Account requiring Referral Source to be populated before the record saves.
Why A is wrong: A flow could theoretically populate the field, but conversion field mapping is the native, maintenance-free mechanism for this exact need, so a flow is unnecessary custom work and does not run against the Lead once it is converted.
Why B is wrong: Adding the field to the layout only controls visibility; if the value is never written during conversion the field stays blank, so this addresses display rather than the missing data.
Why C is correct: Lead field mapping is the declarative setting that tells Salesforce which Account, Contact, or Opportunity field receives each custom Lead field's value at conversion, so the value transfers automatically.
Why D is wrong: A validation rule can force a field to be filled but cannot supply the value itself, so it would block conversion rather than carry the data across.