CRM and contacts

Importing Contacts Without Making a Mess: A Step-by-Step Plan

How to import a contact list into a CRM safely: prepare the file, map columns, handle phone formats and duplicates, test a small batch and check skips.

Call editorial team · Published · 5 min read

An import feels like the easy part: you have a list, you have a button. But a bad import is one of the most expensive things that can happen to a CRM. It floods the system with duplicates, puts people on call lists who should not be there and turns months of careful data into a puzzle. The cure is dull and effective: prepare, test, check. This guide walks through a safe approach for phone teams.

A person checking a spreadsheet of contacts before importing it
Illustrative image

It follows Keeping CRM Data Clean and prepares the ground for Tags and Segments for Contact Lists. If the list will be used for outbound calling, read Keeping Outbound Call Lists Healthy too.

Before you start: know the source and your right to use it

Not every list is a good list. Ask where it came from. Customers and enquirers who dealt with you are a different thing from a bought or scraped list, and many places restrict calling people who have not agreed or who are on a do-not-call register. Decide whether you are allowed to call these people, for what purpose and under which rules, before you load them.

Also decide what you want from the import. Is it a one-off migration from another system, a regular feed, or a list for a single campaign? One-off migrations deserve the most care, since they set the baseline for everything that follows.

Prepare the file

Open the file in a spreadsheet and fix it there. It is much easier than fixing the CRM afterwards.

What to check in the file

  • One row per personRemove empty rows and merge obvious duplicates before importing.
  • Names and companiesEvery row should have at least a contact name or a company.
  • Phone numbersWrite each with the country code, or fill a country column so a local number can be read.
  • Email addressesOne column, one address, no extra text.
  • Header rowThe first line names each column in the way the importer expects.
  • Commas and quotesCheck text fields for commas, which can break a simple comma-separated format.

Be careful with spreadsheet tools that change data silently. Leading zeros in numbers can disappear, long numbers can turn into scientific notation and accents can be damaged when saving. After saving as CSV, open the file in a plain text editor and look at a few lines.

Map columns to fields

Every importer needs to know which column is which. Some let you map columns on screen; others expect fixed headings in a fixed order. Either way, write down the mapping and check the first few rows against it. Common slips are swapping first and last names, putting a company in the name field and putting an email in the number column.

A safe import

  1. Check rightsConfirm you may contact these people.
  2. Clean the fileOne row per person, numbers with country codes.
  3. Test a few rowsImport five to ten rows and open the records.
  4. Read the resultHow many imported, how many skipped, and why.
  5. Import the restLoad the full file only when the test looks right.
  6. Check for duplicatesRun a duplicate review straight away.

Test with a small batch

Always import a handful of rows first. Choose a mix: a clean row, a row with a local number, one with a company but no contact name, and one that you know already exists. Open each resulting record and compare it with the file. If something is wrong, you can delete five records, not five thousand.

Read the result and fix what was skipped

A good importer tells you what it did: how many contacts it added and what it passed over. Rows are commonly skipped when they have neither a contact name nor a company, when the number cannot be read, or when the number is already in your phone book. Do not ignore the skipped count. It tells you about problems in the source that you can fix and re-import.

What happens to different kinds of row

Typical handlingWhat you should do
Number cannot be readSkippedFix the number or add the country, then import again
Already in the systemSkipped or mergedCheck whether the existing record needs updating
No name or companySkippedAdd the missing detail if you can
On the do-not-call listImported but blocked, or skipped, depending on the toolCheck that the contact cannot be called
Extra columnsIgnoredAdd a field first if the information matters

Within a day, run a duplicate review and spot-check twenty records. Look at numbers, names, companies and whether the do-not-call and consent status came through correctly.

Repeat imports and ongoing feeds

If you import regularly, treat it as a process. Use the same file layout every time, keep a log of each import with the date, source, row count and who did it, and tag each batch. Decide who may import: fewer people means fewer accidents. If you can, set a rule that anything over a certain size gets checked by a second person before it goes in.

Import checklist

  • Right to contact these people confirmed
  • File cleaned and numbers in one format
  • Original file saved untouched
  • Mapping written down and checked
  • Test batch imported and read
  • Skipped rows understood and fixed where possible
  • Duplicates reviewed after the import
  • Batch tagged and logged

Importing contacts in Call

In Call, open Campaigns › Prospects and press Import. Optionally choose a campaign that every imported contact should belong to. Replace the example in the text box with your CSV, where the first line is the header: company, contact_name, phone, email, country, city. Press Import, and a message says how many contacts were imported. The box reads plain comma-separated text; there is no file upload on this screen, and quoted fields with commas inside are not supported, so save from your spreadsheet as CSV and paste the text. Agents and managers can both import.

Write numbers with the country code, or fill the country column so a local number can be read. Fewer contacts may be imported than the lines you pasted: lines with neither a contact name nor a company, lines whose number cannot be read and numbers already in your phone book are passed over. A number already on your do-not-call list is imported at the stage Do not call instead of being dropped. Afterwards, the Data hygiene tab on the Revenue page finds records that share a phone number or email and lets you merge them without losing history, which is a good step after any import that brought in the same people twice. Merging cannot be undone from that page, so check which record is kept first.

Frequently asked questions

Why were fewer contacts imported than I pasted?

Rows can be skipped if they have no contact name or company, if the phone number cannot be read, or if the number is already in the system. Check those cases in the source.

What format should phone numbers use?

Use the country code, or fill a country column so local numbers can be read. Pick one format and use it throughout the file.

How do I avoid duplicates?

Clean the file first, decide how matching rows are treated, import a small test batch and run a duplicate review afterwards.

Can I import a list I bought?

Be careful. You need to know you are allowed to contact those people for your purpose, and rules differ by country. Check the official regulator or a qualified adviser.

What if my text contains commas?

Simple comma-separated imports can break on them. Remove or replace the commas in the file before importing, or use a tool that supports quoted text.

How do I undo a bad import?

Tag each batch so you can find it. Deleting a small test batch is easy; fixing a large bad import is not, so always test small first and keep the original file.

Import a contact list from CSV and check what was skipped in Call

In the demo console you can try incoming calls in a simulation.

Related guides