Skip to content

Booking, CRM and Follow-Up

Exporting Contacts to CSV Without Breaking Your Data

How to export contacts to CSV and import them elsewhere intact: column mapping, phone and ZIP formats, dates, duplicates and a ten-row test first.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing8 min read

On this page
  1. The damage happens after the export
  2. Know what is in the file
  3. Open the file without letting the spreadsheet rewrite it
  4. Clean the file in a fixed order
  5. Import ten rows first
  6. Look after the file itself
  7. Frequently asked questions
  8. References
Booking, CRM and Follow-Up: Exporting Contacts to CSV Without Breaking Your Data15 digits: is the most Excel keeps for a number; it also drops leading zeros unless the column is textBOOKING, CRM AND FOLLOW-UPExporting Contacts to CSVWithout Breaking Your Data15 digitsis the most Excel keeps for a number; it alsodrops leading zeros unless the column is textAssistCallInsightsBooking, CRM and Follow-Up: Exporting Contacts to CSV Without Breaking Your Data15 digits: is the most Excel keeps for a number; it also drops leading zeros unless the column is textBOOKING, CRM AND FOLLOW-UPExporting Contacts toCSV Without BreakingYour Data15 digitsis the most Excel keeps for a number;it also drops leading zeros unless thecolumn is textAssistCall
Figure source: Microsoft Support, 2026[1]

Key takeaways

  • The export rarely breaks data; opening and re-saving the file in a spreadsheet does, so keep the original untouched.
  • Open CSVs through the import tool with phone, ZIP and ID columns set to text, and save as UTF-8.
  • Clean in a fixed order: phone format, names, duplicates, tags, dates, then remove what should not travel.
  • Import ten rows first and check each record by hand before running the full file.
  • A contact export is a file of personal data: share it carefully and delete working copies after the import.

The damage happens after the export

Exporting contacts to CSV takes one click. The damage usually happens in the next five minutes, when someone double-clicks the file, the spreadsheet reformats three columns on the way in, and the file gets saved back over the original. The procedure below keeps the data intact from the system it leaves to the one it lands in.

CSV itself is simple, which is why it travels everywhere. The format documented in RFC 4180 puts one record per line, separates fields with commas, wraps any field containing a comma, a line break or a double quote in double quotes, and writes a double quote inside a field as two double quotes[2]. Contact notes contain all three characters all the time, so a file that looks fine on screen can still split a note across two columns if one tool in the chain ignores the quoting.

The common reasons to export are moving to a new CRM, loading contacts into an email or texting tool, handing a list to a bookkeeper, or simply keeping a backup you control. The steps are the same for all of them. Only the column mapping changes.

Know what is in the file

Open the export in a plain text editor first, not a spreadsheet, and read the header row and the first few lines. You are checking three things: which columns exist, how phone numbers and dates are written, and how multi-value fields such as tags are joined.

Example: when an SI Employee answers your calls, each new caller number becomes a contact, and the standard contact list in your AssistCall account exports twelve columns: name, phone, email, tags, notes, last_call_at and created_at, then preferred_name, organization, birthday, vip and other_phones. US and Canadian numbers are stored as +1 followed by ten digits and numbers from elsewhere keep their own country code. Tags and extra phone numbers are joined with semicolons, every field is wrapped in double quotes, and the two dates are full timestamps in UTC. Birthdays are month and day only, such as 03-14, which a spreadsheet will quietly turn into a full date in the current year. Other systems differ in the details, but the questions in the table below apply to any export.

Column mapping for a typical contact export, and what to watch for in each column
Export columnUsual target fieldWatch for
nameFull name, or First name plus Last nameSplitting Mary Ann Lee into Mary and Ann Lee; blank names on callers who never gave one
phoneMobile or PhoneThe plus sign dropped, or the number shown as 1.31256E+10 after a spreadsheet opens it
emailEmailBlank cells; the same email on two contacts, which some tools reject
tagsTags or LabelsSemicolon-joined values; the target may want commas or one column per tag
notesNotes or DescriptionLine breaks and quotes inside the field; a length limit in the target
last_call_atA custom date fieldUTC timestamps; evening calls can land on the next day if only the date is kept
created_atCreated date or a custom fieldMany tools overwrite the created date with the import date
birthdayBirthday or a custom date fieldMonth and day only; a spreadsheet adds a year, and some targets reject a date without one
other_phonesSecond phone fieldsSeveral numbers in one cell, joined with semicolons, some with an extension after an x

