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. Let’s start with a business use case.
Business Use Case
Pamela Kline is working as System administrator at Universal Containers (UC). She has received a requirement a to auto populate Account Source field on Account object from Lead Source field on the Lead object when converting a lead.
Solution for the above business requirement
There are few possible solutions for the above business scenario, but we will use the Process Builder to solve this, without creating custom fields. Follow the below instructions to create a Process for the above business requirement
1. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder and click on the New button, Enter Name, API Name and then click on the Save button.
Define Process Properties
2. The next step is to add entry criteria. For this click on Add Object, select Lead object and for the entry criteria, Select when a record is created or edited, as shown in the below screenshot, once you are done click on the Save button.
Evaluation Criteria
3. The next task is to add Process Criteria, To do this click on Add Criteria, enter Name, Type of action and set filter conditions (In this case set [Lead].IsConverted Equals Boolean True as shown in the following screenshot.
Process Criteria
4. The next step is to add an Immediate action to Process. Click on Add Action (Under Immediate actions), Select the type of action to create (In our case Record Updates), and then fill out the fields to define the action, as shown in the following screenshot.
Add Action – Record Updates
For Record Type choose ‘Select a record related to the Lead‘ as shown in the following screenshot
Select a record related to the Lead
5. Once you are done, click on the Save button, it will redirect you to Process canvas. Finally, the Process will look like the following screenshot.
Don’t forget to active the Process by clicking on the Activate button.
It’s time to test this feature
1) Navigate to the Lead tab, identify the Lead record and click on Lead Name to open record detail page, as shown in the following screenshot.
Sample Lead Record
2) Now convert the Lead, and make sure to create a new account, as shown in the following screenshot
Convert Lead
Once you are done, click on the Convert button.
Outcome :-
Converted Account
Note: – I will suggest you to implement this first on your developer org, test it and then move it to production.
13 thoughts on “Getting Started with Process Builder – Part 52 (Map Lead Source to Account Source during lead conversion)”
JD Dooley
Which related record should be used when the Salesforce Org has PersonAccounts activated? Lead.Converted Account Id or Lead. Converted Contact Id
Shayna Wilczynski
This is a great article and was very easy to implement however I’m having a problem where the account source updates when a new lead is converted and attached to an existing account. I do not want the account source to update after it’s been set. How can I do this?
Rakesh Gupta
Thanks for your feedback Shayna!
In your case, Try to add something like Account.CreatedDate=Lead.ConveretdDate, in record update filter.
Last option is to move the record update and filter part in Flow.
Shayna Wilczynski
Thanks! It works
Vipula
Can you please send the screen shot of where to add Account.create date=lead.converted date
After trying so much solutions only this solution worked for me but I dont want to change the account source value when I convert lead under the existing account.
Thanks
Vipula
Rakesh Gupta
Thank you very much Vipula for bringing this oversight to my attention.
To better manage it, I will suggest, use Flow to account record update
–> Create three Text variables LeadID, ConvertedAccountID and LeadSource
–> Now use Record Update lement to update Account Source field, as shown in the following screenshot
–> At the end,your Flow should look like the folloiwng screenshot
–> Use Flows action to trigger from the Process builder, as shown in the following screenshot
Vipula
Hi Shanaya
Can you please share the screenshot of your solution. I having the same problem where the account source updates when a new lead is converted and attached to an existing account.
Thanks
Pending to be confirmed
Dear Rakesh Gupta,
I just start to work with process builder. Currently I am trying to map lead source to account source when converting. Note: Pick-list has 10 Values.
I have been using your article as a great help. By following the instructions in the article the process works with one value, but when trying to have several values from the pick-list its states that it will only take one of the selected values.
I have tested all the possible options without luck. E.g. when adding criteria selecting choosing Any of the conditions are met (OR). Any suggestions please!
Rakesh Gupta
Could you please email me PB screenshot here info@automationchampion.com
Ty
When it’s time to select a record related to the lead, the Account object and it’s fields are not available to me. How did you get access to the Account fields?
Rakesh Gupta
Lead object is not connected with Account object. After conversion you will get the Account ID.
Jay Allen
Worth noting that Setup -> Customize -> Leads -> Lead Settings -> “Require Validation for Converted Leads” MUST be checked for process builder related items to fire during conversion. Appears that this is not checked by default.
Rakesh Gupta
You are 100% right.