How to Export LinkedIn Leads and Sync Them to Outreach
By Theo Castellanos, AI Prospecting & Outbound Pipeline. Last updated: 2026-10-21
What can you actually export from LinkedIn?
Three routes, with different yields. Your own data export (Settings, then "Get a copy of your data") returns your connections with names, current companies and titles, and the date you connected. Email addresses come only where the member's settings share them, which for prospecting lists means: mostly not. Treat this export as a network inventory, not a contact file. Sales Navigator is where working lists live: saved leads and accounts, lead lists built against searches, and, on Enterprise tiers, CRM Sync, which keeps Navigator lists and Salesforce in step and is the only route LinkedIn itself maintains as a living sync rather than a snapshot. Lead Gen Forms and campaign exports from Campaign Manager give you the leads who converted on your ads, with the fields they submitted, the cleanest consent basis of the three. Everything else marketed as a LinkedIn export is a third party scraping the interface, with the policy exposure our safest LinkedIn automation tools analysis works through. Know which route each list came from; the route decides what the data may be used for.
Which fields matter, and what is the stable key?
Map to a fixed schema on every import, whatever the source file looked like: first name, last name, title, company, company domain where known, location, connection date or capture date, source (which route, which list, which campaign), and the LinkedIn profile URL. The URL is the field that does the work. Names repeat, titles churn, companies rebrand; the profile URL is the closest thing LinkedIn offers to a primary key, and it is what your dedupe, your suppression checks and your writeback all hang from. Normalize it on import (strip tracking parameters and trailing slashes, keep one canonical form), because the same profile arrives with three different URL decorations from three different exports, and naive dedupe reads them as three different people.
Want to put this into practice?
Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.
See Reachium →How do you map fields into the outreach tool?
Decide the mapping once, in writing, and stop re-deciding it per import. Concretely: personalization fields the sequences actually use (first name, title, company, one custom field for the signal that earned the lead a place on the list) get mapped and validated; everything else lands in a notes or custom-properties field where it can do no harm. Validate before the first send, not after: empty first names, placeholder titles and "LinkedIn Member" rows all exist in real exports, and each one becomes a visibly broken message at scale. Keep the source field sacred. When a campaign underperforms, source is the only way to learn which list, and which route, produced it. The Salesforce-side version of this discipline, keeping the revenue record straight once leads land, is in Salesforce LinkedIn revenue tracking.
How do you dedupe and suppress?
In this order, on every sync, not just the first:
- Dedupe within the file on normalized profile URL, then on email where you legitimately hold it.
- Dedupe against the outreach tool on the same keys, so a re-export never creates a second enrollment for a live contact.
- Suppress against active conversations. Anyone who has replied anywhere, is mid-sequence in another campaign, or sits in your CRM as an open opportunity or a customer gets excluded before enrollment, not discovered after a second first-touch lands.
- Suppress the permanent list: unsubscribes, hard bounces, do-not-contact requests, and competitors, maintained as data rather than as someone's memory.
Most "the tool double-messaged my prospect" stories are a step skipped in this list, usually step 3, because the conversation lived in a different system from the list.
What sync cadence keeps lists honest?
Lists decay because people change jobs. Run the sync on the cadence your volume implies: weekly for active outbound teams, with the writeback treated as half the job. Replies, bounces, unsubscribes and meeting outcomes generated inside the outreach tool must flow back to the source list and the CRM, or every future export re-imports people whose status you already learned. Where a lead magnet is the capture mechanism, the pipeline version of this loop is in LinkedIn lead magnet automation: capture, delivery, recording, sync and handoff as one designed flow rather than five manual ones. The principle generalizes: an export is a photograph; a sync with writeback is a system. Build the second, and the photographs stop mattering.
Want to put this into practice?
Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.
See Reachium →FAQ
Can you export email addresses of your LinkedIn connections?
Only where a member's privacy settings share their address with connections, which is the exception for prospecting lists. Plan as if the personal data export contains no usable emails, because for most rows it will not, and build enrichment as a separate, deliberate step.
What is the best format for importing leads into an outreach tool?
A clean CSV mapped to a fixed schema beats any native one-off import, because the mapping is reviewable and repeatable. The format matters less than the discipline: same columns, same normalization, same dedupe keys, every time.
How do you stop the same lead entering two campaigns?
Dedupe on the profile URL at import, then enforce a one-active-enrollment rule in the outreach tool against contacts already in a sequence or a conversation. Both checks are needed; import dedupe cannot see enrollments created after the import.
How often should you re-export and re-sync?
Weekly is the working cadence for active teams, with event-driven writeback in between: replies, bounces and unsubscribes should update the source records when they happen, not at the next scheduled sync.