LinkedIn Data Export Guide
When To Use
You want to see your whole network in one list without a tool that logs in as you. Years of connections sit behind a search box, and the tools that offer to pull them out for you break LinkedIn's rules and put your account at risk the month you need it most. This answers: how do I get my own data, which parts do I need, and where does it live while I use it?
When Not To Use
If you already hold a clean connections file in a private place, go straight to Warm Network Map. If you only want the people who saw your work, Former Colleagues List starts from memory and needs no export.
Inputs
- What you will read the list against: your two-line brief, or your Ideal Client Profile
- Whether you want a first guess at closeness later (that decides whether you need the messages file)
- Where you will work: one private chat with file upload, or a private Project
If you have none of this, I start from the request steps alone and mark the output as a first draft.
Approach
Your own data, downloaded by you, following LinkedIn Help's page on downloading your account data. A second LinkedIn Help page, on prohibited software and extensions, rules out tools that scrape or automate the site, which is why nothing in this guide logs in as you. The judgement is in what you leave out: the export holds other people's names, sometimes their email addresses, and in the messages file their own words. The failure it prevents: a full archive dropped into a shared folder and forgotten there.
Workflow
- Ask at most three questions: do you want closeness later, will you work in one private chat or a private Project, and on what date will you delete the copy.
- Give the request steps as LinkedIn Help states them today: open the page, follow its menu path to the data download, and choose specific categories, not the full archive. Menus and delivery times change, so the plan links the help page and you note the date you asked.
- Choose the files: the connections file always. For closeness, two options, your choice: upload the messages file to your private space, or count exchanges per person yourself and bring only the count. File names are checked in your own download, not guessed.
- Leave the rest out: every category the method does not need. Fewer files means less of other people's data in your hands.
- Clean the columns: keep name, title, organisation and the date you connected. Drop email addresses unless you want them in your own private copy. Some will be missing because people chose not to share them; you do not look for them elsewhere.
- Check for work accounts: if your profile was tied to a former employer's tools, the export is still your own connections, but lists your employer gave you are not yours and stay out.
- Decide where it lives: your private chat or private Project only, never a shared space. You put the deletion date in your own calendar.
Output Format
# LinkedIn Export Plan
Requested on: [date] | Help page followed: [link, date read] | Delete by: [date I set]
## Files
| File | Use it? | Why | Kept where |
|---|---|---|---|
| Connections file | Yes | Read against my brief | [private chat / private Project] |
| Messages file, or my own count | [my choice] | First guess at closeness | [private space only] |
| Everything else | No | Not needed | Not uploaded |
## Column cleanup
| Keep | Drop |
|---|---|
| Name, title, organisation, connected on | [emails, unless kept privately], [other columns] |
## Rules for this copy
- No scraping tool, bot or extension; no tool logs in as me
- Nothing from a former employer's lists
- Never shared; deleted on [date]
## Decision
[Your name] decides by [date] which files to upload and the deletion date, then requests the export personally.
Done When
- The steps point to LinkedIn Help and the categories are chosen, not the full archive by default.
- Closeness is planned one of two ways, and you chose which.
- A private location and a deletion date are written down.
Quality Bar
- Steps come from LinkedIn's own help page; nothing about menus, timings or file names is guessed.
- Missing email addresses stay missing; no lookup elsewhere.
- Questions about holding other people's data: check with a qualified adviser.
- The plan covers the download only; reading the names is the next skill.
- Your own data, downloaded by you and kept private; nothing is scraped and no tool logs in as you.
Next
Run start-warm-network-map (Warm Network Map) to read the connections against your brief.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: start-linkedin-data-export3description: Plans how you download your own LinkedIn data and keep it private, with the request steps from LinkedIn Help, which files to use and leave out, column cleanup, where the copy lives and a deletion date. Use for "run start-linkedin-data-export", "download my LinkedIn connections", "LinkedIn data export", "export my network", "how do I get my connections file", "see my network without a scraping tool", "where do I keep my export", part of the Claude Guide for New Founders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/start-linkedin-data-export6---78# LinkedIn Data Export Guide910## When To Use11You want to see your whole network in one list without a tool that logs in as you. Years of connections sit behind a search box, and the tools that offer to pull them out for you break LinkedIn's rules and put your account at risk the month you need it most. This answers: how do I get my own data, which parts do I need, and where does it live while I use it?1213## When Not To Use14If you already hold a clean connections file in a private place, go straight to Warm Network Map. If you only want the people who saw your work, Former Colleagues List starts from memory and needs no export.1516## Inputs17- What you will read the list against: your two-line brief, or your Ideal Client Profile18- Whether you want a first guess at closeness later (that decides whether you need the messages file)19- Where you will work: one private chat with file upload, or a private Project20If you have none of this, I start from the request steps alone and mark the output as a first draft.2122## Approach23Your own data, downloaded by you, following LinkedIn Help's page on downloading your account data. A second LinkedIn Help page, on prohibited software and extensions, rules out tools that scrape or automate the site, which is why nothing in this guide logs in as you. The judgement is in what you leave out: the export holds other people's names, sometimes their email addresses, and in the messages file their own words. The failure it prevents: a full archive dropped into a shared folder and forgotten there.2425## Workflow261. Ask at most three questions: do you want closeness later, will you work in one private chat or a private Project, and on what date will you delete the copy.272. Give the request steps as LinkedIn Help states them today: open the page, follow its menu path to the data download, and choose specific categories, not the full archive. Menus and delivery times change, so the plan links the help page and you note the date you asked.283. Choose the files: the connections file always. For closeness, two options, your choice: upload the messages file to your private space, or count exchanges per person yourself and bring only the count. File names are checked in your own download, not guessed.294. Leave the rest out: every category the method does not need. Fewer files means less of other people's data in your hands.305. Clean the columns: keep name, title, organisation and the date you connected. Drop email addresses unless you want them in your own private copy. Some will be missing because people chose not to share them; you do not look for them elsewhere.316. Check for work accounts: if your profile was tied to a former employer's tools, the export is still your own connections, but lists your employer gave you are not yours and stay out.327. Decide where it lives: your private chat or private Project only, never a shared space. You put the deletion date in your own calendar.3334## Output Format35```markdown36# LinkedIn Export Plan37Requested on: [date] | Help page followed: [link, date read] | Delete by: [date I set]38## Files39| File | Use it? | Why | Kept where |40|---|---|---|---|41| Connections file | Yes | Read against my brief | [private chat / private Project] |42| Messages file, or my own count | [my choice] | First guess at closeness | [private space only] |43| Everything else | No | Not needed | Not uploaded |44## Column cleanup45| Keep | Drop |46|---|---|47| Name, title, organisation, connected on | [emails, unless kept privately], [other columns] |48## Rules for this copy49- No scraping tool, bot or extension; no tool logs in as me50- Nothing from a former employer's lists51- Never shared; deleted on [date]52## Decision53[Your name] decides by [date] which files to upload and the deletion date, then requests the export personally.54```5556## Done When57- The steps point to LinkedIn Help and the categories are chosen, not the full archive by default.58- Closeness is planned one of two ways, and you chose which.59- A private location and a deletion date are written down.6061## Quality Bar62- Steps come from LinkedIn's own help page; nothing about menus, timings or file names is guessed.63- Missing email addresses stay missing; no lookup elsewhere.64- Questions about holding other people's data: check with a qualified adviser.65- The plan covers the download only; reading the names is the next skill.66- Your own data, downloaded by you and kept private; nothing is scraped and no tool logs in as you.6768## Next69Run start-warm-network-map (Warm Network Map) to read the connections against your brief.7071## About the makers7273This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).