Text and data

How to Format and Map a Google Contacts CSV Import

When migrating contact address books from Microsoft Outlook, Apple iCloud, or internal customer spreadsheets into Google Contacts, the import frequently fails or omits phone numbers because of column header mismatches and strict formatting specifications.

Diagram showing input CSV column mapping, phone normalization, and batch export into Google Contacts format.
Google Contacts import workflow: map custom headers to canonical schema, normalize phone digits, and partition at the 3,000-contact limit.

What to run

Open Google Contacts CSV Import Mapper in your browser and upload your exported contact spreadsheet. If your file was exported from Outlook, Apple Contacts, or Excel, the parser inspects your column headers locally without transmitting personal contact details over the network.

Review the suggested column mappings. If your source file combines names into a single column (such as "Full Name" or "Contact Name"), assign it to the Full Name auto-splitter so it separates into First, Middle, and Last Name fields.

How to read the result

Ensure that telephone numbers are mapped to paired columns like "Phone 1 - Value". Google Contacts rejects standalone column headers like "Mobile" or "Phone" unless paired with an associated type field.

If your address book exceeds 3,000 contacts, verify that the tool has partitioned your export into sequential batches (e.g. Part 1, Part 2). Google Contacts enforces a hard ceiling of 3,000 contacts per single import operation.

What to open next

If you also possess multi-card vCard archives from iPhone or Android backups, use VCF Duplicate Remover to reconcile cross-platform duplicates prior to importing.

If your CSV contains character encoding corruptions or broken line breaks, open CSV Fixer to normalize delimiters and unescaped quote characters.

Stop when

You have downloaded your formatted CSV candidate files and imported them into contacts.google.com without column omission warnings.

Never upload personal customer address books to untrusted cloud conversion APIs when local browser transformations preserve your data privacy.

References

Continue troubleshooting

Related tools

Frequently asked questions

Why does Google Contacts show empty fields after importing a CSV?

Google Contacts expects exact header strings such as Given Name and Phone 1 - Value. Generic column titles like Name or Mobile are ignored during import unless mapped to Google’s schema.

What is the maximum number of contacts Google allows per CSV upload?

Google Contacts allows a maximum of 3,000 contacts per single CSV upload batch. Files exceeding this limit trigger an import error and must be partitioned.

Does Google Contacts support custom field headers?

Google Contacts accepts standard headers and preserves extra fields if properly formatted, but custom columns are often placed in the general Notes field rather than structured profile attributes.

Need help with a tool or found a bug?

Report an issue directly to engineering. No accounts required — all client data remains private on your device.

Report an Issue →