Is it possible to specify the Opportunity Name on the Lead object itself, rather than entering it at the time of conversion? Yes; this article walks through the custom field, field mapping, and record triggered flow setup needed to populate the standard Opportunity Name field automatically when a Lead converts, based on a value entered on the Lead beforehand. It's recommended to do this testing in a Sandbox or developer environment first.
This article explains how to specify the Opportunity Name on a Lead before conversion in Salesforce. To do this, create custom fields on the Lead and Opportunity, map the fields, and use a record-triggered Flow to copy the mapped value into the standard Opportunity Name field.
It is recommended to test this configuration in a Sandbox before implementing it in Production.
Go to Setup | Object Manager | Lead | Fields & Relationships | New.
Note: It is recommended that the field not be Read-Only because users need to enter the desired Opportunity Name before converting the Lead.
Go to Setup | Object Manager | Opportunity | Fields & Relationships | New.
Go to Setup | Object Manager | Lead | Fields & Relationships | Map Lead Fields.
Under the Opportunity field mapping, map the Lead field Lead Opportunity Name to the Opportunity field Lead Opportunity Name, then click Save.
This allows the value entered on the Lead to be carried over to the custom Opportunity field when the Lead is converted.
Go to Setup | Process Automation | Flows | New Flow, then select Record-Triggered Flow.
Replace Lead_Opportunity_Name__c with the API name of the custom Opportunity field created in Step 2.
Click Activate.
The complete process works in this order:
After this configuration is activated, users can specify the desired Opportunity Name directly on the Lead before conversion. For example:
000387770

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.