Use a LinkedIn connections export without turning it into a cold list

Start with your own export

LinkedIn lets members request a copy of their connections data from Settings & Privacy. LinkedIn's current export includes first and last name, public profile URL, company, position, connection date, and an email address only when that connection has allowed it to be downloaded.

Follow LinkedIn's official export instructions and download the file on a personal computer. Do not use scraped profile data or a list purchased from someone else as a substitute.

Missing email is normal. A blank email field can reflect the connection's privacy choice. It is not a data-cleaning error to repair with guessed addresses.

Treat the CSV as a routing layer

1. Normalize employer names. Group harmless variants such as abbreviations and legal suffixes without erasing genuine company differences.
2. Match employers to current public roles. Keep the employer's own posting URL and confirm that the role is still open.
3. Review the actual relationship. A first-degree connection can be a former coworker, a brief event contact, or someone you have not spoken with in years. The CSV does not explain that context.
4. Prioritize credible paths. Give more weight to recent, relevant relationships where the person can reasonably speak to your work or the employer.
5. Choose one next action. Ask for context, request an introduction, apply directly, or leave the target alone. Not every match needs outreach.

What makes a referral request credible

A useful request makes it easy for the other person to understand the fit and to decline. Before sending anything, be able to answer:

• Which specific role or team are you asking about?
• Why is your background relevant to that work?
• What relationship context makes this request reasonable?
• Are you asking for information, an introduction, or a referral?
• Can the person say no without pressure?

One thoughtful request to a credible contact is more useful than a sequence sent to every row sharing the same employer.

Where software helps and where judgment stays manual

Software can normalize employer names, surface possible company matches, combine public hiring signals with the user's own relationship context, and keep the source role and next action visible in one workspace.

It should not claim that a company match proves a close relationship, that a connection endorses the applicant, or that a current employee will provide a referral. Those decisions remain human.