Import Client Contacts Into CRM Without Losing Data

When you're ready to switch from a spreadsheet, a filing cabinet full of index cards, or a platform that no longer fits your business, the single biggest concern is losing client history. A botched import can orphan appointment notes, disconnect phone numbers from names, or leave you scrambling to re-enter hundreds of records by hand. The good news: import client contacts into a CRM cleanly by exporting a CSV from your current system, cleaning the column headers and phone formats in a spreadsheet editor, mapping each field to the new CRM's contact properties, running a small test batch first, then importing the full file and spot-checking a dozen records across the alphabet to confirm nothing was dropped.

Most service-business CRMs—including Relay—accept contact imports via CSV (comma-separated values) spreadsheet files. The mechanics are straightforward, but skipping the prep steps costs you hours of cleanup after the fact or, worse, forces you to delete the import and start over.

Key Takeaways

• Export your current client list as a CSV, then clean column headers, phone number formats and duplicate rows before you import into the new CRM.
• Map each spreadsheet column to the correct contact field in the new system—first name to first name, mobile to phone—so data lands where you expect it.
• Run a test import with 10-20 rows first, check that names, phone numbers and notes appear correctly, then import the full file once you've confirmed the mapping.
• After the full import, spot-check a sample of contacts (A, M, Z) to verify that phone numbers dial, email addresses are intact, and any custom notes or tags survived the transfer.
• Keep the original export file as a backup for at least 90 days in case you need to re-import or cross-reference a missing field.

Why a Clean Import Matters for Service Businesses

A salon with 800 clients, a med spa booking 40 appointments a week, or a barbershop juggling walk-ins and standing reservations all depend on accurate contact records. When a phone number imports with a stray space or a parenthesis in the wrong spot, your text reminders bounce. When a client's preferred pronouns or allergy notes end up in the wrong field—or vanish entirely—you've lost context that took months to build.

The stakes are higher than they first appear. A missing phone number means a no-show you could have reminded. A transposed first and last name means the automated review request opens with the wrong greeting. And if your old system stored appointment history or service preferences in a notes field that doesn't map cleanly, that context is gone unless you plan the transfer carefully.

Small service businesses typically carry between a few hundred and a few thousand active contacts. That size feels manageable—until you're halfway through a manual re-entry project and realize it will take the rest of the week. A well-executed CSV import moves the entire list in minutes, not days.

What You Need Before You Start

Before you touch the new CRM, gather three things: the export file from your current system, a spreadsheet editor (Excel, Google Sheets or Numbers), and a list of the contact fields your new CRM recognizes.

Export from Your Current System

Most platforms and even older desktop software offer a Contacts export or Download clients button, usually under Settings or Reports. The file format you want is CSV. If the only option is Excel (.xlsx) or vCard (.vcf), open the file in a spreadsheet editor and re-save it as CSV.

Check what the export includes. Some systems bundle every field—name, phone, email, address, birthday, custom tags—into one file. Others split contacts and appointment history into separate downloads. For the initial contact import, you need at least first name, last name, phone and email; everything else is helpful but not required to get the list into the new system.

If you're leaving behind a paper card file or a spreadsheet you've been updating by hand, you already have a CSV (or can create one by copying the rows into Google Sheets and exporting). Just make sure every row represents one client and every column represents one piece of information.

Clean the Column Headers

Open the CSV in your spreadsheet editor and look at the first row. Those headers—First Name, Phone, Email Address, Notes—tell the CRM where each piece of data belongs. The CRM will ask you to map each column to a field it understands, so clear, consistent headers save you guesswork during the import.

Rename any vague or concatenated headers. If your old system exported a single Name column, split it into First Name and Last Name using the spreadsheet's text-to-columns tool or a formula. If you see Phone 1, Phone 2, Phone 3, decide which one is the primary mobile number (the one you'll text) and label it Phone or Mobile; you can import the others into a notes field or skip them.

Delete columns you don't need. If the export includes internal IDs, creation timestamps, or fields you never filled out, clear them out now—fewer columns make the mapping step faster.

Standardize Phone Numbers

Phone number formatting trips up more imports than any other field. Your old system might have stored numbers as (555) 123-4567, 555-123-4567, 5551234567, or even +1 555 123 4567. The new CRM expects a consistent format—usually ten digits with no punctuation, or E.164 international format (+15551234567).

Pick one format and apply it to the entire phone column. In Google Sheets or Excel, you can use find-and-replace to strip out parentheses, dashes and spaces, then prepend +1 if the CRM requires country codes. If you're not comfortable with formulas, a manual pass through a couple hundred rows is tedious but only takes an hour.

