Moving to a new Android phone is safest when you treat it as a verification process rather than a single copy operation. This Android transfer and reset manual explains how to back up the old phone, migrate apps and personal data, move authenticator accounts and passkeys, handle an eSIM, verify messages and photos, and erase the old device only after the replacement is ready.
Overview
Android migration usually combines several methods: a Google account backup, a direct cable or wireless transfer, and manual exports from individual apps. No single method should be assumed to move everything. App data, banking credentials, authenticator tokens, downloaded files, local messages, eSIM service, and manufacturer-specific settings may follow different paths.
Keep both phones charged and connected to a reliable Wi-Fi network. Do not factory-reset the old phone until you can unlock the new one and confirm the information that matters most. If the old phone is damaged or unavailable, restore what is present in the Google backup and use each service's account-recovery process for anything that was not backed up.
Pre-transfer checklist
- Install pending system updates on both phones if practical, and note the Android versions and manufacturer models.
- Confirm the Google account used on the old phone and make sure you can sign in to it.
- Charge both phones, keep the original cable or a known-good data cable nearby, and have the required screen locks available.
- Back up photos, contacts, calendars, and important files. Check the backup status instead of assuming it completed.
- List security-sensitive apps: authenticator apps, password managers, banking apps, passkey providers, work profiles, and multi-factor authentication services.
- Record eSIM and mobile-service details before moving or erasing the old phone. The exact procedure depends on the carrier and device.
For a related hardware check, see the USB-C Troubleshooting Manual if a cable charges but does not support data transfer.
What normally transfers?
| Data or setting | Typical transfer path | What to verify |
|---|---|---|
| Google contacts and calendar | Google account sync or backup | Open Contacts and Calendar on the new phone and check recent entries. |
| Installed apps | Google restore or direct phone-to-phone setup | Some apps may need to be downloaded again or signed in manually. |
| Photos and videos | Cloud photo backup, cable, wireless transfer, or manual copy | Check recent, favorite, and locally stored media. |
| SMS and call history | Supported backup or direct migration | Confirm recent conversations and important attachments. |
| Authenticator codes and passkeys | App-specific transfer, cloud sync, export, or recovery method | Test sign-in before removing the old device. |
| Downloads and files | Manual copy or cloud storage | Inspect the old phone's Downloads and document folders. |
| eSIM | Carrier-supported transfer or new activation | Place a test call and confirm mobile data before erasing the old phone. |
How to estimate
Use a simple readiness estimate instead of guessing whether the move is complete. Divide your checklist into five groups: account access, personal data, apps, security credentials, and mobile service. Mark each group verified, needs action, or not applicable. The old phone is ready to reset only when every required group is verified.
Step 1: Run a Google backup
- On the old phone, open Settings and search for Backup. Menu names vary by manufacturer and Android version.
- Review the Google backup account and the categories included.
- Start or request a backup, then leave the phone connected to power and Wi-Fi long enough for it to finish.
- Open Google Photos or the relevant cloud service and confirm that recent photos are present online.
Step 2: Use cable or wireless migration
During setup of the new phone, choose the option to copy apps and data from another device. A cable is often the more predictable choice, provided it supports data. Wireless transfer can be convenient, but keep the phones close, unlocked when requested, and connected to power. Follow the prompts on both screens and do not interrupt the process because the progress display appears slow.
Step 3: Handle security credentials separately
Open the authenticator app on the old phone and look for an account-transfer, export, backup, or cloud-sync option. Complete the service's instructions, then test a code on the new phone. For passkeys, check the password manager or account provider that stores them and confirm that the new phone is recognized. Save recovery codes in a secure location before removing the old device. Never assume that reinstalling an authenticator app restores its accounts.
Step 4: Move the eSIM carefully
Keep the old phone active until the new phone has a working mobile connection. In the new phone's mobile-network settings, look for an eSIM transfer or add-SIM option. If that option is unavailable, use the carrier's activation procedure. Menu paths and transfer support differ by carrier, model, and region. Test calls, text messages, and mobile data before proceeding.
Inputs and assumptions
Your migration outcome depends on inputs that are easy to overlook:
- Old-phone access: A working screen lock and operating phone allow more direct transfer options.
- Backup scope: A backup may cover selected device data without including every app's private database or downloaded file.
- Manufacturer differences: Samsung, Google, Motorola, OnePlus, and other brands may provide different transfer tools and menu labels.
- App design: Some apps restore from an online account; others require an export, a fresh sign-in, or device reauthorization.
- Security controls: Authenticator tokens, passkeys, work profiles, and banking access should be tested individually.
- Network service: A SIM or eSIM transfer can succeed separately from the data migration, so verify it as its own task.
These assumptions also explain why a transfer can appear successful while still missing a few important items. Search the old phone manually for files, recordings, notes, downloads, and media stored outside the main photo library.
Worked examples
Example: both phones work
Back up the old phone, start setup on the new phone, and use a data cable if both devices support it. Select the data categories offered, allow the process to finish, and sign in to priority apps. Verify contacts, recent photos, messages, downloads, authenticator codes, passkeys, and mobile service. Keep the old phone untouched for a short verification period, then remove accounts and erase it.
Example: the old phone is damaged but unlockable
Use Google backup first, then connect the phone to a computer or new device if its screen and storage remain accessible. Prioritize security credentials and irreplaceable files. If an app cannot export its data, use its account recovery or support process rather than repeatedly guessing passwords.
Example: the new phone is missing data
Do not reset the old phone. Compare the old phone's Contacts, Photos, Messages, Downloads, and app list with the new phone. Re-run the supported transfer, manually copy missing files, or sign in to the relevant cloud account. For work data, follow the organization's device-management instructions before removing the old profile.
Factory-reset checklist
- Confirm the new phone can unlock, make calls, send texts, and use mobile data.
- Verify recent photos, contacts, messages, files, authenticator access, passkeys, and essential apps.
- Remove the old phone from account and device lists where required, especially for security-sensitive services.
- Sign out of accounts and remove the eSIM or physical SIM according to your service instructions.
- Open Settings and search for Factory reset or Erase all data. Read the warning carefully and follow the device's reset sequence.
- After the reset, stop at the initial setup screen if the phone will be sold, recycled, or handed to another person.
A factory reset removes local content, but it does not replace account recovery planning. If the old phone is already inaccessible, secure your accounts from another device by changing passwords, reviewing signed-in devices, and replacing lost authentication methods.
When to recalculate
Revisit this checklist whenever you change Android versions, switch manufacturers, replace a SIM or eSIM, change your authenticator or password manager, or restore a phone after loss or damage. Also repeat it before selling a device, after a failed migration, and whenever a critical app changes its sign-in or backup process.
Before each reset, repeat the five-group check: account access, personal data, apps, security credentials, and mobile service. If any item is marked needs action, postpone the reset and resolve it first. This small pause is the most reliable way to avoid turning a routine Android transfer into a recovery problem.
