Before merging Google Contacts: check the account and the people

For the owner of personal contacts in one Google Account, using Google Contacts on a computer. The purpose is to decide which suggested duplicates, if any, should be merged. This is documented preparation, not a verified merge result or a rule for matching people automatically.

Resolve the scope before accepting suggestions

First identify the account and the particular records privately. Google's merge instructions describe combining duplicate listings for the same person and say contacts saved in different Google Accounts cannot be merged. This guide does not authorize moving contacts between accounts to work around that boundary.

If you are working in someone else's delegated list, stop this merge workflow. Google's Workspace delegation guide, About what delegates can and can't do says delegates cannot find and merge duplicates, even though they can edit contacts. Ask the owner to handle the decision; do not change accounts or permissions to bypass the restriction.

As an editorial precaution, compare the actual records before accepting a suggestion. A matching name, shared household number or similar address alone is not proof of one person. If identity or a conflicting field is uncertain, leave the records separate and ask the owner. No field-precedence or lossless-merge behavior was established here.

Choose a bounded action

Google's computer instructions use Menu → Merge & fix. They distinguish Merge for one or more suggestions from Merge all for all suggestions. Choose the control whose scope matches the decisions actually made; reviewing one suggested pair is not a reason to accept the rest.

The help page says that without a Merge duplicates option there are no contacts available to merge in that workflow. Do not turn that interface result into proof that every real-world duplicate has been found. If the screen or selected account differs, resolve that difference before acting. Any later account change still requires the owner's authorization.

After a separately authorized merge, inspect the resulting contact and the fields that mattered to the decision. If the result is uncertain, stop further merges. A reduced contact count alone does not demonstrate that the right records or fields were preserved. No account operation was performed for this article.

Plan for mistakes before making changes

Use the export preparation guide [cited revision] to preserve the intended current scope before edits; an export is not proof of successful restoration. Keep address books and identifying details private.

Google's merge help links to Undo changes to contacts for separating merged contacts. That operation reverses all changes back to a chosen time within the past 30 days. Contacts added after that time will not appear. It is not a promised one-pair undo. Preserve current contacts and assess the effects on other edits before any separately authorized restoration. Permanently deleted Trash contacts cannot be recovered through this guidance.

Evidence: Official Google computer merge, edit/undo and delegation pages inspected 2026-10-05T05:13:05.984034Z. No source publication dates were displayed. This is source-only guidance; no contacts, account, field preservation or recovery was tested. The author checked eight manual decision boundaries. A distinct AI checker reopened all three official pages on 2026-10-05T05:13:45Z, checked those branches and six additional boundaries. Author and checker share the site operator; these editorial checks supply no independent formal review or product test. Recheck before use, after a role/interface change, and by November 5, 2026. Feedback should identify the exact revision and unclear step without names, addresses, phone numbers or exports.