Import a VCF or vCard file into Google Contacts

Check the file and the destination

Start with the file extension and the destination account. A vCard file ends in .vcf; it can contain one person or a whole collection. An Apple Contacts archive ends in .abbu. These are different formats: changing the filename does not convert an archive into a vCard.

Record which account or list supplied the file and roughly how many people you expect. If you exported All Contacts on a device with several accounts, the file may overlap with records already in Google. For a more controlled transfer, export the particular iPhone contact list you intend to move.

Can you import an Apple Contacts archive into Google?

Google documents CSV and vCard imports, not Apple’s .abbu archive format. If the original contacts are still available on your Mac, select the intended cards in Contacts and choose File → Export → Export vCard. The separate Contacts Archive export creates an .abbu file instead.

If you only have the archive, do not casually open it in your everyday Contacts collection. Apple says importing an archive replaces current contact information. Preserve both the archive and your current contacts first; restore it only in a suitable recovery environment, then export the recovered cards as vCard. Ask Apple Support for help if you cannot isolate that recovery from your live accounts.

If the contacts are also available on iCloud.com, the iCloud-to-Google export route avoids archive restoration entirely. Use the original source whenever possible instead of uploading your address book to an unfamiliar conversion website.

Use Google Contacts on the web

Before importing, export the existing Google address book if it contains records you need. Keep that baseline separate from the incoming file.

1. On a computer, open Google Contacts and confirm the signed-in email address.
2. Select Import in the side menu, then Select file. Expand the menu if it is hidden.
3. Choose your .vcf file and select Import.
4. Wait for the result and check a few expected names before uploading another batch.

Save the original file unchanged. If your destination already contains some of the same people, plan to review the imported records rather than treating a larger contact count as proof of a clean transfer.

Verify the fields you rely on

Use a small verification sample with different kinds of information. The following checks distinguish a useful transfer from an upload that merely finished:

• Identity: compare one recent contact and one older contact with the originals.
• Numbers: check a card with both mobile and work numbers, including country codes.
• Text: inspect accents, non-Latin names, postal addresses and notes you rely on.
• Extra fields: look for photos and labels, whose representation can differ between systems.

If a detail seems missing, open the full card and inspect its notes. When exporting from Mac Contacts, the vCard settings also control whether notes and photos are included; Google cannot import a field that was omitted from the file.

If something is wrong, avoid a blind retry

A failed upload and a completed upload with an unexpected result need different next steps. Start with the file-format and import-limit checks if Google rejects the file. If cards appeared, inspect those records before repeating the import.

For a field problem, make a new small export containing one affected card and one ordinary card. Compare that file with the destination. This narrows the issue without repeatedly adding the entire collection. Keep a short record of filenames and results so you can tell which batches already succeeded.

If overlapping records remain, use the Google duplicate cleanup guide. To see the imported cards on your phone, connect the destination Google account to iPhone Contacts. Importing a file does not itself configure the phone or keep the original Apple address book synchronized.