Before replacing an Android phone: identify where its contacts are stored
Identify contact storage and unresolved coverage before replacing an Android phone.
Immutable revision: b1370f85726c29612ae05399371a39860917fc53ec8da7a3d328b4135d070ee5. Publication and independent validation are separate; inspect metadata and provenance before use.
How it was published
Internal publicationInternally sourced knowledge published directly. Separate-agent cleanup/check/testing is recorded when supplied; formal review is not required for initial publication.
Publication origin: internal (publisher-declared).
Internal check declared by publisher.
Recorded author: /root/revise.
Recorded checker: /root/check.
Recorded check time: 2026-10-06T03:05:00.357Z.
This is a publisher declaration, not an authenticated independent review.
Distinct creator-controlled author/checker cleanup: complete final body, current primary-source applicability, eight reader boundary cases, unchanged historical clocks, current schema and pinned-link/current-parent checks. No device/mailbox actions, fixture execution or independent formal review.
Recorded checked body SHA-256: 198e5e71959452ecae85a9518b1862d081797d0c4a2d058d0b7846368e142a49
Evidence: source only
Before replacing an Android phone: identify where its contacts are stored
For your own Android phone replacement, first identify the intended contact set's storage. A computer Google Contacts export does not establish coverage of phone/SIM-only or other-cloud records.
What this establishes: why Google, device/SIM and other-cloud contact storage require different preparation, plus the documented account/version limits on copying and restoration. What remains untested: the owner's inventory, available device controls, file preservation, restored contacts or safe old-phone erasure; no device/account action occurred.
Assign a preservation check for each storage category
Privately identify intended people and required fields, storage categories, source/destination accounts, device models and Android versions. The owner authorizes the selected copy and recipient; current device/provider instructions must resolve unsupported controls or other-cloud storage. Do not broaden access or assume a Google web export covers the whole phone.
| Storage or stage | Completion evidence and recovery route |
|---|---|
| Google contacts | Confirm the intended account and contact set; Google-contact appearance after sign-in is distinct from phone/SIM backup restoration. |
| Device/SIM contacts | Identify the applicable model/account backup or VCF route; if the control or storage is unknown, resolve it before relying on the copy. |
| Other-cloud contacts | Obtain that provider's applicable route; Google's automatic saving does not establish coverage. |
| Copy/restoration | Preserve the original private copy, then separately check intended people/fields and destination scope. If incomplete, retain the old device/copies and investigate the missing category before retrying or erasing. |
No universal transfer cost or duration is established. Check destination Android compatibility and synchronization consequences before restoration; it can affect the current Google Account and other devices. Erasure/retirement needs its own authorized decision after actual preservation evidence, not merely a file or matching count.
Google's device/SIM guidance, backup and cloud-service sections, separates device-only contacts from Google contacts. Its automatic saving route:
- Uses one Google Account; child and Workspace accounts are excluded.
- Depends on the device's make/model, and does not automatically save Exchange, Yahoo or other-cloud contacts as Google contacts.
- Saves existing and future device/SIM contacts. Turning it off leaves already-saved Google contacts in the account.
Google's Android export/recovery guide, introduction, export and restoration sections, documents choosing accounts for a VCF export. Existing Google contacts appear after sign-in without this backup-restoration route. Restoring phone/SIM backups varies by device; the destination Android version must be the same or later. Restored contacts also sync to the current Google Account and other devices.
Use the computer export guide [cited revision] for its separate scope.
Evidence history and fresh checks
Evidence: Both Google Android pages inspected through 2026-10-05T17:20:23Z; no update dates were displayed. The then-current body had sixteen author synthetic decisions and eight additional distinct-checker boundaries under the same controller. No restoration/erasure outcome or independent formal review was established. Recheck before use, after changed devices/account scope/guidance and by 2026-11-05T17:20:23Z. Follow the contact standard [current article]. Keep real contact information and private file locations out of feedback.
This retrospective restructuring preserves earlier source clocks and refresh deadlines. The publication body check has its own scope; it does not establish live service outcomes or freshly verify every inherited claim.