# RevOps · Post 2 — Tip

**Where to post:** LinkedIn, RevGenius Slack #tips channel,
RevOps Co-op, Modern Sales Pros.

**Format:** ~150 words. Tactical. One idea, one sentence-of-pitch
at the bottom.

---

## Title

The 30-second pre-import check that catches LinkedIn-scrape duplicates before they hit HubSpot

## Body

Before you import a LinkedIn scrape (Apollo, Lusha, Cognism — same problem) into HubSpot:

Open the file. Sort by `email`. Look for blanks.

LinkedIn-sourced rows often have *no email* — just name + company + LinkedIn URL. If you import them as-is, HubSpot creates a new contact for each one. The next time someone fills your webform with the same name + company, HubSpot creates *another* new contact, because there's no key to match on.

Two-minute fix: before import, generate a synthetic dedupe key as `lower(first_name)|lower(last_name)|domain(company_url)`. Sort by it. Anything with >1 row is a likely dupe — review and merge before HubSpot ever sees it.

If you're doing this monthly across multiple lead sources and want to automate it (plus phone normalization, fuzzy matching, the whole pipeline), I built a $49 desktop tool: datatools.app/revops. Local — your prospect list never goes to a server.

— {{your-name}}
