A new phone can make old information look deceptively easy to move. Some items return after signing into an account; others depend on an application-specific transfer, a local export, or access to the old device. The safest time to discover those differences is before the old phone is erased, traded in, or becomes unavailable.
This guide proposes a migration checklist for personal Android and iOS devices. It is organized around the information and access you need, rather than assuming one transfer button covers everything. Use the Android backup page and iOS backup page for platform-specific starting points, then test the tasks that matter on the replacement device.
Inventory by information, not by app icon
List the things you would notice missing: photographs, contacts, messages, notes, local downloads, recordings, authenticator access, and application projects. Put each item beside the account or device that currently holds it. A screen full of familiar app icons is not evidence that the data behind every icon has transferred.
Mark items stored only on the old phone. These deserve early attention because signing into an account elsewhere may not retrieve them. Look inside applications that create their own local files, and inspect downloads that are not part of your usual photo or document collection.
Keep work-managed information separate from personal material. Follow the organization's migration process for managed profiles, accounts, and restricted applications. Do not move organizational records into personal storage simply because that appears to be the easiest way to get them onto the new device.
Check the actual backup scope
Google's Android backup and restore guidance states that not all apps can back up or restore all settings and data. It also explains that restoring a backup from a higher Android version to a lower version is not supported. These limits make app-level verification important even when the device reports a completed backup.
Inspect the backup account, the latest completion information, and the selected categories on the phone you are moving from. Make sure the account belongs to you and remains accessible independently of the device. Record the result without copying passwords or recovery codes into an ordinary checklist.
For an iPhone or iPad, review the supported iCloud and computer backup methods described on the linked iOS topic page. Treat synchronized cloud content and device backup coverage as separate questions. Check the method you actually use instead of assuming that another person's setup describes your own.
Protect sign-in access before moving data
Write down which accounts require more than a password. Consider authentication apps, hardware keys, trusted-device prompts, and recovery contacts or codes. Use each service's supported migration or recovery procedure while the old phone is still available. Do not disable protections broadly to make the move more convenient.
Store recovery material through a secure route that does not depend exclusively on the old device. A screenshot of recovery codes saved only on that same phone will not help if it is lost. Avoid sending codes to yourself through an unprotected message or placing them in the general photo collection.
Test access to an important account on another authorized device before the migration. Keep the test controlled and do not sign out of every working session at once. The goal is to verify an alternate route, not to create an account lockout while preparing for a hardware change.
Give photos and videos their own check
Inspect where the originals live and whether the full files are available. A preview on the phone may not be the same as a locally stored original. Choose representative items from different years and formats, including a long video or an edited image if those matter to your collection.
When creating an independent copy, verify more than a thumbnail count. Open a few full-size images, play videos, and check dates or album context where relevant to your goal. Note any material that requires a separate export from an editing application or a shared collection.
Do not delete the old library as a test. Deletion in a synchronized service may affect other devices too. The cloud sync versus backup guide explains why a second screen showing the same photographs should not automatically be counted as an independent recovery copy.
Export contacts with their important fields
Check which accounts supply the address book. One visible list may combine personal contacts, a work directory, and records stored on the device. Preserve only the records you are authorized to export, and note their origin so you do not later merge incompatible sources without noticing.
Use the supported export route for the relevant contact service. Inspect several complex records, including multiple phone numbers, organization names, notes, and non-English characters. Keep the original export unchanged, and test imports in a separate address book or controlled profile when possible.
After moving, compare a representative sample rather than relying solely on the total count. Duplicates can inflate a count while missing fields remain unnoticed. The contacts backup checklist provides a more detailed review for people whose address book is a critical working resource.
Handle application-specific transfers deliberately
Prioritize the applications that contain unique information or enable important access. Read their supported transfer instructions before changing devices. Some may require the old device, a specific account, a compatible destination, or an export created from inside the application. Treat each requirement as a dependency in your migration plan.
Avoid random third-party transfer tools that ask for broad access without a clear need. Evaluate what data a tool can read and where it sends that data. Prefer documented routes from the platform or application provider, and test a non-sensitive sample before entrusting a large private archive to an unfamiliar workflow.
Keep a record of which applications have passed a functional check. Opening an app is only the first step. Retrieve an older note, open an attachment, inspect an archived conversation, or load a saved project. Choose a test that demonstrates the data you intended to preserve is actually usable.
Separate cross-platform moves from ordinary restores
Moving between operating systems is not the same task as restoring onto a replacement running the same platform. Build a destination-specific checklist and identify the formats or supported transfer features available for each category. Do not assume a whole-device backup can be imported wherever an application with a similar name exists.
Expect to make explicit decisions about material that does not transfer cleanly. A readable local archive may be sufficient for old reference material even when it cannot appear in the new application's normal interface. Document that choice rather than quietly treating the material as restored.
Verify the new phone before retiring the old one
Create a short acceptance list based on daily use. Can you sign into essential accounts, find key contacts, open important photos, read required records, and access the documents used for work or travel? Test on the new phone itself instead of inferring success from a transfer progress message.
Allow time to notice less frequently used information while keeping the old device protected. Do not leave it unlocked or share it casually simply because it is no longer your primary phone. Retain access only as long as needed under your personal or organizational policy.
Before erasing or handing over the old phone, confirm the remaining account and device-removal steps through the platform's supported procedure. A trade-in deadline should not replace the acceptance check. Keep the final backup and its access route available until you are confident that the chosen recovery goals have been met.
Conclusion: move the information and the access
A successful phone migration preserves both the content you value and your ability to reach the accounts that control it. Inventory the data, verify backup coverage, handle application-specific transfers, and test the replacement before retiring the original. Start with the irreplaceable items and record the remaining gaps. A deliberate handover is easier to trust than a new device that merely looks familiar.
