Move and Clean Up Android Contacts Without Losing Ownership

The Contacts app is a view, not necessarily the address book. One screen can combine records owned by a personal Google Account, work Google Account, Microsoft Exchange, the phone itself, a SIM and other applications.

If you start by pressing “Merge all”, you may clean the view while leaving the ownership problem untouched—or move business contacts into a personal account. Start with an inventory.

Define the intended outcome

Record:

• current device and accountable person/organisation;
• every signed-in account that supplies contacts;
• device/SIM-only and third-party sources;
• intended destination owner/account;
• whether this is a copy, ownership transfer or device replacement;
• contacts that must remain separated;
• retention/privacy requirements; and
• what will happen to the old device/account after acceptance.

A work contact is not automatically owned by the employer, and a record displayed on a work phone is not automatically stored in the work account. Resolve that with the owner—not by guessing from the name.

Inventory each contact store

In the Contacts app, use the account/filter controls to view one source at a time. Menu wording varies, so record what the app actually shows.

For each source, capture a safe summary:

Do not publish screenshots or counts tied to real people. Contact exports contain personal data and should be stored/transferred accordingly.

Create recovery copies before changing ownership

Google Contacts on Android can export contacts from selected accounts to a VCF file. Export each relevant source separately where permitted, use names that identify source and time without exposing them publicly, and copy the files to an approved protected location.

Verify:

• file exists and has non-zero size;
• the expected number of contacts can be read by an authorised viewer or controlled import preview;
• representative names, multiple numbers/emails, notes, organisations and addresses are present;
• photos/labels/custom fields needed by the owner survive the chosen route; and
• the source account remains unchanged.

A VCF may not represent every vendor-specific field. Preserve the provider’s native backup/sync path as well where required.

Choose one destination owner deliberately

Google documents that device and SIM contacts can be saved automatically as Google contacts, but only to one selected Google Account; contacts already managed by another cloud service are not automatically absorbed. Confirm the displayed destination account before enabling that setting.

For a one-off move, Google Contacts can move a contact from another account into a Google Account. Moving deletes it from the original account. Use that only when transfer of ownership is intended and the source export is safe.

If the requirement is a copy, use an approved export/import route and retain the source until acceptance. Be aware that future edits then diverge unless one account becomes authoritative.

For work or school accounts, administrative policy may restrict export, sharing or retention. Use the organisation’s approved method rather than routing records through a personal account.

Move in a controlled batch

1. Pause casual contact editing on the old/new devices.
2. Confirm sync status and the exact source and destination account.
3. Export the source and protect the recovery copy.
4. Move or import a small representative batch.
5. Check it in the destination’s web/native address book—not only the combined phone view.
6. Verify important fields, labels and search/dial behaviour.
7. Complete the remaining approved batch.
8. Allow sync to settle and capture source/destination counts.

Do not reset or hand over the old phone because some names appear on the new one. A combined view can hide missing fields or contacts still sourced from the old account.

Reconcile ownership and completeness

Counts alone are not enough, but unexplained count differences matter. Reconcile:

• records exported from each source;
• records selected to move/copy/exclude;
• import failures/skipped rows;
• destination count after sync;
• representative contacts with multiple fields;
• labels/groups and favourites where required;
• contacts searchable from the destination account’s web interface;
• contacts visible when the old account is filtered out or temporarily removed from the test view; and
• new-contact default save account.

Document intentional exclusions and duplicates. A person with two roles may correctly have two records; two people may share a name, household number or generic mailbox.

Clean duplicates only after migration reconciles

Google can suggest duplicate contacts and merge selected records within one Google Account. It cannot merge contacts stored in different Google Accounts. If two entries come from different owners, decide ownership first.

Review suggestions individually when the address book matters. Compare:

• full name and organisation;
• every phone/email and label;
• notes, dates, postal addresses and photos;
• account/source; and
• whether the records really describe one person.

After each meaningful batch, check destination count and representative records. Do not delete the exported recovery files until the owner’s retention period ends.

Understand the recovery window

Current Google Contacts documentation says deleted contacts normally remain in Trash for 30 days and account-wide changes can be undone to a point within the previous 30 days. Permanently deleted records fall outside that recovery path, and an account-wide rollback can also remove contacts added after the chosen restore point.

Treat those features as short recovery options, not the migration backup. Export the current state before a rollback so newer legitimate additions can be reconciled afterward.

Hand back or retire the old device safely

Only after owner acceptance:

• confirm destination ownership and sync on an independent session/device;
• retain approved recovery export and migration record;
• confirm required applications use the correct contact source;
• remove personal/work accounts according to handback policy;
• verify device-management and factory-reset ownership requirements; and
• perform the approved reset/retirement process.

The finish line is not “the names show up”. It is that the intended account owns a complete, usable and recoverable address book, other owners’ records remain separate, and the old device can be retired without becoming the last surviving copy.