Check for obviously broken entries: phone numbers with only seven digits, letters mixed in, or a placeholder like N/A or call for info. Either fix them now or delete those rows and add them manually after the import—a handful of bad records won't stop the import, but they'll clutter your contact list with un-textable entries.

Deduplicate Before You Import

Scroll through the spreadsheet and look for duplicate rows—two entries for Jane Smith, one from 2022 and one from 2024, each with slightly different phone numbers or email addresses. Decide which record is correct (usually the most recent), delete the other, or merge the two by hand if both contain useful information.

Most spreadsheet editors offer a Remove duplicates tool under Data or Edit. Run it on the email column or phone column to catch obvious doubles, but review the results—sometimes two clients share a phone number (a couple, or a parent booking for a teen), and you don't want to delete a real person.

How to Map and Import the CSV Into Relay

Once your CSV is clean, head to your new CRM's import tool. In Relay, you'll find contact import under the Contacts section. The process follows the same three-step pattern in most systems: upload the file, map the columns, then review and confirm.

Upload the CSV

Click Import contacts or Upload CSV, choose your file, and let the CRM read the first few rows. The system will display a preview table showing the headers and a sample of the data underneath. This is your chance to catch any formatting problems before you commit: if phone numbers still have parentheses, or the first row is actually a duplicate header line, go back to the spreadsheet, fix it, save, and re-upload.

Map Each Column to a Contact Field

The CRM will present a dropdown next to each column header, asking you to match it to a standard field. Map First Name to First Name, Last Name to Last Name, Phone or Mobile to Phone, Email to Email, and so on.

If your CSV has a column the CRM doesn't have a built-in field for—say, Preferred Stylist or Allergy Notes—you have two options. Some CRMs let you create a custom field on the fly during import; if yours doesn't, map that column to a general Notes or Description field so the information isn't lost. You can split it out later or reference it when you're on the phone with the client.

Leave unmapped any column you don't need. If you kept an internal ID column for reference, just set its dropdown to Do not import.

Run a Test Import First

Before you import all 1,200 rows, import the first 10 or 20 as a test batch. Copy those rows into a new CSV, upload it, map the fields the same way, and complete the import. Then open a few of the newly created contact records in the CRM and check:

• First and last names landed in the right fields and are capitalized correctly.
• Phone numbers are formatted consistently and have no stray characters.
• Email addresses are complete and lowercase.
• Any notes or tags you mapped appear in the correct spot.

If something looks wrong—names are reversed, phone numbers are truncated, or a whole column ended up blank—you caught it on 10 rows instead of 1,200. Delete the test contacts, go back to the CSV, fix the mapping or the data, and test again.

Import the Full File

Once the test batch looks clean, go back to the import tool, upload the full CSV, apply the same column mappings, and confirm. Most CRMs process the import in the background and email you when it's done; larger files (more than a thousand rows) might take a few minutes.

When you get the confirmation, open the Contacts list and sort by Date Added or Created Date so the new imports appear at the top. Spot-check a dozen records: one whose last name starts with A, one with M, one with Z. Call or text one of the phone numbers to make sure it connects. Send yourself a test email to one of the addresses. Open the contact record and confirm that any notes, tags, or custom fields carried over.

What to Do if Records Are Missing or Incorrect

If a handful of contacts didn't import—maybe their rows had a formatting issue the CRM couldn't parse—add them by hand. If dozens or hundreds are missing, compare the row count in your CSV to the number of contacts the CRM says it imported. A mismatch means something went wrong during the upload: check that the CSV is saved with UTF-8 encoding (not Windows-1252), that there are no blank rows in the middle of the file, and that every row has the same number of columns.

If data landed in the wrong fields (first names in the last-name field, for example), the fastest fix is to delete the imported batch and re-import with corrected mappings. Most CRMs let you bulk-delete contacts imported on a specific date, or you can filter by Date Added and select all.

Importing Into Relay Specifically

Relay accepts contact imports via CSV on every paid plan (Relay Basic, Starter, Pro and Business). You can import first name, last name, phone, email and a notes field; the phone number should be ten digits or E.164 format, and email addresses must be valid (no spaces, a single @, a domain).

Relay does not create duplicate contacts when the phone number or email already exists—so if you import the same list twice by accident, the second import updates the existing records rather than doubling your contact count. That's a safety net, but it also means you should finish cleaning the CSV before you import, because re-importing won't fix a field you left blank the first time unless you populate it in the CSV and map it again.

After the import, Relay adds the new contacts to your shared inbox and makes them available for pipelines, booking links and automations. If you're on Starter or higher, you can immediately send a bulk text to the imported list—for example, a welcome message with your new booking link—but draft the message carefully and send a test to yourself first, because once a text goes out to hundreds of people, you can't recall it.

