Salesforce Lead Data Migration: How to Migrate Converted Leads
Salesforce Lead Data Migration requires careful planning when you're moving Leads that already contain converted Lead information. This can be a tricky part of the migration because Salesforce handles converted Leads differently from standard Lead records.
If you want your reports and dashboards to continue working correctly after moving to a new Salesforce org, it's important to understand how Lead conversion works and how to migrate the associated conversion information correctly.
In this guide, you'll learn what happens when a Lead is converted, which fields you need to migrate, and how to preserve converted Lead information in your new Salesforce org.
🔄 Salesforce Lead Data Migration: Understanding Lead Conversion
When a Lead is converted in Salesforce, Salesforce can create three related records:
The Account represents the company, the Contact represents the individual, and the Opportunity can be used to track the potential sale.
For example, imagine you have a Lead named Coral Benedite, who works for a company called Pro Dynamics.
When Coral's Lead is converted, Salesforce can create:
Salesforce then stores the IDs of these newly created records as part of the converted Lead information.
What Happens When a Lead Is Converted?
When a Lead is converted, Salesforce can create an Account, Contact, and Opportunity from the original Lead.
Salesforce also stores information about these converted records on the Lead. This information becomes important when migrating converted Leads in Salesforce.
Why Does This Matter?
During a Salesforce-to-Salesforce migration, you don't want to lose the relationship between the original Lead and the records created during its conversion.
If the converted Lead information is not migrated correctly, reports and dashboards that depend on this information may no longer work as expected.
📊 Salesforce Lead Data Migration and Reporting
One of the main reasons to preserve converted Lead information is reporting.
Salesforce provides the Leads with Converted Lead Information report type, which allows you to report on Leads and their conversion information.
A Salesforce report type designed to report on Lead conversion data.
For example, a report can initially display all Leads, including both converted and unconverted records.
You can then apply a filter to show only converted Leads.
This is especially important when recreating reports and dashboards in a new Salesforce org.
If your source org relied on converted Lead information, preserving these fields during migration helps your reports and dashboards continue to populate as expected.
⚠️ Limitation of Salesforce Lead Data Migration
There is an important limitation to remember when migrating converted Leads.
Conversion fields on the Lead object are only accessible when inserting new Lead records.
This means you cannot simply import your Leads first and then update existing Leads later with their conversion information.
You cannot rely on a later update to add the converted Lead information to existing records.
Insert all 500 Leads first and then update the 200 converted Leads with their conversion fields afterward.
Include the appropriate conversion information for the converted Leads during the initial insert.
If converted Lead information was not included during the original insertion, those records may need to be deleted and reinserted with the correct conversion information.
Plan your converted Lead data before performing the import. Adding the conversion fields during the initial insert can prevent the need to redo the migration.
📋 Fields Required for Converted Leads
Your migration file needs to include several additional fields to preserve converted Lead information.
IsConverted
ConvertedDate
ConvertedAccountId
ConvertedContactId
ConvertedOpportunityId
These fields provide Salesforce with the information needed to recreate the converted Lead status in the destination org.
🗂️ Preparing Your Salesforce Lead Data Migration File
Before loading the data into your new Salesforce org, review your source file carefully.
Your file should identify which Leads have been converted and include the appropriate conversion information for those records.
A simplified example might look like this:
| Lead | IsConverted | Converted Date | Account ID | Contact ID | Opportunity ID |
|---|---|---|---|---|---|
| Coral Benedite | TRUE |
2026-01-15
|
001XXXXXXXX
|
003XXXXXXXX
|
006XXXXXXXX
|
| John Smith | FALSE | — | — | — | — |
🔑 Important: The exact IDs and values will depend on your source Salesforce org.
✅ Before Importing, Check:
🚀 Loading Converted Leads into the New Salesforce Org
Once your data file is prepared, you can continue with your normal Salesforce data-loading process.
During the import, make sure the appropriate Lead fields are mapped to the corresponding fields in the destination Salesforce org. The goal is to preserve the converted Lead information so that Salesforce can recognize those Leads as converted and maintain the information needed for reporting.
🔍 Verify the Migration
After loading your Leads into the new Salesforce org, don’t immediately consider the migration complete.
Take time to verify the results.
Check the Following:
Use this checklist to validate converted Lead information after migration.
💡 Key Takeaway
These fields carry important conversion information into the new Salesforce org.
By including these fields, you can carry important conversion
information into your new Salesforce org and help maintain the
functionality of reports and dashboards that depend on that data.
A little preparation before the migration can save significant time later.
Want to see the process demonstrated?
Watch the Salesforce training lesson:
▶️ Understanding Converted Leads in Salesforce Data Migration❓ Frequently Asked Questions
When a Lead is converted, Salesforce can create an Account, Contact, and Opportunity. The original Lead retains information about these converted records.
No. Converted Lead fields need to be populated when the Lead is initially inserted. They cannot simply be added later through a standard update.
For converted Leads, your migration file should include:
-
IsConverted -
ConvertedDate -
ConvertedAccountId -
ConvertedContactId -
ConvertedOpportunityId
Preserving converted Lead information allows reports using Leads with Converted Lead Information to continue showing the appropriate Account, Contact, and Opportunity relationships.
📊 This is especially important when recreating reports and dashboards in a new Salesforce org.If converted Lead information is not included during the initial insert, you may need to delete and reinsert the affected Leads with the correct conversion fields.
Not necessarily. Salesforce can convert a Lead without creating an Opportunity, depending on how the conversion is performed.
In those cases, the ConvertedOpportunityId may not be populated.
After the import, check the Lead conversion status and verify the associated Account, Contact, and Opportunity information.
You should also run your existing reports and review dashboards to confirm that they are displaying the expected data.
Yes. Salesforce Data Loader can be used to insert large volumes of Lead records and map the required Lead fields during a migration.
The biggest mistake is treating converted Lead fields like normal fields that can be updated later.
🔑 Plan and map the conversion information during the initial Lead insertion.Ready to Take Your Salesforce Lead Skills Further?
Want to go beyond Lead fields and understand more about Salesforce data migration, field mapping, and real-world Salesforce workflows? Explore more practical Salesforce training with Salesforce Masterclass.
Can You Migrate This Lead Correctly?
Test your knowledge of converted Lead data before moving it into another Salesforce org.
Which field tells Salesforce that this Lead was converted?
Migration Check Complete!
You completed the converted Lead migration challenge.