Free - No signup - Your address book stays in your browser

Preflight a Google Contacts CSV.

Map ordinary spreadsheet columns into Google's current template, check dates, phones, labels and limits, then export a 100-row test and safe 3,000-row batches.

A Google Contacts CSV preflight maps source headers into the current Google template, validates locally provable field and size rules, and splits ready output into imports of at most 3,000 contacts. This private workspace never signs in to Google or sends contact values away from the tab.

01 - How it works

Turn a spreadsheet into a reviewed contact handoff.

Every source column receives an explicit Google role. The complete file is checked locally before any contact-data download is enabled.

i. load

Open CSV or Excel

Drop a source, paste comma CSV, or load an imperfect or ready sample. Excel is converted locally because Google Contacts uploads CSV or vCard.

ii. map

Review roles and labels

Confirm name, email, phone, address, organisation, date, website, relation, custom, Notes, Labels, or Ignore for every source column.

iii. test

Export controlled batches

Resolve blockers, acknowledge the account handoff, then download the first 100 contacts and source-order batches of at most 3,000.

02 - What it checks

Evidence before address-book mutation.

The desk validates what the file can prove and labels every account-dependent uncertainty for review.

  • 01

    Current template roles

    Construct official name, repeated label/value, address, organisation, birthday, Notes, and Labels fields from explicit choices.

  • 02

    Contact formats

    Check emails, optional phone punctuation, country-code review, real DD-MM dates, and exact ::: label separation.

  • 03

    Storage boundaries

    Enforce 1,024 characters per non-Notes field, 500 fields, 128 KB of mapped text, and the 3,000-contact import batch.

  • 04

    Account handoff

    Keep backup, target account, 25,000-contact quota, duplicate merging, labels, and final acceptance as visible Google-side reviews.

"A clean contact file is not proof that the target account, duplicates, or labels are ready."
csvtodashboard.com
Scope and handoff

Know what a local check cannot see.

The preflight never signs in to Google or invokes the Contacts API. Account and post-import state still require human review.

  • CSV handoff

    Google Contacts accepts CSV or vCard. Excel and pasted sources are local preparation paths that end in reviewed Google-format CSV.

  • No account state

    Access, current contact count, 20 MB storage, directory permissions, backups, existing labels, and duplicate suggestions are not queried.

  • No acceptance guarantee

    Back up as Google CSV, import at most 100 test contacts, inspect representative records, then continue one 3,000-row batch at a time.

03 - FAQ

Google Contacts CSV questions.

Can I validate a Google Contacts CSV before importing it?
Yes. This local preflight maps source columns into Google's current template, checks contact fields and documented limits, and creates a first-100 test plus maximum-3,000-contact batches. It cannot query your Google Account or guarantee acceptance.
No. Parsing, mapping, validation, masked evidence, batching, and downloads remain in the current browser tab. Contact values are not sent to Google or csvtodashboard.
Google's documented Contacts import accepts CSV or vCard. The validator can read one Excel sheet locally, map it, and download Google-format CSV without uploading the workbook.
Google documents a maximum of 3,000 contacts in one import. The validator preserves source order and creates selectable batches of at most 3,000 rows.
Use DD-MM-YYYY when the year is known or DD-MM-- when it is not. The validator checks that the day and month form a real date.
Use three colons between nonempty label names, such as Work friends ::: Family ::: Project11.
Do not assume it will. Google provides a separate Merge and fix workflow after import. The validator blocks exact duplicate rows and flags repeated email or phone values for review without predicting a merge.
No. The tool can enforce per-row field and byte limits, but the 25,000-contact and 20 MB account ceilings depend on existing account contents and require Google-side review.
Related tools
Google Contacts CSV import guide
Use the current template, prepare fields, split batches, test, and troubleshoot.
Open →
CSV to vCard
Create a local VCF contact file when vCard is the better handoff.
Open →
CSV column mapper
Translate an upstream export into a reviewed destination schema.
Open →