0

I've built a visual flow that will take a lead and turn it into an account, contact, opportunity, and sometimes some other related custom objects and all with duplicate detection. When the lead is created the flow checks that the lead has all of the necessary information and if so does all of those things. If not, then a rep will be able to launch the flow via a button. No one uses the standard Convert functionality.

I've recently noticed that none of my leads have the isConverted boolean set to true, so I'm trying to figure out if there is something functionality I'm missing out on as a result of this.

As far as I can tell, leads with isConverted set to true:

  • Cannot be edited
  • Cannot be searched for

unless you have the permission "View and Edit Converted Leads"

Is there something else I'm missing out on?

1

The system's lead conversion process does two things decently well. First, it automatically converts standard types of data for you, such as moving tasks and campaign information from the lead to the contact and opportunity. This means some of your flow might be doing duplicate work that could have been saved by default functionality. Second, it provides some canned reports that include things like lead conversion rates and ROI reports. This also tangentially leads to other benefits if you're using Einstein Scoring systems, such as predicting the win rate of a given opportunity or lead, etc. Your leads won't be properly scored without this lead conversion process, thus resulting in inaccurate data.

If you don't care for all the extra bells and whistles that the canned conversion process provides, then that's fine. You should simply be aware that by eschewing this process, you're losing out on the future potential benefits of reporting and Einstein Analytics. These features may or may not be useful to you in the future, and certainly some random person on the Internet shouldn't presume to know your business model and organization's needs.

That said, perhaps a hybrid approach is warranted. You could perform the conversion as part of the flow in order to preserve future analytics, and use the flow to fill in the gaps that standard functionality doesn't offer. I won't presume to know too much about your current process, but perhaps it could be as simple as a drop-in InvocableMethod that simply performs the actual conversion and maps the account, contact, and opportunity data back in to the flow to finish up the process.

In our org, for comparison, we have a custom lead conversion page (and soon a Lightning Component) that does a lot of custom conversion, but also calls the standard Database.convertLead function. We use Lead Scoring and Opportunity Scoring, though, so that was an important thing for us to implement to get our analytics correct. We use a hybrid approach that I mentioned in the previous paragraph to give us the flexibility we want while retaining all of the benefits of standard conversion.

| improve this answer | |
  • 1
    you also get lead field mapping rules (declarative) to account, contact, opportunity with the OOTB lead convert – cropredy Apr 3 at 5:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.