Export Google Contacts and keep a dated copy outside the address book you are about to change. Sync makes changes travel between devices; an independent export preserves a point in time.

Back up before changes that affect many people

Useful checkpoints include moving to a different Gmail account, importing a large file, merging duplicates, or connecting a tool that can update contacts. Make the backup before the operation, not after you discover a problem.

If you manage multiple Google accounts, back up the source and destination separately. Name each file with the account role and date so you will not confuse an old source export with the destination’s pre-import state.

Make the export

Open Google Contacts on a computer and confirm the signed-in account. Use Export, select the intended contacts and choose a suitable format. Google CSV is useful for a later Google import; vCard can be useful when moving to other contact applications.

For a broad safety copy, make sure the scope covers the full collection you intend to protect rather than only a search result or a label. Save the export somewhere you can find again without depending on the phone you are replacing.

Give the backup a quick integrity check

  1. Check the filename, file size and storage location.
  2. Inspect a recent card and a card with several phone or email fields.
  3. Confirm that names and international numbers look correct.
  4. Record which account and collection the file represents.

Do not edit your only backup in a spreadsheet. Make a working copy if you need to clean data; automatic formatting can change values. A backup you accidentally modified is a weaker recovery point.

Plan the recovery before you need it

Importing a backup usually adds records to a destination; it should not be assumed to restore every aspect of an account exactly or remove later duplicates. If the problem is a recent deletion, check Google’s built-in recovery options before reimporting the entire backup.

Keep both the before-change file and a verified after-change file until the migration has settled. Store them privately and delete obsolete extra copies when appropriate for your own retention needs.

There is no single backup interval that suits everyone. At minimum, create a fresh snapshot before a large operation and after adding information you would not be able to reconstruct easily.