w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

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

Prepare a Google Contacts export and choose a scoped recovery route.

Immutable revision: 83c1eb179582c03617fc98e652202742b69fcbab2fc182f4843387e081e7a6a1. Publication and independent validation are separate; inspect metadata and provenance before use.

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: select one, several checked, or Selection Actions → All contacts; verify the scope, then More actions → Export and save.

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.

If recovery is needed, choose its scope first

Google's Edit or delete contacts, Recover deleted contacts, says contacts deleted in the last 30 days can leave Trash. For one saved contact on computer: Trash → check that contact → Recover. Confirm account and record; avoid All for one contact.

Deleted Other contacts do not appear in Trash; their documented recovery route undoes all changes within the past 30 days. Contacts permanently deleted from Trash cannot be recovered. Missing record or deletion date: recovery remains unresolved.

Undo changes to contacts documents Settings → Undo changes → choose a time → Confirm, affecting all changes in the past 30 days at once. Contacts added after that time will not appear; Google recommends exporting current contacts so they can be added back later. Resolve scope, time and preservation of later good changes before considering bulk restoration.

Evidence and refresh: All four linked Google pages were independently reopened by this author through 2026-10-05T11:09:25Z; no visible update dates were shown. Sixteen synthetic manual decisions checked this revision. No account, selection, export, import, Trash recovery or Undo action occurred. Field preservation, duplicate handling and recovery outcomes remain unobserved. A distinct same-controller source and practical check was completed; shared control provides no independent formal coverage. Recheck before use, after changed account/surface/control guidance, and by 2026-11-05T11:09:25Z.

The exact previous edition [current article] retains original authorship, the four-source checks dated October 5, 2026 and nine distinct internal manual decision checks. Those attributed historical checks are not new account observations. Prior reference clocks remain preserved. Follow the contact standard [current article].

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.

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.