- Every external list has quality issues. Importing before cleaning creates duplicates, breaks automations, damages sender reputation, and inflates pipeline numbers.
- The cleaning order matters: audit the file, remove junk rows, standardise formatting, deduplicate, validate emails and phones, strip formula injections, then map fields to your CRM schema.
- Teams that build this into a repeatable workflow spend minutes per import instead of hours per week fixing downstream problems.
You’ve got a list. Maybe it came from a webinar platform, a Sales Navigator export, a purchased database, or a spreadsheet a colleague sent over Slack with the subject line “leads - pls upload.”
Whatever the source, you’re about to import it into your CRM. And this is the moment where most teams make a mistake that costs them weeks of cleanup later: they import first and clean up after.
That’s backwards. Every dirty record you push into your CRM creates downstream problems - broken automations, duplicate contacts, bad routing, inflated pipeline numbers, and reps wasting time on leads that were never real in the first place.
This guide walks through how to clean a lead list properly before it goes anywhere near your CRM.
Why cleaning before import matters
It’s tempting to skip this step. The list is sitting there, your reps want leads now, and your CRM has deduplication rules anyway - so what’s the worst that can happen?
Quite a lot, actually.
Duplicates compound fast
Your CRM’s native deduplication is usually based on exact email matches. But dirty lists create near-duplicates - same person, slightly different name formatting or job title, different email alias. Those slip through and multiply every time someone uploads another list. Within a few months, your CRM has three records for the same person, each with different activity history, and your reps are stepping on each other’s toes.
Bad data breaks automations
If a phone number field contains text instead of digits, or a country field has six different formats for “United Kingdom,” your sequences, lead scoring, and routing rules will misfire. Automations are only as reliable as the data they run on.
Reporting becomes unreliable
When your CRM is full of duplicates, incomplete records, and inconsistent formatting, every report you pull is wrong. Pipeline numbers are inflated. Conversion rates are skewed. Territory counts are off. And leadership starts making decisions based on data that doesn’t reflect reality.
Sender reputation takes a hit
Importing unverified emails and blasting them through your outbound sequences is the fastest way to damage your domain’s sender reputation. High bounce rates tell email providers you’re not managing your list hygiene, and once your domain is flagged, it affects deliverability across every campaign - not just the one with bad data.
Compliance risk increases
Importing records without checking consent status, region, or do-not-contact flags puts your team on the wrong side of GDPR, PECR, and other data regulations. A clean import process should catch these issues before they become problems.
The cleaning checklist: step by step
Here’s the process, in the order that tends to produce the best results. Each step builds on the one before it, so resist the urge to skip ahead.
1. Audit the raw file first
Before you change anything, open the file and look at it. Not a quick scroll - an actual audit. You want to understand what you’re working with before you start fixing things.
Ask yourself a few questions. How many rows are there? What fields are included? Are there obvious gaps - columns that are mostly empty? Are there rows that are clearly junk (test entries, internal emails, blank names)? Is the formatting consistent, or does it look like three different sources were pasted together?
This step takes five minutes and saves you from running a cleaning process on a file that should have been thrown out or split up first.
2. Remove obviously bad rows
Start by deleting records that are clearly unusable. That includes rows with no name or no company, internal or personal email addresses (unless you’re specifically targeting those), test entries like “asdf” or “test test,” records with no way to identify the person or organisation, and any rows that are clearly outside your ICP - wrong geography, wrong industry, wrong company size.
Don’t overthink this step. You’re not filtering for quality yet - you’re removing noise so the rest of the process runs cleaner.
3. Standardise field formatting
This is where most of the actual cleaning work happens. Inconsistent formatting is the single biggest source of downstream CRM problems, and it’s almost always present in lists that come from external sources.
Names - Strip extra whitespace, fix capitalisation (all caps, all lowercase, random mixed case), and separate first and last names into distinct fields if they’re combined. Watch for titles and suffixes jammed into name fields (“Mr John Smith MBA”).
Email addresses - Convert everything to lowercase, trim whitespace, and remove any rows where the email field contains something that clearly isn’t an email. Don’t try to validate deliverability at this stage - that comes later.
Phone numbers - Standardise to a consistent format. For UK numbers, that usually means E.164 format (+44 followed by the number with no spaces, brackets, or leading zero). Remove any entries that are obviously incomplete or contain text characters.
Company names - This one is deceptively tricky. “Acme Ltd,” “Acme Limited,” “ACME LTD,” and “acme” are all the same company, but your CRM will treat them as four different records. Standardise suffixes (Ltd, Limited, Inc, PLC), fix capitalisation, and remove unnecessary punctuation.
Job titles - Normalise variations where possible. “VP of Sales,” “Vice President, Sales,” “VP Sales,” and “Vice President of Sales” should all resolve to the same thing if you want your filters and routing rules to work.
Location fields - Pick a format and stick with it. “UK,” “United Kingdom,” “GB,” and “Great Britain” should all be one value. Same for city names, regions, and postcodes.
4. Deduplicate
If you’re importing specifically into HubSpot, how to clean a CSV before uploading it to HubSpot covers HubSpot-specific steps in detail.
Once formatting is consistent, deduplication becomes much more reliable. If you standardised company names and email formats in the previous step, your duplicate detection will catch matches it would have missed before.
Start with exact email matches - those are definitive duplicates. Then look for fuzzy matches: same name and same company with different emails, or same phone number across multiple rows.
When you find duplicates, don’t just delete the extras. Merge them. Keep the most complete record and pull in any unique data points from the others. If one duplicate has a phone number and the other has a verified email, the merged record should have both.
5. Validate emails
Cleaning and formatting an email address doesn’t tell you whether it actually works. Before import, run your emails through a verification check. This will flag addresses that are invalid or non-existent, catch-all domains where you can’t confirm individual addresses, role-based addresses (info@, sales@, support@) that are unlikely to be monitored by a decision-maker, and temporary or disposable email addresses.
Remove or flag anything that comes back as invalid. For catch-all and role-based addresses, make a judgment call based on your outreach strategy - some teams exclude them entirely, others keep them but deprioritise.
6. Check phone numbers
If your list includes phone numbers, validate those too. At a minimum, check that numbers are correctly formatted for the country, that they’re real and currently active, and whether any are registered on a do-not-call list (like the TPS/CTPS in the UK).
Calling a number on the TPS register isn’t just a waste of time - it’s a legal issue. Catch these before import, not after a prospect complains.
7. Strip formula injections
This one gets overlooked, but it matters. CSV files can contain cells that start with characters like =, +, -, or @. When those cells are opened in a spreadsheet application, they can be interpreted as formulas - and in some cases, that’s a genuine security risk.
Even if the injection is accidental (someone’s company name starts with a plus sign, or a note field starts with an equals sign), it can cause errors during import. Strip or escape these characters before the file goes anywhere near your CRM.
8. Map fields to your CRM schema
Your source file almost certainly doesn’t use the same field names as your CRM. Before import, map each column in your cleaned file to the corresponding field in your CRM. This means “Company” maps to your CRM’s “Account Name.” “Title” maps to “Job Title.” “Mobile” maps to “Phone (Direct).”
Get this wrong and data ends up in the wrong fields - or worse, overwrites data that was already correct. Take the time to map it properly and preview a handful of records before you run the full import.
9. Preview and spot-check
Before you hit import, pull a random sample of 20 to 30 records and check them manually. Do the names look right? Are emails formatted correctly? Do phone numbers have the right country code? Do company names look clean?
This final check catches issues your automated rules might have missed - and it only takes a few minutes.
What “clean” actually looks like
After running through the steps above, every record in your file should meet a basic standard. Names should be properly capitalised and split into first and last name fields. Emails should be lowercase, trimmed, and verified as deliverable. Phone numbers should be in a consistent format and validated. Company names should be standardised with consistent suffixes and capitalisation. Job titles should be normalised enough to work with your CRM’s filters and routing. Location fields should use a single, consistent format. There should be no duplicates, no junk rows, no formula injections, and no fields in the wrong columns.
That’s what “CRM-ready” means. Not perfect - no dataset ever is - but clean enough that your automations work, your reps can trust what they see, and your reporting reflects reality.
How often should you do this?
Once records are in your CRM, the CRM data hygiene checklist for sales and RevOps covers how to maintain data quality on a recurring basis.
Every time you import a list. No exceptions.
It doesn’t matter if the list came from a “trusted” vendor, a well-known data provider, or an internal team. Every external file has quality issues. The question is never “does this list need cleaning?” - it’s “what kind of cleaning does this list need?”
If you’re importing lists regularly (most outbound teams are), this process needs to be repeatable and ideally automated. Running through a manual checklist once is fine. Doing it every week in a shared spreadsheet is not sustainable.
The cost of skipping this step
Teams that skip pre-import cleaning tend to pay for it in a few predictable ways.
Reps lose trust in CRM data and start keeping their own shadow spreadsheets. Ops spends hours every week fixing duplicates and formatting issues. Bounce rates creep up and sender reputation degrades. Automations misfire and leads get routed to the wrong reps or sequences. Reporting becomes unreliable and leadership loses visibility into pipeline health.
All of these are avoidable. A clean import process doesn’t take long - especially when the steps are built into a repeatable workflow rather than handled manually each time.
Building this into a repeatable workflow
For a comparison of tools that handle deduplication, formatting, and validation, see best CSV cleaning tools for sales and RevOps teams.
The cleaning process described above isn’t complicated, but it has a lot of steps - and each one matters. The teams that do this well don’t rely on individual reps to remember the checklist. They build the process into their tooling.
That means having a place to upload a CSV and preview what needs fixing. Applying standardisation, deduplication, and validation rules automatically. Mapping fields to the CRM schema before export. And keeping an audit trail of what was cleaned, what was changed, and who ran the process.
When those steps are connected in a single workspace, cleaning a list before import goes from a dreaded chore to a two-minute task. And the data that reaches your CRM is something your team can actually work with.
Before you clean, it helps to know what you’re dealing with. Use the free CSV health checker to check your import readiness before going through the full cleaning workflow. For the broader CRM data quality picture after a list is imported, see CRM data cleaning for sales and RevOps teams. If you’re importing specifically into HubSpot, see HubSpot import cleaning.
DataFixr handles CSV upload, cleaning, deduplication, validation, and field mapping in one workflow - so your team can go from raw file to CRM-ready export without the spreadsheet gymnastics. Request early access ->