Turning LinkedIn Connections into CRM Contacts

You have 800 LinkedIn connections. Or 2,000. Or 4,500. And yet when you need to reach out to someone in your network — a warm intro, a job referral, a potential customer — you're starting from a search bar and hoping the algorithm surfaces the right person.

That's backwards. Your LinkedIn connections are a relationship database that you can't actually query. DenchClaw fixes that by pulling your LinkedIn network into a real database that you own and can actually use.

The Problem with LinkedIn as Your CRM#

LinkedIn is great at surface-level professional networking. It's bad at almost everything else that makes a CRM useful:

Platform lock-in. Your connections live on LinkedIn's servers. They can change what data you can see, throttle your search, or show you less of your own network based on their product decisions. You don't own your network.

No notes or context. Where did you meet this person? Why did you connect? What did you talk about? LinkedIn doesn't have fields for any of this. Your context about each relationship lives nowhere, or in some forgotten DM thread.

No relationship tracking. When did you last reach out? Did they respond? Do you have a deal or opportunity associated with this person? LinkedIn has no concept of this.

LinkedIn messaging is terrible for relationship management. It's fine for initial outreach, but ongoing relationship management via LinkedIn DMs is clunky and easy to lose track of.

The answer isn't abandoning LinkedIn. It's using LinkedIn as a data source for your actual CRM.

Step 1: Export Your LinkedIn Connections#

LinkedIn lets you export your connection data as a CSV. Here's how:

1. Go to Settings & Privacy → Data Privacy → Get a copy of your data
2. Select Connections (you can also grab Messages, but start with Connections)
3. Request the export — LinkedIn emails you a download link within ~10 minutes
4. Download the CSV

The CSV contains: first name, last name, email address (only if they've shared it), current company, current position, connected-on date, and their profile URL.

What it doesn't contain: their bio, location, photo, previous companies, mutual connections, or anything else in their profile. You get the directory, not the profiles. We'll fix that in a later step.

Step 2: Import the CSV to DenchClaw#

Send the CSV file to DenchClaw:

"Import this LinkedIn connections CSV as contacts. Set source field to 'LinkedIn Import'. Tag them all as 'linkedin-connection'."

DenchClaw reads the CSV, creates a contact entry for each row, and populates the fields it can. For connections where LinkedIn provided email addresses, those get set. For those without emails (the majority), you'll have name, company, role, and profile URL.

For a 1,000-connection export, this typically takes 30-60 seconds. Once it's done:

"How many LinkedIn contacts do I have? Show me a breakdown by current company."

Now you can actually query your network.

Step 3: Enriching LinkedIn Data with the Browser Agent#

Raw LinkedIn export data is thin. DenchClaw's browser agent can pull the actual profile content.

Because the browser agent uses your Chrome profile, it's already logged into LinkedIn as you. No bot detection issues, no fake credentials — just you, browsing your own connections' profiles.

To enrich a specific contact:

"Look up Marcus Rodriguez's LinkedIn profile and update his contact record with his current title, location, and bio summary."

DenchClaw opens Marcus's profile URL (from the import), extracts the relevant information, and updates his entry.

For batch enrichment of a subset of your connections:

"Enrich the LinkedIn profiles of all contacts tagged 'linkedin-connection' where company is 'Stripe'. Pull title, location, and a one-sentence bio summary."

This is where the value compounds. Instead of a flat CSV, you now have a rich contact database with current, accurate profile information for the contacts you care most about.

A note on rate limiting: Don't try to enrich thousands of profiles in one session. LinkedIn will notice unusual browsing patterns even with a real session. Enrich in batches of 20-50 at a time, spread across a few days.

Step 4: Adding Context from Your Connection History#

The data LinkedIn provides tells you who someone is. It doesn't tell you your relationship with them.

For each contact that matters, add your context:

"Add a note to Marcus Rodriguez: met at YC Batch interview day, 2024. We talked about his infrastructure startup. We've stayed loosely in touch. He moved to Stripe 6 months later."

For newer connections with a connection message, DenchClaw can help:

"I connected with Priya Patel on LinkedIn and she sent this note: 'Hey Mark, I saw your post about DenchClaw and would love to chat — I'm building something adjacent.' Add her as a contact with this context."

Building out the context layer is what turns a contact database into an actual CRM. The data says who they are; your notes say who they are to you.

Creating a "LinkedIn Imported" View#

Once your connections are imported and enriched, create a view that makes the data useful:

"Create a view called 'LinkedIn Network' that shows: name, current company, current role, location, connected-on date, last contact date, and my context notes."

Then you can ask questions like:

• "Who in my LinkedIn network works at Series B+ startups?"
• "Which of my connections are in San Francisco and work in fintech?"
• "Who have I connected with in the last 6 months that I haven't followed up with?"
• "Who do I know at Stripe?"

These are the queries that make your network actually useful. LinkedIn's search is optimized for profile discovery, not relationship management. DenchClaw's is optimized for the questions you actually need to answer.

Staying in Touch Without LinkedIn Messaging#

Once your connections are in DenchClaw, you don't need LinkedIn's messaging for relationship maintenance. Email is better for substantive outreach, and DenchClaw can draft those emails using the same contact context.

Set a "reconnect interval" for contacts you want to stay in touch with:

"Set a quarterly check-in reminder for all contacts tagged 'strategic' in my LinkedIn network."

When the check-in window hits, DenchClaw surfaces the person and can draft an email that references your notes and any recent activity you've seen from them (if you've tracked it).

The goal isn't to replace LinkedIn — it's great for public professional presence and discovery. The goal is to manage your relationships in a tool you own, with data you control, and queries you can actually run.

FAQ#

Will importing my LinkedIn connections violate LinkedIn's terms of service?

LinkedIn's ToS governs the use of their platform and data. Exporting your own data via their official export feature is explicitly provided as a user right. Browsing profiles through a legitimate session is standard user behavior. If you're concerned, stick to the official export without browser enrichment.

What about connections who've changed jobs since I connected with them?

The CSV will have their job at time of export. Browser enrichment will pull their current title. This is actually one of the most valuable use cases — surfacing connections who've moved to relevant companies since you last checked.

Can I keep my DenchClaw contacts in sync with LinkedIn as connections update their profiles?

Not automatically without periodic re-enrichment. Set a recurring task to re-enrich your top-priority contacts monthly or quarterly to keep data fresh.

My LinkedIn CSV doesn't have email addresses for most connections. Is it still worth importing?

Yes. Name, company, role, and profile URL plus your context notes are enough to make the database useful. Emails can be added manually or through other enrichment later.

What if someone removes me as a connection after I've imported them?

Their record stays in your CRM. Your contact database is yours, not a mirror of LinkedIn's state. The profile URL might stop working for enrichment if they've blocked you, but the record and your notes remain.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →