Before You Import That Lead List Into Salesforce, Read This

This post was contributed by Cloudingo.

There’s a familiar moment for anyone who manages a Salesforce or Marketo org: a spreadsheet lands in your inbox — a trade show list, a partner hand-off, a CSV pulled from an event platform — and the cursor is hovering over “Import.” The import itself takes thirty seconds, and there is always pressure to get the data in as fast as possible. But, cleaning up after a bad import can take weeks. 

Bad imports don’t just create duplicate records. They break lead routing rules, distort attribution, throw off forecasting, and quietly erode the team’s trust in the CRM. And because most import problems aren’t visible until someone downstream trips over them, the damage is usually discovered well after the file has already been pushed. 

This post walks through the most common import scenarios, what typically goes wrong, and a practical checklist to run through before committing the import. It closes with what to do when a manual check isn’t enough to catch everything, which is a real limit worth knowing about before you’re relying on it.

Why the import moment matters more than people think 

An import is a one-way door disguised as a routine task. Once records land in Salesforce or Marketo, they don’t sit still — they get enriched, assigned to reps, dropped into nurture tracks, and reported on. The longer a bad record lives in the system, the more expensive it becomes to fix, because untangling it means finding everything it’s already touched. 

That’s why the import step deserves more attention than it usually gets. It’s the last point where a mistake is cheap. After that, it’s a time-consuming and expensive cleanup project. 

Where these lists tend to break 

The specifics vary, but most import problems trace back to the same handful of root causes. It’s worth knowing which one you’re dealing with, because it changes what you’re checking for: 

• Formatting problems: inconsistent dates, states written out instead of abbreviated, picklist values that are close to the options in the database but not exact. 
• Collection problems: the data was captured in the way a person typed or spoke it in the moment (a badge scan, a business card), not the way it already exists in your CRM — so “Robert Smith at Acme Corporation” and a new row for “Bob Smith, Acme” look unrelated on the surface even though they’re the same contact. 
• Trust problems: you don’t control what source data was collected, how it was collected, or how it was formatted, and there’s usually pressure to load the file fast so reps can start working it. 

The pre-import checklist you can actually use 

Regardless of where the list came from, here’s a working checklist to run through before adding the data to Salesforce or Marketo: 

1. Standardize formatting — dates, phone numbers, state, and country fields — before uploading. 
2. Confirm picklist values match the options in your data fields exactly. 
3. Remove exact and near-duplicate rows within the file itself. 
4. Decide your matching logic in advance (email, name plus company, or domain). 
5. Check the list against records that already exist in your org, not just against itself. 
6. Test a small sample batch before importing the full file, especially for partner hand-offs, and review and confirm results. 

What a good pre-check catches, and what it doesn’t 

A careful manual review will catch a lot: formatting issues, obvious duplicate rows, missing required fields. What it can’t catch is whether “Bob Smith” in your spreadsheet is already sitting in Salesforce as “Robert Smith” at a company listed under a slightly different name. Spotting that kind of match means checking the incoming list against your actual Salesforce data — not just eyeballing the file. 

Why this is usually a job for a third-party tool, not native to Salesforce alone 

It’s worth being direct about why this keeps happening even to careful teams: Salesforce’s native import capabilities and duplicate rules are built to catch duplicates as records are created or edited one at a time in the UI. They weren’t designed to screen an entire import file before it lands, and depending on how a file is loaded, bulk imports can bypass those rules altogether. 

There’s no built-in way to preview a file against your existing data, adjust matches, and then decide what happens next — you find out about the duplicates after they’re already in the org or in your error report.  And it’s not possible to check the file against multiple objects in a single process (contacts and leads). That gap is exactly what a purpose-built import tool that includes data quality features is for.

A dedicated solution checks a list against your existing records before anything is created, gives you a preview step to review and adjust matches, and applies consistent matching and merge logic across every import instead of relying on whoever happens to be running that day’s upload. For teams doing recurring imports — event follow-ups, monthly partner hand-offs, ongoing list uploads — that consistency is the difference between a repeatable process and a recurring cleanup project. 

How Cloudingo helps 

FormAssembly’s forms handle clean collection at the front door — and if you’ve set up a two-form workflow to catch duplicate submissions, you’re already stopping a lot of duplicates before they’re created. But most Salesforce and Marketo orgs also take data in through the back door — spreadsheets, event lists, partner hand-offs — and a form-level check won’t touch a list that never went through a form at all. This is where a partner like Cloudingo comes in: a dedicated data quality and import tool built specifically to check a list against your existing CRM data before anything gets created. 

For teams that want that same always-watching protection to extend past the form — catching duplicates the moment they’re created or updated in Salesforce, no matter where they came from — Real-Time Merge does that continuously in the background. 

Here’s what the Import Wizard does for a list before it ever reaches Salesforce or Marketo: 

• Matches before it creates. Every row in the file is checked against existing Salesforce or Marketo records first. If a match is found, the existing record can be updated instead of a new one being created — which is the core fix for the “Bob Smith” versus “Robert Smith” problem covered above.  Matching options are customizable to add flexibility when needed. 
• Lets you preview and edit before anything goes live. You see the matches, the new records, and any formatting issues before the import runs — not after. Last-minute fixes like standardizing phone number formatting or correcting a malformed email happen at this step, not in a cleanup project two weeks later. 
• Applies customizable filters. You control exactly which Salesforce or Marketo records the incoming list gets compared against, which fields count as a match, and to what degree — useful when a partner list needs different matching logic than a routine spreadsheet upload. 
• Handles required fields and merge rules automatically. 
• Saves templates for repeat imports. Field mappings can be saved and reused, which matters most for the imports that repeat on a schedule — monthly partner hand-offs, post-event follow-ups — instead of rebuilding the mapping from scratch every time. 
• Scans without committing, when that’s all you need. Cloudingo’s Find Data tool checks a file against Salesforce without creating or merging anything, which is useful when you just want a duplicate count before deciding how to proceed, or when you need to append your list with additional data points for another purpose. 

One practical note: import files are capped at 20MB, so larger lists — a big trade show list, for instance — are best split into batches rather than pushed through in one file. 

The bottom line 

Every list you import is a decision point, not just a data transfer. A few minutes spent standardizing formats and checking for matches before running the import saves hours – sometimes weeks – of untangling records after the fact. Pair that discipline with a tool built to check incoming data against what’s already in your org, and imports stop being a recurring cleanup project.

Author:

Stephen Harding, Co-founder and COO of Cloudingo, leverages 15 years of expertise in aiding Salesforce users with data cleaning, maintenance, and migration. His real-world experience makes him a valuable voice on this topic, offering actionable insights for optimized data management.