Check the file format, batch size, account capacity and actual imported records before retrying. A rejected upload and a successful import with unexpected fields need different fixes.

Check Google’s documented limits

Google lists importing more than 3,000 contacts at once and reaching 25,000 contacts in the account among causes of import problems. For larger CSV collections, split the work into smaller batches while preserving the header row.

Before reducing a collection, export a backup. Do not delete important cards just to make an import fit. If the account is near capacity, first determine whether the source contains duplicates, obsolete data, or contacts that belong in a different account.

Check what the file really contains

Google supports CSV and vCard imports. A renamed ZIP, PDF, spreadsheet workbook or proprietary contacts archive is not converted by changing its extension. Return to the source application and export a supported format. For an Apple .abbu file, see the archive-to-vCard guidance before restoring or converting anything.

For CSV, inspect the field headings and a few representative rows. For vCard, try re-exporting a small selection from the source rather than manually splitting the file at arbitrary line numbers. One record can span multiple lines, and splitting in the wrong place can damage it.

Separate partial imports from missing fields

If some cards appeared, write down what succeeded before taking another action. Check the signed-in account and search for several expected names. Inspect the full card if a phone number or note seems absent from the list preview.

Use a two-record diagnostic file: one ordinary card and one that failed or lost a field. If only the complex card has a problem, investigate that source record. If neither imports, focus on the file format and account rather than deleting the destination address book.

Retry once you can explain the change

A useful retry changes something specific: a corrected header, a smaller batch, a clean export, or the correct account. Uploading the same file repeatedly without checking the outcome can create duplicate copies and make the original failure harder to reconstruct.

Keep a short batch log with filenames, approximate counts and results. After the final import, verify important fields and export the destination as a new baseline. If the problem persists, report the exact error and a description of the source format to support; avoid attaching a full real address book to an initial support request.