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.
This article answers the question: how do you use a Salesforce Record-Triggered Flow on the Lead object to automatically update a converted Opportunity when its original Lead is updated? The steps cover the required permission, the custom fields, the flow configuration, testing, and alternative approaches.
To edit converted Leads, ensure that the user has the View and Edit Converted Leads permission enabled.
On the Opportunity object, create two fields to be synchronized under Setup > Object Manager > Opportunity > Fields & Relationships.
Use a Record-Triggered Flow that updates a converted Opportunity with a value from its original Lead.
When the Flow Builder page appears, configure it as follows.
Notes:
| Setting | Value |
|---|---|
| Object | Lead |
| Trigger the Flow When | A record is updated |
| Condition Requirements | All Conditions Are Met (AND) |
The Condition Requirement should be as follows:
| Field | Operator | Value |
|---|---|---|
| Converted Opportunity ID | Is Null | False |
| Setting | Value |
|---|---|
| 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 |
Add an Update Records element that updates the Opportunity whose ID equals the Converted Opportunity ID of the triggering Lead record.
Notes:
When specifying the resource type, select Formula and define it as follows. Data Type: Text. The formula returns the text "True" when the Lead checkbox is checked and "False" when it is not.
IF( {!$Record.IsBusinessEmail__c}, "True" , "False" )
The Update Records element then appears 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.
Mapping requirements:
Or add the Lead field directly to the Opportunity Lightning Page:
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.