Before editing or moving Google Contacts: choose and preserve an export

For someone preparing to export their own Google Contacts on a computer before editing contacts or moving them to another account. This is a source-based preparation procedure: no account, contact selection, download, import or recovery was observed. Phone/SIM backups, delegated contacts and organization-wide Directory exports need different scope. An export file is a copy of the chosen data, not proof that another product will preserve every field.

Decide which contacts the copy must cover

Privately record the source account, purpose, intended selection and destination before downloading anything. A copy for a few selected contacts and a backup of all personal contacts are different artifacts. Keep the account identity and contact details private; a shared handoff can describe the scope without publishing an address book.

Google's computer export instructions, Export contacts, distinguish a single contact, several checked contacts and all contacts through Selection Actions → All. Do not assume selecting one contact selects the whole account. Verify the intended selection before using More actions → Export and saving the file.

Two boundaries can prevent the expected export:

• The same guide says work/school users cannot select all contacts in the Directory. “All” personal contacts is not a claim to have copied the organization's directory.
• Google's delegation guide, About what delegates can and can't do, says delegates cannot export or forward contacts. Being able to edit a delegated list does not establish export capability. Hand the export task to its owner rather than broadening the selection or account scope.

If the account, list or selection is uncertain, resolve it before export. If the documented control is missing, inspect the current help and selected surface instead of guessing an alternative account action. Google's import guide also describes a top-right Export route under From a Google Account; these are published instructions, not a verified current screen layout.

Choose the file for the purpose

Purpose	Documented choice and remaining question
Keep a Google Contacts backup before edits	Google specifically recommends Google CSV in Export contacts. Retain the downloaded original separately from any working copy.
Move to another Google account	Google's import guide, From a Google Account, uses Google CSV export followed by import in the other account. Confirm the source and destination account independently before any later import.
Move to a different product	The export guide describes CSV or vCard downloads. Check that destination's current import documentation for accepted format, version and field limits before choosing. A request for vCard does not establish compatibility with every vCard version or every field.

Google's Import from an existing CSV or vCard file recognizes .csv and .vcf files. File extensions identify the intended format; they do not verify correct contents or lossless transfer. If the destination or its requirements are unknown, keep the Google backup and leave the migration format unresolved. Do not choose a universal “best” format from this procedure.

Preserve the original and separate later actions

As a preparation practice, retain the untouched download privately and edit a separate copy. Keep a private note of the source account, selected scope, export time, chosen format and saved-file location. Verify that the file exists and review the fields important to the intended move in an appropriate private viewer before relying on it. Preserve the original if a viewer or editor changes values. A file that opens, a record count or a local parse does not prove destination field preservation.

For preparing a Google import CSV, use the pinned CSV preparation guide [cited revision]. Its fictional exact-template checker tests local strings; it is not an automatic validator for arbitrary Google export files. The two-email experiment [cited revision] retains separate, untested Google mapping questions. Neither establishes that an export can restore the account or migrate every field.

Downloading a backup, editing the account, importing to a destination and deleting the source are separate operations. An export request does not authorize the latter actions. Before a later authorized migration, resolve important field and duplicate behavior; if the result is uncertain, inspect it before retrying or deleting originals.

Do not treat Undo changes as a narrow rollback

Edit or delete contacts, Undo changes to contacts, describes undoing all changes during the past 30 days at once. Its warning says contacts added after the chosen restoration time will not appear, and recommends exporting current contacts so they can be added back later. This is why preserving current scope matters before bulk restoration; it is not an instruction to perform a restore now.

The same guide says contacts permanently deleted from Trash cannot be recovered. Deleted Other contacts do not appear in Trash; its documented recovery route is undoing all changes within the past 30 days, with the broader effects above. Do not assume an export or the Undo control makes every deletion recoverable. Recovery availability and restoration results remain unobserved here.

Evidence and refresh: Google's four public computer help pages checked October 5, 2026; no visible page-update dates were shown. Selection coverage, export bytes/fields, CSV encoding, vCard version, import mapping, duplicate behavior and recovery outcomes were not tested. A distinct internal checker reopened all four official pages on 2026-10-05T04:34:12Z and performed nine additional manual decision checks. Author and checker share the site controller; these source/desk checks are not independent review or product tests. Recheck before use, after an account/surface, format or documented-control change, and at the next editorial review on November 5, 2026.

Feedback: identify the exact revision, product/surface, intended selection, unclear format or step, check date and public source or actual result. Keep real exports, names, addresses, phone numbers and private file locations out of public feedback.