Skip to main content

How to deploy "Lead Mapping" also known as Lead Convert Settings

A walkthrough on how to deploy "Lead Mapping" (also known as Lead Convert Settings)

Evan Bernard avatar
Written by Evan Bernard
Updated over 3 weeks ago

How to retrieve Lead Convert Settings in Gearset

In order to deploy what many refer to as "Lead Mapping", you’ll need to include Lead convert settings metadata in your comparison filter.

You'll also need Custom field metadata (sub-component of Custom object) if the mapped fields are new in the source org/environment.

Recommended filtering options

Gearset's Compare all filter is the only default filter that includes Lead convert settings metadata.

Therefore, our suggestion is that start your comparison with On-demand comparison filter on your Compare and deploy page (image below), and from there be more granular select the metadata you want to retrieve.


What do Lead Convert Settings look like in the comparison results?

To deploy Lead Convert Settings, the mapped fields need to exist in both the source and target for your deployment to succeed.

If the Custom fields are new in the source, make sure to include them in your deployment package.

Gearset screenshot: a finished comparison showing the XML differences between the lead convert settings in the source and target orgs
Did this answer your question?