Decide before you start which target field each column feeds, and write the mapping down. A ten-line mapping note saves the second import, which is always messier than the first because half the contacts already exist.

Open the file without letting the spreadsheet rewrite it

Double-clicking a CSV hands it to the spreadsheet's guesswork. Excel automatically removes leading zeros, keeps at most 15 significant digits and turns long numbers into scientific notation such as 1.23E+15; Microsoft lists phone numbers among the data it affects[1]. A phone value like +13125550142 can lose its plus sign and display as 1.31256E+10. ZIP codes in New England, New Jersey and Puerto Rico begin with 0, and a column of them loses the zero the same way. If the file is then saved, the damage is permanent.

  1. Copy the original and lock it

    Keep the downloaded file read-only in a folder named for the date. Work on a copy. If anything goes wrong, you export again or start from the original.

  2. Use the import tool, not double-click

    In Excel, use Data, From Text/CSV, and set phone, ZIP and ID columns to Text before loading; Microsoft recommends this route[1]. In Google Sheets, import with the option to convert text to numbers and dates switched off.

  3. Check the encoding

    Names like José or Nguyễn should look right. If you see stray symbols in their place, re-import with UTF-8 encoding selected.

  4. Save as CSV UTF-8

    When you save the cleaned copy, choose the UTF-8 CSV option so accented names survive the trip to the next system.

Clean the file in a fixed order

Order matters because each step makes the next one easier. Merging duplicates before phone numbers share a format, for example, misses every pair written two ways.

  1. Put every phone number in one format: +1 and ten digits for US and Canadian numbers. Country code 1 covers 20 North American countries[3], so do not assume a +1 number is in the US, and never add +1 to a number that starts with another country code.
  2. Split names only if the target insists on first and last name fields. Check two-word first names and surnames with particles, such as de la Cruz, by eye.
  3. Merge duplicates on phone number first, then on email. Keep the row with the most notes and the oldest created date.
  4. Rewrite tags in the format the target wants: semicolons to commas, or one column per tag. Remove tags that only meant something in the old system.
  5. Convert timestamps to the date format and time zone the target expects. Keep the original column next to the converted one until the import is checked.
  6. Remove what should not travel. The FTC's advice is to keep only what you need and to dispose of what you no longer need[4]: card numbers or ID numbers that crept into notes come out now.
  7. Flag stale records. About 35 million phone numbers are disconnected and made available for reassignment each year[5], so contacts with no call in eighteen months or more should be tagged for checking, not loaded straight into a calling or texting list.

One more phone check is worth the time. Many customers, especially older ones, still give a landline. Among US adults aged 65 and over, 57.9% lived in wireless-only households in late 2024, against 88.9% of those aged 25 to 29[6]. If the target has separate mobile and home fields, map carefully, and if a contact has two numbers, keep both rather than letting one overwrite the other.

US adults living in wireless-only households, by age, July to December 2024Adults with their own cellphone and no landline at home.
US adults living in wireless-only households, by age, July to December 2024Bar chart. 18 to 24: 85%; 25 to 29: 88.9%; 30 to 34: 88.1%; 35 to 44: 88.3%; 45 to 64: 79%; 65 and over: 57.9%.18 to 2418 to 24: 85%85%25 to 2925 to 29: 88.9%88.9%30 to 3430 to 34: 88.1%88.1%35 to 4435 to 44: 88.3%88.3%45 to 6445 to 64: 79%79%65 and over65 and over: 57.9%57.9%US adults living in wireless-only households, by age, July to December 2024Bar chart. 18 to 24: 85%; 25 to 29: 88.9%; 30 to 34: 88.1%; 35 to 44: 88.3%; 45 to 64: 79%; 65 and over: 57.9%.18 to 2418 to 24: 85%85%25 to 2925 to 29: 88.9%88.9%30 to 3430 to 34: 88.1%88.1%35 to 4435 to 44: 88.3%88.3%45 to 6445 to 64: 79%79%65 and over65 and over: 57.9%57.9%

Source: CDC National Center for Health Statistics, 2025[6]

Show the data
ItemValue
18 to 2485%
25 to 2988.9%
30 to 3488.1%
35 to 4488.3%
45 to 6479%
65 and over57.9%

Import ten rows first

Every import tool has quirks that only show on real data. Pick ten rows that cover your awkward cases, import those, and open each resulting record by hand before running the full file.

