Last Updated on March 3, 2022 by Rakesh Gupta

Big Idea or Enduring Question:

• How can you map the lead source to the account source during the lead conversion?

A lead in a marketing context, is a potential sales contact, an individual or organization that expresses an interest in your products or services. Leads are typically captured through the referral of an existing customer, or direct through the company website (Using web-to-lead), etc. Usually, leads are converted when they have been identified as qualified sales prospects.

During conversion, the information from the standard lead fields appears in standard fields for contact, account, and opportunity records. A lead source is mapped to contact and opportunity lead source. It means the standard Lead Source field on the Lead object is not mapped automatically to the Account Source field on the Account object when converting a lead.

Objectives:

This blog post will help us to understand the following

• Map lead field to multiple objects fields (account, contact, or opportunity)during lead conversion
• How you can update the converted account fields

Business Use case

Pamela Kline is working as a System administrator at Universal Containers (UC). She has received a requirement from the management to auto-populate the Account Source field on the Account object from the Lead Source field on the Lead object when an account is created from lead conversion.

Automation Champion Approach (I-do):

There are multiple solutions possible for the above business scenario. We will use Salesforce Flow to solve the above business requirement.

To solve this requirement, we will use the After-save Record-Triggered Flow. Check out this article to understand why we are using after-save record-triggered flow for this scenario.

Before discussing the solution, let me show you a diagram of a Process Flow at a high level. Please spend a few minutes going through the following Flow diagram and understand it.

Let’s begin building this automation process.

Guided Practice (We-do):

There are 3 steps to solve Pamela’s business requirement using Record-Triggered Flow. We must: 

1. Define flow properties for record-triggered flow
2. Add a decision element to check if the lead is converted
3. Add an update records element to update the account source on the account

Step 1: Define Flow Properties

1. Click Setup.
2. In the Quick Find box, type Flows.
3. Select Flows then click on the New Flow.
4. Select the Record-Triggered Flow option, and click on Create and configure the flow as follows:
   1. Object: Lead
   2. Trigger the Flow When: A record is created or updated
   3. Set Entry Criteria
      1. Condition Requirements: None
   4. Optimize the Flow For Action and Related Records
5. Click Done.

Step 2: Using Decision Element to Check if Lead is Converted

Now we will use the Decision element to check, if the lead is converted. Remember, once a lead gets converted, you can view it on the UI unless you have permission to view converted leads.

1. On Flow Designer, click on the +icon and select the Decision element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Under Outcome Details, enter the Label the API Name will auto-populate.
4. Condition Requirements to Execute Outcome: All Conditions Are Met (AND)
   1. Row 1:
      1. Resource: {!$Record.IsConverted}
      2. Operator: Equals
      3. Value: {!$GlobalConstant.True}
5. When to Execute Outcome: Only if the record that triggered the flow to run is updated to meet the condition requirements
6. Click Done.

Step 3: Update Account Source on Account into which the Lead Converted

The next step is to update the account field on the Account object.

1. On Flow Designer, click on the +icon and select the Update Records element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. For How to Find Records to Update and Set Their Values select Specify conditions to identify records, and set fields individually
4. Object: Account
5. Select All Conditions Are Met (AND).
6. Set Filter Conditions
   1. Row 1:
      1. Field: Id
      2. Operator: Equals
      3. Value: {!$Record.ConvertedAccountId}
7. Set Field Values for the Account Records
   1. Row 1:
      1. Field: AccountSource
      2. Value: {!$Record.LeadSource}
8. Click Done.

In the end, Pamela’s Flow will look like the following screenshot:


Once everything looks good, perform the steps below:

1. Click Save.
2. Enter Flow Label the API Name will auto-populate.
3. Click Show Advanced.
4. Type: Record-Triggered Flow
5. API Version for Running the Flow: 54
6. Interview Label: Record-triggered: Lead After Save Flow {!$Flow.CurrentDateTime}
7. Click Save. 

Almost there! Once everything looks good, click the Activate.

Proof of Concept

Now onwards, if a business user converts a lead, then the record-triggered flow will automatically populate the lead source on account from the converted lead. 

1. Navigate to the Lead tab, identify the Lead record and click on Lead Name to open the record detail page, as shown in the following screenshot:
2. Now convert the Lead. Now open the newly created account record and verify the Lead Source.

Formative Assessment:

I want to hear from you!

What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.