iCloud.com to Google Contacts: prepare a contact copy

For your own iCloud contacts and personal Google Account, using a computer. Privately identify both accounts, the intended people and authority to disclose their details. This prepares a file copy and later authorized import; it establishes no continuous synchronization or permission to retire the source.

Establish both inventories

Apple’s account guide, account-selection section, explains that iPhone Contacts can show multiple accounts. Review the relevant account; a phone’s combined list is not an iCloud inventory. Choosing a default account concerns new contacts, not moving existing ones.

Record the intended source scope, destination’s existing records and important fields privately. Preserve the destination baseline using the Google export guide [cited revision]. Counts help reconciliation but cannot identify people or prove field preservation.

Prepare the web export

Apple’s iCloud.com guide, Export a vCard, documents selecting one contact; Command-click on Mac or Control-click on Windows for several; or Actions → Select All Contacts for all. Then use Share → Export vCard. Multiple selected contacts produce one vCard.

Preserve the untouched private file with its account, selection and export date. This is the web route; Mac archive and privacy-setting instructions do not establish its behavior. Required notes, photos, multiple addresses and list membership need their own later comparison. No vCard version or cross-product list/field fidelity is established here.

Prepare the destination and failure branch

Google’s computer import guide, existing-file section, accepts a .vcf: in the intended Google Contacts account, use Import → Select file, choose the file, then Import. This is a later account write, not part of obtaining the copy. If an imported detail seems absent, check that contact’s Notes.

Its troubleshooting section flags more than 3,000 contacts per import, the 25,000-contact limit and unsuitable formatting. Its splitting instructions concern CSV; they are not a verified VCF-splitting recipe. Oversized or uncertain files require a separately supported plan before import.

Google’s error guidance, storage limits, also states 20 MB excluding photos; per contact, 128 KB, 500 fields and 1,024 characters per field except Notes. Contact count alone therefore does not establish fit. Preserve an error and the baseline privately; do not cut fields or delete contacts merely to force acceptance.

Inspect before repeating or merging

After a separately authorized import, compare the intended people and required values with the original and destination baseline. A completion banner or matching count is insufficient. Stop on uncertain completion, missing values or apparent duplicates; retain the source and file instead of blindly repeating the import. Retry and duplicate behavior remain unobserved.

Google’s merge guide concerns same-person duplicates within one account. Use the existing merge preparation [cited revision] for a separate identity and scope decision; similar names alone are insufficient. No automatic deduplication or lossless merge is promised.

Hand back the source selection, retained copy, destination baseline, observed or pending comparison and unresolved fields/lists. Keep source deletion, account removal, phone erasure and sync setup outside this handoff. Keep real contact files and identifiers out of public feedback.

Evidence: Five primary pages read through 2026-10-06T02:31:01Z. Apple’s account guide displays February 10, 2026; the other pages show no update date. Eighteen author manual reader decisions checked this text. No account, contact inventory, export, import, merge, sync or deletion occurred. A distinct checker under the same controller reread the five primary pages, standard and overlap articles, rechecked the author decisions and exercised ten additional boundaries. These source and desk checks supply no independent formal review. Recheck before use, after changed controls, account scope or required fields, and by 2026-11-06T02:31:01Z. Follow the contact standard [current article].