This article focuses on Lead-Opportunity synchronization, but the same approach can be applied to any related converted objects. In Salesforce, the Converted Opportunity ID is located on the Lead, which deviates from a conventional database model where the Id would typically reside on the child or related object. This distinction influences the condition entries employed.
Prerequisite : To edit converted Leads, ensure that the user has the View and Edit Converted Leads permission enabled.
Step 1: Assign the View and Edit Converted Leads permission to the user using a Permission Set
Step 2: Create a Custom Field on Lead object
Step 3: On the Opportunity object, create two fields to be synchronized under Setup > Object Manager > Opportunity > Fields & Relationships
One Checkbox field Boolean IsBusinessEmailOnLead__c, which will be of the same data type as the field created on the Lead object
Step 4: Leverage a Record-Triggered Flow that would update a converted Opportunity, with a value update from its original Lead
Step 5: When the Flow Builder page appears, configure it as follows
Notes:
| Object | Lead |
| Trigger the Flow When | A record is updated |
| Condition Requirements | All Conditions Are Met (AND) |
The Condition Requirement should be as follows:
| Converted Opportunity ID | Is Null | False |
| When to Run the Flow for Updated Records | Every time a record is updated and meets the condition requirements |
|
Optimize the Flow for
| Actions and Related Records |
Step 6: Add an Update Records element, that will be in charge of updating the Opportunity whose ID equals to the Converted Opportunity ID of the triggering Lead record
Notes:
When specifying the resource type, select Formula. Define it as follows:
IF( {!$Record.IsBusinessEmail__c}, "True" , "False" )
The Update Records element will appear as follows:
Note: The Flow can also be enriched with Fault Paths or error handling. To further enhance security during build and deployment, consider creating Flow test scenarios
Step 7: Save and Activate the Flow
Step 8: Test our Flow and verify Opportunity synchronization with Lead
Alternative approaches that could be considered when working with Leads
A. Lead Conversion mapping
Mapping Requirements:
B. Directly point to the Lead Field Value
Or
Directly add the Lead field to the Opportunity Lightning Page
Edit the page from an Opportunity record page, or Setup > Object Manager > Opportunity > Lightning Record Pages or, use Page Layouts if Lightning Pages haven't been leveraged for this object
Click Upgrade Now on the layout to switch to a Dynamic Form if it's not already
From the left panel, select the Fields tab
Select Original Lead
Then select the Is Business Email Lead field to display on the Opportunity
Save and Assign the new Lightning Record Page to the relevant Applications or Profiles
C. Leverage a Screen Flow or a LWC (Lightning Web Component)
_____________________________________________________________________________
- Salesforce Help: Convert Leads
https://help.salesforce.com/s/articleView?id=sf.leads_convert.htm
- Salesforce Help: Record-Triggered Flows
https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger_record.htm
- Salesforce Help: Permission Sets Overview
https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm
- Salesforce Help: Map Lead Fields for Lead Conversion
https://help.salesforce.com/s/articleView?id=sf.customize_leadconvert.htm
- Trailhead: Flow Builder
https://trailhead.salesforce.com/content/learn/modules/flow-builder
- Salesforce Developer Docs: Lightning Web Components
https://developer.salesforce.com/docs/component-library/overview/components
005185010

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.