Example: moving contacts from one system to another
  • Your team
  • System
  1. 01Your team

    Export the contacts

    Download the CSV; keep the original read-only.

  2. 02Your team

    Open as text

    Import tool with phone, ZIP and ID columns set to Text.

  3. 03Your team

    Clean in order

    Phones, names, duplicates, tags, dates, removals, stale flags.

  4. 04System

    Test ten rows

    Import the awkward cases and open each record by hand.

  5. 05System

    Run the full file

    Import the rest with the same mapping and settings.

  6. 06Your team

    Reconcile the counts

    Rows in the file equal records created, updated and skipped.

Example sequence for a small business contact migration. Keep the mapping note with the original export.

  • A contact with a long note containing commas, quotes and a line break: the note arrives whole, in one field.
  • A contact with an accented name: the name reads correctly.
  • A contact with three tags: three separate tags, not one tag with semicolons in it.
  • A contact whose last call was in the evening: the date matches the day the call happened in your time zone.
  • A contact with no name: the record imports and does not get a placeholder like Unknown.
  • A contact that already exists in the target: it updates rather than duplicates, or the tool tells you why not.

Example: a call at 9:30 pm Eastern on March 3 is stored as 02:30 UTC on March 4. If the target keeps only the date, the call moves to the wrong day and every follow-up keyed on it shifts by one. Catching that on ten rows takes a minute; catching it after two thousand takes an afternoon.

After the full import, reconcile the numbers. Rows in the cleaned file should equal records created plus records updated plus rows skipped, and every skipped row should have a reason in the import report. Anything unexplained gets fixed before anyone starts working from the new system.

Look after the file itself

A contact export is a list of your customers' names, numbers, emails and notes in one portable file. Treat it like the cash drawer. Share it through a link with access control rather than an email attachment, never leave it in a downloads folder on a shared computer, and delete the working copies once the import is reconciled. Keep one dated original in a secure place if you need a backup.

Clean exports start with clean records. The rules in turning callers into contacts prevent most of the cleanup above, and CRM for small business covers choosing the system the file is going to. If the contacts are headed for a texting tool, read the consent notes in the follow-up text templates before anyone presses send. What an SI Employee is explains how calls create these records in the first place, and the small business buyer's guide puts it alongside the other ways to answer the phone.

Teams moving lead records between agents see the problem at its sharpest; the real estate team example shows lead calls feeding a shared system, and the real estate guide to migrating to a new CRM without losing data covers the move from a brokerage's point of view.

Frequently asked questions

Why do my phone numbers look like 1.31E+10 after I open the CSV?

The spreadsheet read them as numbers and switched to scientific notation. Close without saving, then open the file through the import tool with the phone column set to Text.

Should I export contacts as CSV or vCard?

CSV for moving contacts between business systems, because every CRM and email tool can map its columns. vCard suits phones and address books, and carries less of the business history.

How do I keep the leading zero on ZIP codes?

Set the ZIP column to Text before the data loads, using the import tool rather than double-clicking the file. Re-typing zeros by hand afterwards is error-prone.

What if the new system rejects some rows?

Read the import report, fix the rows it lists in your cleaned file, and import only those rows again. Common causes are duplicate emails, invalid phone formats and missing required fields.

How often should I export my contacts as a backup?

Monthly is a sensible rhythm for a small business, kept as a dated, access-controlled file. Delete older backups you no longer need rather than letting copies pile up.

References

  1. Microsoft Support (2026). Keeping leading zeros and large numbers (opens in a new tab) ↑

  2. IETF (RFC Editor) (2005). RFC 4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files (opens in a new tab) ↑

  3. North American Numbering Plan Administrator (NANPA) (2026). About the North American Numbering Plan (opens in a new tab) ↑

  4. Federal Trade Commission (2016). Protecting Personal Information: A Guide for Business (opens in a new tab) ↑

  5. Federal Communications Commission (2018). Advanced Methods to Target and Eliminate Unlawful Robocalls, Second Report and Order (FCC 18-177) (opens in a new tab) ↑

  6. CDC National Center for Health Statistics (2025). Wireless Substitution: Early Release of Estimates From the National Health Interview Survey, July-December 2024 (opens in a new tab) ↑

Book a demo

Meet your SI Employee.

Book a short demo. We walk through calls like yours and show what your SI Employee would answer, book and follow up.

Book a demo