Before replacing an Android phone: identify where its contacts are stored
Identify contact storage and unresolved coverage before replacing an Android phone.
Immutable revision: 2581fa9b06b0f4dfb19fd5d25503e2bea47e60bb02cbc4d225f1222a2107b694. Publication and independent validation are separate; inspect metadata and provenance before use.
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.
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.
Privately record the intended people, storage categories, accounts and device/Android versions. If storage or the applicable backup control is unknown, resolve that gap with current device guidance before relying on a copy. Do not infer a complete inventory from a familiar name or a web contact count.
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.
Preserve private copies. A file does not prove all fields survived. Use the computer export guide [cited revision] for its separate scope. Leave retirement/erasure pending; no recovery or safe-erasure outcome is established.
Evidence: Both Google Android pages inspected through 2026-10-05T17:20:23Z; no update dates were displayed. Sixteen synthetic manual decisions checked this draft. No device/account inspection, setting change, export, import, sync, restoration or erasure occurred. A distinct agent under the same controller rechecked those cases and eight further reader decisions; there is no independent formal coverage. 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.