How to import LinkedIn Connections data into Salesforce Leads
When you download your LinkedIn data, you get a Connections.csv file. This template maps the export to Salesforce's standard lead fields: names, email, company, job title, and the LinkedIn profile URL. The URL column maps to the custom LinkedIn_URL__c Lead field, so create that field on the Lead object in Salesforce before importing, or repoint the mapping in the column mapper. Lead Source is set to LinkedIn and Status to Open - Not Contacted on every row. Emails are lowercased and name fields are title-cased. One thing to know before you start: LinkedIn only includes the email of a connection who turned on email sharing, typically 10 to 30 percent of rows, so most rows land in Salesforce without an email. The Connected On date has no native Salesforce Lead field; the Columns we don't use section covers it.
Field-by-field mapping
This is the complete column mapping from LinkedIn Connections to Salesforce Leads. The left column is the header in your CSV export. The right column is the Salesforce Leads field it should map to.
| First Name | First NameFirstName | |
| Last Name | Last Name*LastName | |
| Email Address | Email LinkedIn only includes the email of a connection who turned on email sharing, typically 10 to 30 percent of rows. Blank rows still import as leads but reps will need to find an email elsewhere. TransformLowercased and trimmed | |
| Company | Company* Salesforce requires a Company on every Lead. Rows without a company name will not import. | |
| Position | Title | |
| URL | LinkedIn URLLinkedIn_URL__c Maps to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Lead object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead. | |
| "LinkedIn" | Lead SourceLeadSource Set on every row. Change the value, or remove it, in the column mapper if your process records lead source differently. | |
| "Open - Not Contacted" | Lead StatusStatus Set on every row. This is Salesforce's standard new-lead status. If your org renamed its Lead Status picklist, change the value in the column mapper to match before you run the job. |
Required by Salesforce Leads.
Columns we don't use
Your LinkedIn Connections export includes 1 column this template doesn't map. Each one below explains why, plus the workaround if you want the data in Salesforce Leads.
- Connected On
Salesforce Leads have no native field for the date a LinkedIn connection was made. Salesforce's own CreatedDate is set when the lead is created in Salesforce.
If you need it. Add a custom date field to the Salesforce Lead called LinkedIn Connected On, then map this column to it by hand in the column mapper.
Formatting and cleanup
LinkedIn Connections exports rarely match the format Salesforce Leads expects. Fix these before you import.
- 1.Lowercases and trims email addresses
- 2.Maps URL to the custom LinkedIn_URL__c Lead field
- 3.Sets Lead Source to LinkedIn and Status to Open - Not Contacted on every row
- 4.Title-cases name fields
- 5.Trims whitespace and removes blank rows
Or skip the manual work
Operelio runs this cleanup and mapping for you. Upload your LinkedIn Connections export and download a clean, import-ready file for Salesforce Leads.
LinkedIn Connections to Salesforce Leads FAQ
How do I export my LinkedIn connections data?
Go to Settings, Data Privacy, Get a copy of your data, select Connections, and request the download. LinkedIn will email you when the file is ready.
Why are most email addresses blank?
LinkedIn only includes the email of a connection who turned on email sharing in their privacy settings, typically 10 to 30 percent of rows. Connections without a shared email still import as leads, they just won't have an email until a rep finds one. Dedupe on the LinkedIn URL rather than email if you import more than one export, since email is too sparse to match on.
What happens if Company is blank for some connections?
Salesforce requires a Company value for every lead, so it will reject any row with a blank Company field during import. LinkedIn fills Company on most rows, but spot-check your CSV before upload, or fill blank cells with a placeholder like Unknown and update in Salesforce after import.
Why doesn't the Connected On date transfer to Salesforce?
Salesforce Leads have no native field for the date a LinkedIn connection was made, so the template leaves Connected On unmapped. The Columns we don't use section below shows you how to add a custom date field and map it if you need the connection date.
Does this template handle the LinkedIn profile URL?
Yes. The URL column is mapped to a custom Salesforce field called LinkedIn_URL__c. Create that field on the Lead object in Salesforce before importing, or open the mapping in Operelio and point the column at a different field instead.
Will this create duplicate leads?
Salesforce checks for duplicates based on your org's matching rules. Because most LinkedIn rows have no email, email-based rules won't catch repeats, so dedupe your CSV on the LinkedIn URL before import and review your duplicate settings in Salesforce Setup.