Fix "The File You're Importing Isn't Formatted" in Google Contacts

Few errors are as frustrating as Google Contacts telling you "the file you're importing isn't formatted correctly" and then refusing to say why. The message gives no detail, but in practice the causes are a short, fixable list: headers Google doesn't recognize, the wrong encoding, a file that isn't really a CSV, or a list that's simply too big for one batch. Here's how to diagnose which one you've hit and get your contacts in cleanly.

How the Import Actually Works

Google Contacts reads your file's first row and tries to map each column name onto one of its own contact fields. It understands its own export vocabulary (the headers you get when you export from Google Contacts) and the common Outlook-style CSV headers (First Name, Last Name, E-mail Address, and so on). Anything it can't map gets ignored or, if too little maps, the whole file is rejected with the vague formatting error. That's the key insight: the error is almost never about your data — it's about the header row.

Cause 1: Header Row Doesn't Match

The most common failure is a mapping mismatch — your headers don't line up with anything Google recognizes, usually because the file came from another system with creative column names like "Primary Email," "Mobile #," or "Full_Name." The reliable fix is to start from Google's own template: in Google Contacts, select any contact and use Export to download a Google CSV. Open it, keep the header row exactly as is, and paste your data under those headers.

Headers Google can't map:
Full_Name,Primary Email,Mobile #,Company Name

Headers from another CRM that also fail:
contact_name,email_1,cell_phone,org

Safe: copy the exact header row from your own Google Contacts
export and place each value under the matching column, e.g.
name columns, E-mail 1 - Value, Phone 1 - Value, organization
columns — the exact set depends on your export, so copy, don't
retype.

Watch for near-misses too: a trailing space in "First Name " or a stray BOM character in front of the first header is enough to break the match even though the header looks identical on screen.

If your list is simple — names, emails, phones — you don't need Google's full template. Google also accepts the Outlook-style CSV vocabulary, which is much friendlier to build by hand:

A minimal Outlook-style file Google Contacts accepts:

First Name,Last Name,E-mail Address,Mobile Phone
Jane,Doe,jane@example.com,+1 555 0100
Sam,Lee,sam@example.com,+1 555 0101

Use the full Google template when you need the long tail of fields — multiple emails and phones with labels, addresses split into components, notes, group memberships. Use the minimal Outlook-style headers when you just need people and their email addresses imported without ceremony.

Cause 2: Wrong Encoding

Google Contacts expects a UTF-8 CSV. A file saved from Excel with the plain "CSV (Comma delimited)" option is often Windows-1252 instead, which can fail outright or import names with corrupted accents — "Renée" arriving as "Renée." Re-save using "CSV UTF-8 (Comma delimited)" in Excel (it's a separate entry in the Save As format list), or round-trip the file through Google Sheets: File > Import, then File > Download > Comma Separated Values, which always outputs UTF-8. The corrupted-accent case is the sneaky one, because the import succeeds — you only notice weeks later when autocomplete offers you a mangled name in a new email.

Cause 3: Not a True CSV

Sometimes a file has a .csv extension but isn't comma-separated plain text at all. The three usual impostors: an Excel workbook that was renamed rather than exported (open it in a text editor — if you see unreadable binary, that's it), a semicolon-delimited file from a European system, and a file with a leftover "sep=," line above the headers from a previous Excel fix. If Google keeps rejecting the file, open it in Excel or Sheets and explicitly export to CSV again, then confirm in a text editor that the first line is your comma-separated headers and nothing else.

Cause 4: Too Many Contacts at Once

Google recommends importing no more than 3,000 contacts at a time, and the free consumer account tops out at 25,000 contacts total. Oversized imports can fail or complete only partially — which is worse than failing, because you're left guessing which contacts made it. Split big lists into batches of 3,000 or fewer and import them one after another, checking the contact count between batches.

Cause 5: Junk Rows and Messy Values

A structurally fine file can still import badly. Blank rows in the middle of the list can become empty phantom contacts. Placeholder text like "N/A" or "none" in email columns imports as literal contact data. Stray whitespace around names and addresses survives the import and haunts you later in searches and mail merges. None of these trigger the formatting error — they just quietly pollute your contacts — so clean them before importing rather than after.

Rows that import but shouldn't:

First Name,Last Name,E-mail Address
 Jane ,Doe,jane@example.com     <- whitespace survives the import
,,                              <- becomes an empty contact
Sam,Lee,N/A                     <- "N/A" imports as an email address

Cleaned:
First Name,Last Name,E-mail Address
Jane,Doe,jane@example.com
Sam,Lee,

Step-by-Step: Prep a Google-Ready File

After the Import: Verify and Deduplicate

Google Contacts tags each import batch with a label, so you can review exactly what came in — and, if the mapping went sideways, select the label and bulk-delete the batch to try again cleanly. For duplicates, use the built-in Merge & fix panel in Google Contacts after importing: it finds contacts sharing names or emails and merges them with one click, which is far safer than trying to deduplicate the CSV by eye beforehand.

Before declaring victory, spot-check a handful of contacts you know well: open them and confirm the email landed in the email field, the mobile number isn't sitting in a work-phone slot, and accented names read correctly. Field-level misrouting is the failure mode the import screen never warns you about, and it's much cheaper to catch on contact three than after you've synced the mess to your phone.

The Faster Way: Automated Cleanup

Renaming a dozen columns to Google's template and scrubbing whitespace by hand gets old fast, especially for a list you sync regularly. PipeSheets handles the mechanical part in one pass: rename each source column to the exact header from your Google template, drop the columns Google doesn't need, reorder to match, trim whitespace everywhere, standardize placeholder values to real blanks, and remove empty rows — then export a clean comma-delimited UTF-8 CSV. Preview before downloading, save the steps as a pipeline, and every future export from your CRM is Google-ready in one click.