Link Leads Blog · November 3, 2026

How to import an aged insurance lead CSV into your CRM without duplicate contacts

The file downloads clean. What happens when it lands in a CRM that already has thousands of contacts in it is a separate problem, and most of the ways it goes wrong happen before anyone picks up a phone.

The file is clean; your CRM isn't empty

A delivered lead file is deduplicated against itself — no record appears twice inside the CSV you download. That's a different claim from "no record in this file already exists in your CRM." If you've bought aged leads before, run organic prospecting, or just have a pipeline with a few thousand contacts in it, some share of any new state-and-age order is going to overlap with people already sitting in your system from a prior list, a referral, or a past campaign. Import the new file as a flat batch of new contacts and you get duplicate records for the same person — which means duplicate dial attempts, a disposition history that's now split across two contact cards, and a dialer that treats the same cell number as two different leads to call.

What's actually in the file

Every record in an SMS lead order is first name, last name, state, ZIP code, a validated 10-digit cell number, and age. There's no email field on this product line — that's the email lists, a separate order. That matters for how you dedupe: the only field on the file that's unique per person and stable over time is the phone number. Name alone isn't reliable (plenty of "Michael Smith"s in a 10,000-row file), and ZIP plus age narrows things but doesn't uniquely identify anyone. Phone number is the join key for everything that follows.

Map the columns, then add two fields that aren't on the file

The six delivered columns map one-to-one onto standard contact fields — first name, last name, state, postal code, mobile phone, and a custom "age" field if your CRM doesn't have one. Before you run the import, add two more custom fields to the mapping that don't exist on the CSV itself: an "import batch" field (the order date, or a batch ID you assign) and a "lead source" field tagging it as a Link Leads aged order. Neither shows up anywhere a contact can see it — they're there so that six months from now, when you're deciding whether to reorder the same state and age range, you can filter your own CRM by batch and exclude everyone already in the pipeline instead of guessing. The order builder also has a no-repeats option that excludes your own past orders at the source, but it only knows what you've bought from us — it can't see contacts that got into your CRM some other way, which is exactly what the batch tag is for.

Fix the phone column before you map anything

If the CSV gets opened in Excel or Sheets before it's imported — to skim it, filter it, or hand a slice to another agent — there's a specific way this goes wrong: a spreadsheet that auto-detects a 10-digit cell number as a number instead of text will sometimes format it with a thousands separator, drop it into scientific notation on a wide column, or silently truncate a number that got re-typed or copy-pasted. None of that is visible until the CRM rejects the row or, worse, imports a phone number that's now one digit short and un-dialable. The fix is to force the column to text before you touch it: in Excel, format the phone column as Text (or re-import the CSV through Data → From Text/CSV and set that column's type explicitly) before you save or edit anything. If you're not editing the file at all, skip the spreadsheet step entirely and import the CSV straight into the CRM — the fewer hands that touch the number before it's mapped, the fewer ways it gets corrupted.

Set the dedupe rule to match on phone, not name or email

Most CRMs default their duplicate-detection rule to email match, because that's the reliable key for most B2B import workflows. On a phone-only file, that default rule does nothing — it will never flag a duplicate, because neither record has an email address to compare. Before the import, go into the CRM's duplicate-management settings and add (or switch to) a rule that matches on the phone field, normalized to digits only so formatting differences — parentheses, dashes, a leading "1" — don't create a false negative. That one setting change is the difference between an import that merges new activity onto an existing contact and one that quietly doubles your contact count every time you reorder the same state.

Scrub before you import, not after

Importing first and scrubbing later means dead and landline numbers sit in your CRM looking identical to callable ones, and whatever workflow or sequence triggers off a new contact being created fires on all of them. Run the DNC and landline/wireless check on the raw CSV before it goes anywhere near the CRM, and bring the scrub result in as its own field on import — a simple "scrub status" column — so a record that came back flagged is visibly different from one that's clear, instead of indistinguishable until someone dials it. We recommend Landline Remover for this (disclosure: that's an affiliate link and we may earn a commission if you sign up through it) — it takes a CSV in and hands back the same file flagged for landlines and DNC matches, which is the version worth mapping into the CRM.

Carry disposition and priority fields into the same import

While you're building the field mapping, add the columns your calling workflow will need on day one rather than bolting them on after the first batch is already in the system: a disposition field using a consistent code set (see our disposition-code post for a nine-code structure that routes a record back into rotation or out of the pool) and a dial priority field if you're scoring the list before working it (our lead-scoring post covers what to weight). Both are empty on import — they get written by whoever works the list — but they need to exist as fields before the first call happens, or you end up retrofitting a schema onto thousands of contacts that already have call history attached.

What changes on a monthly plan

A subscription delivers the same states and age range every billing cycle, so the import stops being a one-off setup task and becomes a recurring one. Once the field mapping, the phone-based dedupe rule, and the batch tag are set up correctly the first time, each new monthly file runs through the same mapping — the only thing that changes month to month is the batch ID, which is what lets you tell this month's contacts apart from last month's inside a CRM that now has several overlapping imports in it.

Build the file this import runs on

Link Leads sells SMS and email lead lists at a flat $0.012 per lead, minimum order 5,000 leads ($60), filterable by state and age band (18–64), deduplicated, and delivered as an instant CSV. Build an order in the order builder, or pull a free 100-row sample first to test your field mapping and dedupe rule against before you spend anything on a full order.

These are aged data leads (not consented insurance-form leads) and are not DNC-scrubbed. Buyers are responsible for DNC scrubbing and dialing/texting compliance.