For businesses switching from another CRM or booking platform, Relay also imports from a CSV exported by that tool. The column headers will be different, but the mapping step handles it: match Client First Name to First Name, Cell Phone to Phone, and so on. If the old system stored appointment history in a notes column, map it to Relay's notes field; you won't have structured appointment records in the calendar, but you'll have the written record attached to the contact.

You can re-import additional contacts later—if you acquire a new location or merge in a second business—using the same import tool. Relay processes each import independently, so you can bring in one batch today and another next month without disturbing the contacts already in the system.

Common Pitfalls and How to Avoid Them

Even a careful import can hit snags. Here are the most frequent mistakes and how to sidestep them.

Mixing First and Last Names

If your CSV has a single Name column with full names (Jane Smith, Dr. Robert Kim, Maria), the CRM can't split it automatically. Use a spreadsheet formula to parse first and last names into separate columns. In Google Sheets, =SPLIT(A2," ") breaks Jane Smith into two cells; you can then copy and paste values into First Name and Last Name columns. Watch for names with more than two parts—Mary Beth Johnson or Dr. Kim—and handle them manually.

Importing Personal Email Addresses as Business Emails

If your contact list includes clients' Gmail, Yahoo or iCloud addresses and you map them to a Business Email field, you'll confuse yourself later when you're trying to send invoices. Most service businesses only need one email field per contact, so map to Email generically; if your CRM has both Email and Work Email, pick whichever you'll actually use.

Forgetting to Import Tags or Groups

If your old system let you tag clients (VIP, New Client, Referral Source) and you want to keep those segments, make sure the export includes a tags or groups column and that your new CRM supports tag import. Some tools require you to recreate tags by hand after the import, then bulk-apply them by filtering the contact list. If preserving segments is critical—say, you send different promotions to new versus returning clients—plan that step before you decommission the old system.

Overwriting Existing Contacts by Accident

If you've already started using the new CRM and added a few dozen contacts manually, then you import a CSV that includes those same people, the CRM might update the manual entries with the CSV data. That's usually fine, but if you'd added notes or updated a phone number in the CRM and the CSV has the old number, the import will overwrite your recent work. The fix: export your current CRM contacts, merge that CSV with the old system's export in your spreadsheet editor (deleting duplicates), then import the combined file once.

Leaving the Old System Running in Parallel

After the import, turn off or cancel the old system as soon as you've confirmed the new one works. Running two systems in parallel—taking bookings in both, or checking messages in both—guarantees that client information will diverge, and you'll spend weeks trying to reconcile which notes are current. Set a cutover date, import everything, test for a day, then shut down the old account.

What Happens to Appointment History and Notes

A CSV contact import brings over names, phone numbers, emails and any text fields you map (notes, tags, custom properties). It does not import structured appointment records—dates, times, services, payments—because those live in a different part of most CRMs' databases and require a separate import or API sync.

If preserving appointment history is essential—for example, you need to know that Jane last visited on March 10, 2025, and had a balayage—you have a few options:

• Copy the history into the notes field. Before you export from the old system, create a calculated column in your spreadsheet that concatenates the client's last appointment date and service into a single text string (Last visit: 3/10/2025, balayage), then map that column to the CRM's notes field on import. It's not searchable or structured, but you'll see it when you open the contact.
• Export appointments separately and reference them. Some CRMs let you import appointments as calendar events if you have a CSV with columns for contact name, appointment date, start time and service. Check whether your new CRM supports it; if it does, export appointments from the old system, clean the date and time formats, and import them after you've imported contacts.
• Start fresh and note the transition date. Many service businesses treat the CRM migration as a clean break: appointments from this point forward live in the new system, and if you need to reference older history, you keep read-only access to the old platform for 90 days or export a PDF report for your records. This is the simplest approach when appointment history is rarely referenced or when the old system's data is incomplete.

For notes that aren't tied to a specific appointment—client preferences, allergy warnings, referral source—make sure those are in a column you import. If the old system stored notes across multiple fields (Notes 1, Notes 2, Internal Comments), concatenate them in the spreadsheet before import so everything lands in one place.

After the Import: Keeping Your Contact List Clean

A successful import is the beginning, not the end. Client information changes constantly—phone numbers update, email addresses bounce, people move or stop visiting—so plan to keep the list current.

Set a recurring calendar reminder (quarterly or twice a year) to export your contact list, sort by Last Contact Date or Last Appointment, and archive or delete anyone who hasn't visited in 18-24 months and hasn't responded to a win-back message. That keeps your text and email allowances focused on active clients and prevents your contact list from bloating to the point where it's hard to find the people who matter.

When a text bounces or an email returns undeliverable, update the contact record immediately—either fix the number, ask for a new email the next time the client calls, or mark the record as inactive. Relay and most other CRMs track bounces automatically, but it's up to you to clean them up.

