How to Prepare CSV for Google Contacts Import

By Online CSV Editor · Last updated: 2026-04-11

The safest way to prepare a Google Contacts CSV import is to start from the contact fields you actually need, then clean names, emails, phone numbers, labels, and duplicate risk before a full upload. Most Google Contacts import problems come from contact hygiene and field-shape issues rather than from CSV as a file format.

If this file is part of a broader handoff workflow, start with the CSV import and export guide. If the source file still needs cleanup first, pair this page with how to validate email columns in CSV and how to normalize phone numbers in CSV.

Quick answer

  1. Start from a known-good Google Contacts export or a tested contact template instead of guessing columns.
  2. Keep one contact per row and remove CRM-only fields that do not belong in a shared address book.
  3. Normalize names, email addresses, phone numbers, and labels before import.
  4. Check duplicates so you do not create multiple versions of the same person.
  5. Run a small test import first to confirm mapping and contact formatting.

What Google Contacts CSV format really means

People search for google contacts csv format as if there is one universal spreadsheet shape. In practice, Google Contacts imports work best when the file behaves like a clean address-book handoff: one person per row, recognizable contact fields, and normalized values for names, emails, phones, companies, and labels.

  • Headers need to match contact intent. Generic CRM exports often include fields that do not belong in Google Contacts.
  • One row should represent one person. Mixed records or multi-contact rows create messy imports.
  • Phones and emails need normalization. Duplicates, placeholders, and mixed formatting make contact books harder to trust.
  • Labels and groups should stay deliberate. Importing stale segments, pipeline stages, or internal notes usually creates clutter instead of useful organization.

Step-by-step: how to prepare a Google Contacts CSV import file

  1. Start with the destination schema. Use a recent Google Contacts export or a trusted template as your reference instead of inventing column names from memory.
  2. Trim the file to real contact fields. Keep names, emails, phones, organization fields, notes, and useful labels. Drop CRM-only properties, pipeline values, and operational metadata that do not belong in a personal or team contact book.
  3. Normalize the identity fields. Standardize first and last names, confirm which email should be primary, and format phone numbers consistently before upload.
  4. Review labels, company names, and notes. Make sure categories are readable and intentional. Avoid importing stale internal tags that only made sense in the source system.
  5. Check duplicate risk. Look for repeated people across work and personal exports, alias emails, or phone-number variants that would create multiple contact cards for the same person.
  6. Test a small batch. Import a limited sample so you can verify field mapping, duplicate handling, and the way names, labels, and notes appear in Google Contacts.

Common Google Contacts CSV mistakes

  • Uploading a CRM export full of fields that do not belong in a contact book.
  • Keeping malformed or duplicate email addresses and inconsistent phone-number formats.
  • Using vague labels, internal tags, or pipeline-stage values as if they were contact groups.
  • Combining multiple people into one row or splitting one person across multiple rows unnecessarily.
  • Running a full import before checking how a smaller sample appears inside Google Contacts.

Example: cleaning an event attendee export for Google Contacts

Imagine you export attendees with columns such as First Name, Last Name, Work Email, Mobile, Company, Role, and Lead Source. The file opens correctly, but it is not yet Google Contacts-ready.

  1. Keep the contact fields you actually want in an address book and drop pipeline-only metadata.
  2. Validate email values and normalize phone numbers to one readable rule.
  3. Standardize names and company values so search and autocomplete work cleanly later.
  4. Turn useful segments into simple labels only if they still make sense outside the source system.
  5. Test a small import and review whether duplicate contacts or odd labels appear.

How this page differs from HubSpot and Mailchimp import guides

This page focuses on Google Contacts address-book import prep, not CRM property mapping or email-marketing audience setup. That keeps it separate from the HubSpot contacts CSV format guide, which is CRM-property oriented, and from the Mailchimp CSV import guide, which is audience and subscriber-list focused. If your main problem is general pre-upload QA, use the CSV import and export guide.

Quick checklist before upload

  • Headers match a trusted Google Contacts CSV shape or map cleanly to contact fields.
  • One row equals one contact, with useful names, emails, phones, and company values.
  • Emails and phone numbers are normalized enough for clean search, sync, and deduplication.
  • Only useful labels and notes remain; stale CRM-only metadata was removed.
  • A small test import succeeds before the full contact list upload.

FAQ

What format does Google Contacts want for CSV import?

Google Contacts wants a clean contacts CSV with recognizable contact-field headers, one contact per row, and normalized values for names, email addresses, phone numbers, and labels.

Why does a Google Contacts import fail even when the CSV looks fine?

Because opening the CSV only proves the table is readable. Google Contacts imports can still go badly when headers are messy, emails or phones are malformed, or duplicate records are not handled intentionally.

Should I include every column from my CRM export?

No. Keep the fields that belong in a contact book and that you actually trust. Extra operational columns usually create clutter rather than useful contacts.

Should I test a small import first?

Yes. A small test import is the safest way to confirm mapping, labels, and duplicate behavior before you upload the full file.

Use Online CSV Editor before the final upload

Use the editor to review contact headers, normalize phones and emails, remove duplicate-risk rows, and trim noisy metadata before you import a CSV into Google Contacts.

Open the CSV editor

Canonical: https://csveditoronline.com/docs/google-contacts-csv-format