A phone transfer is complete when the accounts and data you need work on the new device—not when a progress bar reaches 100%. Start with an inventory and keep the old phone intact until you have checked the result.
Make a short account and data inventory
List your main email account, password manager, authenticator, messaging apps, bank apps, photos, local documents, notes and work accounts. Beside each one, record whether it uses cloud sync, an app-specific backup or a direct transfer. Do not put passwords or recovery codes in an ordinary shared checklist.
Open a few important files and check the newest backup date. A thumbnail on the old phone does not prove that an independent copy exists. A device backup also does not necessarily contain everything stored inside every app.
Move authentication deliberately
Google Authenticator can sync codes to a Google Account; codes used without an account require manual transfer. Confirm which mode you use. Keep export QR codes private because they carry the information needed to generate codes.
Microsoft Authenticator’s restore process works between the same device type. Work or school account names can return without their usable credentials, so those accounts need registration again. A restored list is not sufficient proof that sign-in works.
Test a real sign-in on the new device while you still have a working recovery method. For a managed work account, follow the organisation’s enrolment process instead of removing its old authentication method first.
Use the right device-transfer route
- Android to Android: follow the setup copy process. Google says cable and wireless methods support the same data; manufacturer-specific tools and app support still matter.
- iPhone to iPhone: use Apple’s Quick Start or the appropriate backup restore.
- Between platforms: use the supported Android Switch or Apple transfer route for your devices. Do not assume every app’s history crosses with the app itself.
For WhatsApp, check its platform-specific migration instructions before beginning. A Google backup and an iCloud backup are not interchangeable restore files. Keep the chat migration and its later backup as separate checks.
Restore mobile and payment access
Follow the carrier’s eSIM transfer or reissue process if needed; do not delete the only working profile first. Confirm incoming calls, outgoing calls and ordinary SMS on the new phone.
NPCI describes mobile verification when changing handset. Re-registration does not automatically mean every user must reset a UPI PIN. For example, Google Pay supports an existing bank-account UPI PIN. Follow the bank/app’s prompts and any applicable waiting limits; never disclose the PIN to support.
Verify the things a transfer summary misses
- Open recent and older photos, documents and chat attachments.
- Check your password manager and important account sign-ins.
- Confirm contacts, calendar events, alarms and any routines you depend on.
- Check offline media and locally stored notes or game progress individually.
- Verify connected accessories and device-finding settings on the new phone.
Keep the old phone until these checks pass and any missing data is resolved. There is no magic two-week period that makes an incomplete transfer safe.
Erase only after verification
Apple’s resale checklist covers backup, transfer, sign-out, watch unpairing and erasure. It warns that manually deleting synced items while signed into iCloud can remove them from other devices too. Use the documented erase flow rather than manually deleting your photo library.
For Android, follow the exact manufacturer’s resale/reset instructions, including account and device-protection steps. Remove physical SIM and removable storage where present. Check the reset result before handing the phone to someone else. Keep purchase and device-identification records privately.
Reviewed on 27 October 2026. Corrected authentication, UPI and transfer assumptions and replaced arbitrary waiting rules with verification steps.
