How to Push RocketReach Contacts into Salesforce Without Duplicates
Buying contact data is the easy part. Getting it into the CRM without tripling your lead records is where projects stall.
Direct answer: To move RocketReach contacts into Salesforce cleanly, export CSV with a stable unique key, import through the Data Import Wizard with duplicate rules active, and map only the fields you will actually maintain. Never import into the Lead object without a dedupe rule.
Why do duplicate records appear on the first import?
Almost always one of three reasons. The unique key differs (email present on one record, missing on the other). Salesforce’s default matching rules only match on Name and Company for leads, which is loose. Or the import creates Leads when you meant Contacts, so the same person exists in both objects.
RocketReach exports often include a LinkedIn URL. That is the most stable key you have. Set it as your external ID field before importing — it does not change the way email addresses do.
How do you set up the import properly?
Work through this in order. Skipping step two is how people end up with 4,000 duplicates by lunchtime.
- Export from RocketReach as CSV. Include the contact ID, LinkedIn URL, email, phone, title, company, and location columns. Drop anything you will not use.
- Create an External ID field in Salesforce. Setup → Object Manager → Contact → Fields → New → Text(255) → check “External ID” and “Unique”. Name it
RocketReach_ID__c. - Write a duplicate rule on Contact for email and on the External ID. Setup → Duplicate Rules → New Rule, action “Block” or “Allow with alert.” Block is safer for a first import.
- Import with the Data Import Wizard for anything under 50,000 records; use Data Loader above that. Choose “Add new and update existing” and match on the External ID field.
- Import in batches of 500. If batch three fails, you know exactly which records to roll back. Bulk API jobs are not easily reversed.
What fields are worth keeping?
Most teams over-map. Salesforce charges by record but complexity costs you in reporting.
| Field | Keep? | Reason |
|---|---|---|
| Work email | Yes | Primary outreach channel |
| Phone | Yes, if dialing | Expensive to source, cheap to store |
| Title | Yes | Needed for segmentation |
| Personal email | No | Privacy exposure, rarely used |
| Location | Optional | Useful for territory routing |
| Previous company | No | Stale within a year |
Personal email is the one people argue about. Unless your team’s legal and privacy position is clear, leave it out. It is a data-protection liability more often than a lift in reply rate.
How does this differ from live enrichment?
Static import gives you a snapshot. Live enrichment keeps it fresh.
Salesforce does not include native contact enrichment — you either buy an enrichment add-on or you push data in programme by programme. If freshness matters more than control, look at Seamless.AI or Lusha, both of which offer CRM connectors that update records rather than append new ones.
A pragmatic arrangement for smaller teams: static import quarterly for target accounts, live enrichment only for accounts actively in pipeline. That concentrates cost where it changes behaviour.
What breaks after the import?
Three things, reliably.
Ownership. Imported records land on the importing user unless you map an owner field. Every imported contact owned by the ops person becomes invisible to the reps who should work it.
Campaign attribution. Push contacts into a Campaign at import time or you lose the ability to report on source. Add a Campaign__c lookup and set it during the import.
Activity history. New records start empty. If the same person existed as a Lead with two years of call notes, merging them into a fresh Contact can orphan that history. Check before you merge.
Do you need Zapier in the middle?
Not for a CSV import. Zapier earns its place for ongoing sync — a new RocketReach list dropped into a Google Sheet triggers a Zap that upserts contacts nightly. That pattern costs a few hundred task runs a month and removes the manual step entirely.
For a one-time list, the manual import is faster and has fewer failure modes. Automate the recurring workflow, not the occasional one.
Quick Summary
- Use LinkedIn URL or a RocketReach ID as a unique External ID field — email addresses churn.
- Create a duplicate rule before importing, not after.
- Import in batches of 500 so failures are reversible.
- Map title, work email, and phone; skip personal email unless privacy is settled.
- Map Owner and Campaign at import or you lose routing and attribution.
