The spreadsheet arrives in your inbox: a purchased list, event badge scans, a partner referral dump — a few hundred names that need to become Salesforce leads before the team can work them. The questions that follow are always the same. Which import tool do I use? Where do the notes go? What happens when these leads convert?
Salesforce offers several legitimate import paths, and the right choice depends on volume, how often you'll do this, and how much mapping control you need. This guide compares the options and walks through the decisions that keep imports clean — field mapping, notes, duplicates, and what conversion does to your data afterward.
The best way to import leads into Salesforce depends on volume and frequency: the built-in Data Import Wizard (Setup → search "Data Import Wizard") handles up to 50,000 records per run with point-and-click field mapping and is right for most business users; Data Loader handles millions of records and automation via CLI for heavy or recurring loads; and browser extensions like Salesforce Inspector give admins fast paste-and-map imports for ad-hoc batches. Whatever the tool, clean the spreadsheet first, map every column deliberately (unmapped columns are simply skipped), put narrative notes in the Lead Description field or as logged activities, and use matching by email or an external ID to avoid duplicates. Vantage Point builds repeatable import workflows like this as part of its Salesforce consulting work.
Three options cover nearly every scenario:
| Tool | Volume | Strengths | Best for |
|---|---|---|---|
| Data Import Wizard | Up to 50,000 records | Native, browser-based, guided mapping, matching options | Occasional lead/contact/account imports by business users |
| Data Loader | Up to 5 million records | Insert/update/upsert/upsert-by-external-ID, CLI automation, error files | Large migrations, recurring syncs, admin-heavy work |
| Browser extension (e.g., Salesforce Inspector) | Small batches | Paste-from-spreadsheet mapping, in-context in Salesforce | Admins doing frequent ad-hoc loads |
Third-party loaders (dataloader.io and similar) sit alongside these — friendlier UIs, cloud scheduling — at subscription cost. For most teams importing lead lists monthly, the Import Wizard is genuinely sufficient; reach for Data Loader when volume, upsert logic, or automation demands it.
Import failures are spreadsheet failures. Twenty minutes of prep prevents an afternoon of cleanup:
A useful pattern for recurring imports: a two-tab workbook — a raw paste tab where the source list lands untouched, and a load tab whose formulas reshape the raw data into exactly the columns Salesforce expects. The load tab exports to CSV; the raw tab preserves the audit trail.
Every import tool presents a mapping step: your columns on one side, Salesforce fields on the other. Three rules of thumb:
The Import Wizard offers matching on lead import — by name, email, or Salesforce ID — and can update matched records instead of inserting new ones. For anything beyond a one-off, the stronger pattern is upsert on a stable identifier: match by email (normalized) or, for recurring vendor lists, store the vendor's record ID in a custom external-ID field and upsert on it. Pair this with duplicate rules that alert or block on lookalike records, and imports stop being a source of cleanup work.
Teams are often surprised by conversion behavior after an import, so set expectations up front: converting a lead creates an Account and Contact — and optionally an Opportunity, which the converter can skip for early-stage prospects. The lead record itself becomes read-only and disappears from lead list views; users find the person afterward under Accounts/Contacts or via reports. Field values carry over per your lead conversion field mapping (Setup → Lead Settings → custom field mapping), and the Description notes you imported travel with them.
Two practical consequences: run conversion field mapping before your first big import, not after; and train importers that "where did my lead go?" has a boring answer — it converted, and it lives on the account now.
Lead imports concentrate risk in a single click, so treat them as a mini-process: one or two trained admins own the load spreadsheet and the import itself; everyone else submits lists to them. Permissions matter — importing leads requires the Marketing User checkbox plus create/edit rights on leads, and MFA or login-verification prompts are normal on first use of desktop tools. For recurring imports, document the mapping once (a screenshot of the mapping screen suffices) so the process survives the admin's vacation.
Three failure modes account for most import grief. Picklist mismatches: a spreadsheet value that doesn't exactly match a Salesforce picklist entry ("Webinar" vs. "Webinar Event") fails that row — standardize values before loading. Character encoding: a CSV saved in the wrong encoding mangles accented names and smart quotes; save as UTF-8. Truncation: text columns longer than the target field's limit (Description caps at 32,000 characters; most text fields far less) fail or truncate — check your longest cells. Data Loader's success and error files make these diagnosable row by row; the Import Wizard surfaces failures in its results email. Either way, read the error file before assuming the import "worked" — a green banner with 40 failed rows is a partial import.
Recurring vendor or event lists justify automation. Data Loader's command-line interface can run on a schedule against a standing CSV drop, and integration platforms (including Vantage Point's MuleSoft and Workato practices) turn a recurring list into a managed feed with upsert logic and error alerting. The threshold is simple: if someone does the same manual import more than about monthly, the automation pays for itself in a quarter — and removes the "did anyone load the list?" question entirely.
Vantage Point's Salesforce consultants design repeatable import workflows — load-sheet patterns, mapping documentation, duplicate-safe upsert strategies, and conversion field mapping — so list imports become a routine instead of a risk. For larger efforts, our system integration and data migration services cover migrations from legacy CRMs end to end. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver.
Vantage Point can set up a documented, duplicate-safe import workflow — or take a full CRM migration off your plate. Talk to Vantage Point about your Salesforce data.
The built-in Data Import Wizard: from Setup, search "Data Import Wizard," choose Leads, upload a CSV, and map columns to fields on screen. It handles up to 50,000 records per run and requires no software install — the right default for occasional list imports.
When volume exceeds 50,000 records, when you need upsert logic keyed on an external ID, when you want automation via the command line, or when you need detailed success/error files for auditing. The Wizard is for convenience; Data Loader is for scale and control.
Pre-existing narrative notes (prior outreach, context) map best to the lead's Description field, which survives conversion to the contact. Ongoing, chronological notes belong on the activity timeline — Log a Call entries and tasks — after the records exist.
Conversion creates an Account and Contact — optionally an Opportunity — and the lead becomes a read-only record that no longer appears in lead views. Field values carry over according to your conversion field mapping, so configure that mapping before importing large lists.
Use the Import Wizard's matching options (match by email) or upsert on an external ID via Data Loader, and keep duplicate rules active with alert-or-block behavior. Clean the list against existing records before import when the list is small enough to eyeball.
The Marketing User checkbox on the user record, plus create and edit permissions on leads. Desktop tools like Data Loader also require an API-enabled user and may prompt for identity verification on first login — both normal, both resolvable in Setup.