Copy Related Lists and Chatter on Lead Conversion

Copy Related Lists and Chatter on Lead Conversion

In Salesforce, lead management allows your marketing and sales teams to market, qualify, and build your sales pipeline with prospective customers. Once qualified then a lead can be converted into a formal Account, Contact and (optionally) an Opportunity.

The big question addressed in this post with lead conversion is what data comes over during conversion and, more importantly, what data isn’t and how do we fix that?

What Comes Over – Standard & Custom Fields
Many of the standard lead fields are mapped during conversion to the new account and contact records, and as the administrator you can configure which custom fields from the lead are mapped (or not) to the account and contact too.

What Comes Over – Standard Related Lists
Likewise, some of the standard related lists are carried over, such as Campaigns, Activities, and Notes and Attachments, to the new account and contact.

What is left behind?
However, if your team has been using Chatter or custom related lists or using Salesforce Files (and you really should!) then, unfortunately, that data is not brought over to the account or contact upon lead conversion! So sad…

On the custom object, add a new lookup field to Contact object. As long as the record is being used on a Lead then this field will be null. It will be updated via process builder once the lead is converted into a contact.

Create process named “Lead Conversion” on Lead object and start the process when a record is created or edited.

Add a criteria that checks if the lead is converted. In the field chooser, it may be listed as Converted and once chosen display as [Lead].IsConverted:

Add an action to update records and choose the custom object’s name that has __r suffix (e.g. My_Objects__r) then configure field assignment where the custom object’s contact lookup field is assigned the value of the lead’s converted contact id:

A real-life example where I’ve used this trick is when using Survey Force (or other survey tool) that is capturing responses at the lead level but we want to carry that data over to the contact on conversion. Just as described above, I added a contact lookup field to the survey response object and used Process Builder to populate it with the lead’s converted contact id when the lead was converted. Voila, related list data follows the lead through conversion!

    • Related Articles

    • Improve performance and speed in Lightning Experience

      If you or your Users are experiencing slow page-loading times when using Lightning Experience, it may be related to one or more of the following issue types. Geographical Device Browser Salesforce organization configuration issues Please review issue ...
    • Deploying Process Builder Through Change Set

      We can understand process builder as a point-and-click apparatus that lets you effortlessly mechanize if/then trade forms and see a graphical representation of your handle as you construct. Each prepare comprises a trigger, at slightest one criteria ...
    • Lead Management Tips And Best Practices

      Companies that use Salesforce to boost their sales funnel and close more deals soon discover that they need to do more than just track sales performance and create multiple pipeline dashboards. Rather, this process begins with the creation of a ...
    • Salesforce - Sandbox Management Best Practices

      Common use cases for each type of sandbox and recommended best practices Developer - may be refreshed every day, does not include any data automatically but allows 200 MB of data to be imported or created. The most agile and plentiful sandbox type ...
    • Best Practices - Salesforce Changesets

      What are the requirements for change sets utilization? Sending of these messages necessitates a deployment connection , which means that they can be sent only, like earlier mentioned, between ventures that are affiliated to each other. However, the ...