Staring down a spreadsheet with 200 client names, half-finished notes, and no clear plan for getting them into your new system is enough to make anyone put off switching tools for another year. Yet learning how to import contacts correctly is one of the fastest ways to get a CRM up and running without losing years of client history in the process. A messy import can duplicate records, scramble phone numbers, or drop notes you need for your next follow-up, so the process deserves more care than a quick drag-and-drop. If you're still comparing CRM tools worth considering for your business, it helps to know exactly how the import step works before you commit to one. This guide walks through preparing your data, picking the right file format, mapping fields, and cleaning up afterward, so your contact list arrives intact and ready to use.
Below, you'll find a step-by-step breakdown of the entire import process, from exporting your old contacts to organizing them once they land in your new CRM, plus the most common mistakes freelancers and small teams run into along the way.
Manage clients, leads, and projects in one CRM
Importing contacts means transferring your existing contact records into a new system in bulk, rather than typing each name, email, and phone number in by hand. Most CRMs accept imports through a file upload, most commonly a CSV spreadsheet or a vCard file exported from another app. This step usually comes up when a freelancer or small team adopts a new CRM, switches platforms, or finally brings together contacts scattered across a phone, an inbox, and a handful of spreadsheets for easier management. Done well, it saves hours of manual data entry and keeps client history intact from day one.
A clean import starts before you ever touch the upload button. Gathering and standardizing your contact data first prevents scrambled fields, duplicate records, and missing notes once everything lands in your new system.
Export contacts from your current source
Start by pulling contacts out of wherever they currently live. Most email clients let you export contacts as a CSV or vCard file from account settings, phones typically offer a similar export option under contacts settings, and spreadsheets just need saving in a compatible format. If you're moving off another CRM entirely, our guide to CRM migration for freelancers and small businesses walks through exporting historical client data without losing deal stages or notes.
Clean and standardize your data
Before uploading anything, scan for inconsistent formatting: mismatched phone number styles, missing area codes, or emails with typos. Remove blank rows and obvious duplicate entries now rather than after they've cluttered your new CRM. A few minutes spent standardizing name capitalization and contact fields upfront saves a much larger cleanup job later.
Step 2: Choose the right file format for import
Most CRMs import contacts through one of two file types, and picking the right one upfront saves you an extra export-and-retry cycle. Before exporting anything, check your CRM's import settings to confirm which formats it accepts.
CSV files
CSV stands for comma-separated values, a plain spreadsheet format that lists each contact as a row and each detail (name, email, phone) as a column. It's the most flexible and widely accepted format for bulk contact imports, since many CRMs, spreadsheet tools, and email clients can export or open one.
vCard files
A vCard is a standard digital business card format, usually with a .vcf extension, that phones and email apps generate when you export contacts. vCards preserve individual contact cards well but are less flexible than CSV for editing large batches before import.
Step 3: Map your fields to avoid data loss
Field mapping is the process of connecting each column in your import file to the matching field inside your CRM, so a column labeled "phone" lands in the phone field instead of getting dropped or misfiled. Most CRMs handle this automatically for common fields, but it's worth reviewing the mapping screen before you confirm the upload.
Matching standard fields
Standard fields like first name, last name, email, phone, and company usually map on their own, since import tools recognize these common headers automatically. Still, glance over the preview screen to confirm each column landed where expected before finishing the import.
Handling custom fields
Columns like deal stage, referral source, or internal notes often aren't standard CRM fields, so you may need to map them manually or create a new field to hold them. This is also a good time to think through how to use custom fields to organize your client data going forward, so future contacts follow the same structure.
Manage clients, leads, and projects in one CRM
Get started
Once your file is mapped, most CRMs run a preview step before anything goes live. This screen shows how many records are set to import and flags rows with missing fields, invalid emails, or formatting errors, so you can fix problems before they become permanent records. Confirming the upload at this stage is far easier than untangling a bad import afterward.
After the import finishes, spot-check a handful of records against your original file. Pick a few contacts with notes, custom fields, or unusual formatting, since these are the most likely to slip during the transfer. If a handful of rows failed, fix those individually and re-upload just the corrected rows rather than re-running the entire import, which risks creating duplicate records for records that already came through correctly.
Imported contacts often land as separate records when the same person existed in more than one source list, like a client saved in both your email and an old spreadsheet with slightly different details. Cleaning these up turns a raw import into a CRM you'll actually use day to day.
Merge duplicate records
Most CRMs flag likely duplicates by matching name, email, or phone number, but it's worth scanning the list yourself for near-matches the system might miss. Merging duplicates keeps notes, email threads, and communication logs attached to one record instead of scattered across two.
Tag and segment new contacts
Once duplicates are handled, sort contacts into pipeline stages or tags so the list is workable, not just stored. Our guide on how to use CRM tags effectively for better client management covers setting up a tagging structure that holds up as your contact list grows.
Most import headaches trace back to a handful of avoidable errors, and knowing them ahead of time can save you a second cleanup pass. Keep these in mind before you upload anything:
- Skipping the cleanup step: Uploading a messy file as-is just moves duplicate entries and formatting problems into your new CRM instead of fixing them.
- Ignoring the mapping preview: Rushing past the field-mapping screen often leads to mismatched columns, like phone numbers landing in a notes field.
- Skipping a backup: Keep a copy of your original file before importing, so you have something to reference if records go missing.
If you're setting up a new system from scratch, our step-by-step guide to CRM setup covers what to configure before your first import.
Picture a freelance copywriter who's been tracking 40 clients across a spreadsheet and a phone's contact list for two years, finally ready to bring everything into her CRM. That's the exact moment Bonsai CRM is built for: uploading a CSV of existing contacts and having each one land as a client or company record, complete with deal stages and a pipeline view instead of a flat list of names.
Once contacts are in, the CRM keeps communication history and notes attached to each record, so the details that made the import worth doing in the first place don't disappear after day one. A small design agency importing 60 client contacts from an old system can add notes on past projects, referral sources, or billing preferences right on each record, picking up exactly where the spreadsheet left off. Because Bonsai integrates with Zoom Meetings, meeting transcripts can also sync to the client's record in Bonsai, so a consultant who imports a contact list and then hops on a Zoom call with a returning client has that conversation logged alongside everything else, no separate note-taking required.
For a solo bookkeeper managing 25 active clients, that means the import isn't just a one-time data dump. New contacts land in the pipeline with deal stages ready to update, existing notes carry over cleanly, and future client conversations can add to the same record instead of starting a new thread somewhere else. The result is a contact list that's usable the moment the import finishes, not just stored.
FAQ
Q1: What does it mean to import contacts into a CRM?
Importing contacts means uploading your existing contact records into a CRM in bulk, rather than typing each name, email, and phone number in individually. Most CRMs accept this through a file upload, typically a CSV spreadsheet or a vCard file exported from another app or device. The process transfers details like names, emails, phone numbers, and sometimes notes or deal stages, in a single upload instead of one at a time.
This step usually comes up when someone adopts a new CRM, switches platforms, or consolidates contacts scattered across a phone, an inbox, and a few spreadsheets. A freelance photographer moving 80 client contacts out of an email account and into a CRM, for example, would export those contacts as a file and import them rather than re-entering each one by hand.
Q2: What file format should I use to import contacts?
CSV is a flexible and widely accepted format for importing contacts, since many CRMs, spreadsheet tools, and email clients can export or open one. It lists each contact as a row and each detail, such as name, email, or phone, as a column, which makes it easy to review and edit before uploading.
vCard files, usually saved with a .vcf extension, are the other common option and are typically generated when exporting contacts from a phone or email app. vCards preserve individual contact cards well but are less convenient than CSV for editing large batches at once, so CSV tends to work better when importing more than a handful of contacts.
Q3: Can I import contacts from my phone or email into a CRM?
Yes. Most phones and email clients include a built-in option to export contacts, usually found in account or contacts settings, and that export typically comes out as a CSV or vCard file. Once exported, that file can be uploaded directly into a CRM's import tool.
The process works the same whether contacts are coming from a phone's address book, a Gmail or Outlook account, or a spreadsheet someone has kept updated manually. The main difference is the export step itself: phones and email apps generate a ready-to-use file, while a spreadsheet just needs to be saved in a compatible format before uploading.
Q4: How do I avoid duplicate contacts when importing?
Start by cleaning your source file before uploading it, removing obvious duplicate rows and blank entries so they never make it into the new system in the first place. After the import finishes, most CRMs flag likely duplicates by matching name, email, or phone number, but it's worth scanning the list yourself for near-matches the system might miss, like a client saved under a slightly different email address.
Merging any duplicates that do appear keeps notes, communication history, and past details attached to a single record instead of scattered across two. This matters most for contacts with a longer history, since merging preserves the context that made importing them worthwhile.
Q5: How does Bonsai help with import contacts?
Bonsai CRM lets users upload a CSV of existing contacts and have each one land as a client or company record complete with deal stages and a pipeline view, rather than a flat list of names. Notes, referral sources, and other details can be added directly to each imported record, so the context that made the import worth doing doesn't disappear after the upload finishes.
Because Bonsai integrates with Zoom Meetings, meeting transcripts can also sync to the client's record in Bonsai, so conversations with newly imported contacts get logged alongside everything else automatically. That means a consultant who imports a client list and then hops on a Zoom call with one of those contacts sees that conversation attached to the same record, not tracked in a separate tool.
Getting your contacts into a new CRM doesn't have to mean losing years of client history or spending a weekend untangling duplicates. Prepare your data, choose the right file format, map your fields carefully, and verify the results, and the import becomes a one-time task instead of a recurring headache. Whichever CRM you land on, Bonsai included, that same groundwork keeps your client list accurate and ready to use from the first day.