If you're using automations—like a review request two hours after the appointment or a win-back text 60 days after the last visit—double-check that the phone numbers in your imported list are mobile numbers, not landlines. Landlines can't receive texts, and the automation will fail silently. If your CSV mixed mobile and home numbers, review the contact list after import and either correct the entries or remove the landline numbers from the phone field so they don't trigger a failed text.

Bringing It All Together with Relay

Relay handles contact imports through a CSV upload under the Contacts section. You'll map your spreadsheet columns to first name, last name, phone, email and notes, run a test batch, then import the full list. Every paid plan—Relay Basic, Starter, Pro and Business—includes contact import, and you can bring in your entire client list during your first week without losing any of the relationship history you stored in notes or tags.

Once the contacts are in, you can create booking links for each service (one link per service, each with its own length, price and optional deposit), set up appointment reminders by text or email on a schedule you choose, and turn on ready-made automations like missed-call text-back, new-lead follow-up, or a win-back text 60 days after the last visit. Starter and higher plans include texting, so if you're moving from a spreadsheet or a tool that didn't have integrated messaging, you'll go from managing client communication across three apps to handling everything—texts, email, calls and web chat—in one shared inbox.

Relay's automation features (available on every plan, with Pro removing the cap) let you follow up with new imports automatically. For example, you could create a one-time automation that sends a welcome text to every contact imported in the past seven days, introducing your team and sharing your booking link. That turns a static import into an active re-engagement campaign without manual copy-paste for each client.

Full details on what each plan includes and monthly seat and text allowances are at pricing.

Frequently Asked Questions

What file format do I need to import contacts into a CRM?

Most CRMs accept CSV (comma-separated values) files for contact imports. Export your client list as a CSV from your current system, spreadsheet or database, then upload it to the new CRM's import tool. If your old system only exports Excel or vCard files, open the file in Google Sheets or Excel and save it as CSV before importing.

Can I import contacts if I have them in a spreadsheet or on paper cards?

Yes. If your client list lives in Google Sheets, Excel or another spreadsheet, save the file as CSV and import it directly. If you have paper cards, you'll need to type the information into a spreadsheet first—create columns for first name, last name, phone and email—then export that sheet as CSV and import it. It's tedious for a large list, but it's a one-time project that saves you from re-entering clients one by one in the CRM.

Will importing contacts create duplicates if some clients are already in the new CRM?

Most CRMs check for duplicates during import by matching phone number or email address. If a contact with the same phone or email already exists, the CRM typically updates that record with any new information from the CSV instead of creating a second entry. Check your CRM's import documentation to confirm how it handles duplicates—some let you choose whether to update, skip or create a new record.

How do I clean phone numbers before importing so texts don't bounce?

Standardize phone numbers to a single format before you import—either ten digits with no punctuation (5551234567) or E.164 international format (+15551234567). Use find-and-replace in your spreadsheet editor to remove parentheses, dashes and spaces, then scan the phone column for entries with fewer than ten digits or any letters. Fix or delete those rows so the CRM doesn't try to text an invalid number. If your CRM requires country codes, prepend +1 to every US number.

What happens to appointment history when I import contacts?

Contact imports bring over names, phone numbers, emails and notes, but they do not import structured appointment records (dates, times, services) unless your CRM has a separate appointment-import tool. If you need to preserve appointment history, copy the relevant details into a notes column in your CSV before you import (for example, "Last visit: 3/10/2025, balayage"), or export appointments separately if your CRM supports calendar-event imports. Many service businesses start fresh after a migration and keep the old system's export as a reference file.

Can I import custom fields or tags along with contact names and numbers?

Yes, if the CSV includes a column for tags or custom properties and your CRM supports those fields. During the mapping step, match your spreadsheet's tag or custom-field column to the corresponding field in the CRM (or to a general notes field if the CRM doesn't have that exact property). Some CRMs require you to create custom fields before import, so check the settings or documentation first. If your old system exported tags as a comma-separated list in one cell, most CRMs will parse that and apply each tag individually.

Make the Switch Without Losing What You've Built

Moving your client list to a new CRM doesn't have to mean starting over. A clean CSV export, a careful column-mapping step, and a test run before you import the full file will carry your contacts—and the context you've built around them—into the new system intact. Plan the import during a slow afternoon, keep the original export as a backup, and spot-check the results before you send your first message or book your first appointment. The hour you spend on preparation saves you days of manual cleanup and ensures that the phone number you dial or the email you send reaches the client you're trying to serve.

When you're ready to bring your client list into a tool built for service businesses—with one shared inbox for texts, email and calls, booking links for every service, appointment reminders you set once and automations that follow up when you can't—visit gorelaycrm.com to see how Relay handles the contact import and everything that comes after.