How to Back Up Your Phone Before Replacing or Resetting It: iPhone, Android, Photos, Messages, and Authenticator Codes

Quick answer: Before replacing, resetting, selling, or sending a phone for repair, do more than press “Back Up Now.” First confirm which account the phone is using, create a current device backup, verify photos and videos separately, export or sync contacts that live only on the device or SIM, review messaging apps, transfer authenticator codes and recovery methods, save local Downloads and hidden folders, and record anything that may not restore automatically. Then set up the new phone and verify critical data before erasing the old one. On iPhone, you can use iCloud, Quick Start, or an encrypted computer backup. On Android, Google backup and direct cable or wireless transfer can move much of the device, but Google explicitly notes that not every app backs up all of its data and some local files do not transfer automatically.

Moving to a new phone is easiest when you treat backup and transfer as separate checks rather than assuming one automatic process covers everything. Image: CeeJay95, Wikimedia Commons, CC BY-SA 4.0.

Replacing a phone feels simple because modern setup screens promise to copy your data automatically. In many cases they do an impressive job. Apple Quick Start can move settings and data from one iPhone to another, while Android setup can copy apps, photos, messages, call history, contacts, and many settings by cable or Wi-Fi. Cloud backups can restore a device even when the old phone is unavailable.

The danger is assuming that “transfer complete” means “everything important exists somewhere else.” It may not. A cloud backup can exclude data that is already synced separately. A direct Android transfer can skip Downloads, hidden media folders, unsupported apps, non-Google accounts, or data held by apps that do not participate in Android backup. Authenticator applications can require their own transfer or account sync. Messaging apps may have separate backup systems. Work profiles can have administrator restrictions. Local voice recordings, exported documents, offline maps, secure folders, crypto wallets, eSIMs, and some password or passkey systems can require additional attention.

This guide is built around one goal: you should be able to erase the old phone without discovering the next day that something irreplaceable lived only on that device. The process is deliberately redundant. It creates multiple checkpoints, verifies the backup instead of trusting an icon, and postpones deletion until the new phone proves that the important information is actually there.

1. Decide Why You Are Backing Up the Phone

The reason changes the safest workflow.

• Replacing the phone: You can usually use direct device-to-device transfer plus a cloud or computer backup as protection.
• Factory resetting the same phone: You need a backup that can be restored after the erase, because direct transfer to another phone may not be available.
• Selling or trading in the phone: You must verify the replacement first, then sign out, remove activation locks where required, and erase the old phone according to the manufacturer’s procedure.
• Sending the phone for repair: The repair center may erase the device, so create a verified backup and remove or protect sensitive data according to the repair provider’s instructions.
• Emergency backup before suspected failure: Prioritize irreplaceable data such as photos, contacts, messages, authenticator access, documents, and recordings instead of spending hours perfecting settings.

If the phone is already unstable, overheating, restarting, or has a damaged display, work from most valuable to least valuable data. Do not spend your last functioning hour reorganizing the home screen while family photos remain only on the device.

2. Write Down the Accounts That Control the Restore

Before touching backup settings, identify the accounts you will need after reset:

• Apple Account or Google Account;
• email accounts;
• password-manager account;
• messaging accounts;
• work or school accounts;
• banking or payment accounts;
• social accounts;
• cloud-storage accounts;
• carrier account;
• two-factor authentication systems.

Make sure you know the passwords or have a reliable password manager and recovery method. A perfect phone backup is not useful if you cannot sign into the account that holds it.

Important: Do not store recovery codes only in a note on the phone you are about to erase. Keep critical recovery information in a secure location that remains available when the phone is offline.

3. Confirm Which Cloud Account Is Actually Receiving the Backup

People often own multiple Apple or Google accounts. The phone may be backing up to an older address you rarely use.

On Android, Google’s current backup guidance tells users to review the selected backup account under the device’s Google backup settings. On iPhone, verify the Apple Account shown in Settings and the iCloud storage associated with that account.

Write down the exact account address. When you set up the new device, use the same account unless you intentionally plan to migrate.

4. Update the Old Phone Before a Major Transfer When Practical

A current operating system can reduce compatibility problems during device-to-device transfer. Google’s current Android troubleshooting guidance recommends installing available updates when transfer problems occur. Apple likewise recommends current software for many transfer workflows.

However, do not install a major update on a phone that is already unstable unless you understand the risk. If the phone appears close to failure, back up critical data first, then update if needed.

5. Charge Both Devices and Use Reliable Power

Device transfer can take minutes or several hours. Google says Android transfers can range from a few minutes to more than an hour, depending on the amount of data. Apple similarly notes that Quick Start times vary with network conditions and data volume.

Plug both phones into power. If a cable transfer uses the only charging port on one device, start with a full battery or use a supported charging arrangement.

Avoid starting the migration just before leaving home, boarding a flight, or going to sleep if you need the old phone for calls or verification prompts.

6. Take a Current Cloud Backup Before Direct Transfer

Direct transfer and cloud backup solve different failure modes. If the cable fails, the wireless session breaks, or the new phone develops a problem, a current cloud backup gives you another path.

On iPhone: Apple’s current support instructions let you back up with iCloud or with a Mac/PC. In Settings, open your Apple Account, choose iCloud, then iCloud Backup and initiate a backup. Wait until the interface shows a current successful backup date.

On Android: Google’s current Android Help directs users to Settings > Google services > Backup, where you can review the backup account, backup details, and start “Back up now.” Google notes that a Google One device backup can take up to 24 hours to finish completely.

Do not erase the device immediately after pressing the button. Wait until the status confirms completion.

7. Understand the Difference Between Sync and Backup

Sync keeps a live set of data aligned across devices. Backup creates a restorable copy of data that may not already be synchronized.

Apple explains this explicitly for iCloud: data such as iCloud Photos, iCloud Drive, and Notes can sync continuously, while iCloud Backup stores other device information that is not already synced. That means some important data may not be inside the backup file because it is expected to return through synchronization after you sign in.

This distinction matters when troubleshooting. If photos are missing after an iCloud restore, the problem may be with iCloud Photos synchronization rather than the backup itself.

8. Verify Photos and Videos Independently

Photos and videos are often the most emotionally valuable data on a phone, so verify them separately.

On Android with Google Photos: Open Google Photos, confirm the correct Google Account, and check the backup status. Google’s current help page says the app should show “Backup complete” when all selected items are uploaded. Also review “Back up device folders.” Screenshots, downloaded images, messaging-app folders, and camera folders created by other apps may not all be selected automatically.

On iPhone: If you use iCloud Photos, confirm that Photos synchronization is enabled and allow enough time for recent media to upload. If you do not use iCloud Photos, the media may instead rely on iCloud Backup or a computer backup depending on your setup.

For irreplaceable media, consider making a second copy to a computer or external drive. A second copy protects against account mistakes and accidental deletions that sync across devices.

Cloud photo systems can synchronize media independently of the main device backup. Verify their status separately. Screenshot from Google Photos, Wikimedia Commons, public-domain eligibility noted on the file page.

9. Check Contacts by Source, Not Just Total Count

Contacts can live in multiple places:

• Google Account;
• iCloud;
• Microsoft or Exchange account;
• local device storage;
• SIM card;
• work profile;
• another cloud provider.

A phone that shows 900 contacts may actually have 700 in Google and 200 stored only on the device. Open the contacts app’s account or list view and determine where they live.

Move important local contacts into the cloud account you intend to use, or export them to a standard contact file if the app supports it. Keep that export somewhere other than the phone.

10. Confirm Calendar Data Is Synced to the Right Account

Calendar events can also be local or account-based.

Check each calendar’s account source. If an important calendar is “On My iPhone,” “Phone,” or otherwise local, export or move events if the platform permits. Business calendars may belong to Microsoft 365, Google Workspace, or another provider and will reappear only after that account is added again.

11. Treat Messaging Apps as Separate Backup Systems

SMS, MMS, iMessage, RCS, WhatsApp, Signal, Telegram, and other apps do not all use the same restore mechanism.

Google states that Android device backup can include SMS/MMS and, with supported Google apps, RCS messages. Direct Android setup can also copy text messages and multimedia. But third-party messaging apps may maintain their own cloud backup or transfer system.

Before erasing the old phone:

1. Open every messaging app that contains irreplaceable history.
2. Find its backup or transfer settings.
3. Confirm the date of the latest backup.
4. Check whether the restore requires the same phone number, account, PIN, encryption password, or recovery key.
5. Keep the old phone until the app successfully opens on the new phone.

Do not assume a device backup includes an app’s encrypted conversation database.

12. Back Up Authenticator Codes Before Anything Else Can Lock You Out

Two-factor authentication is one of the most important migration steps because losing the authenticator can prevent you from signing into the accounts needed to restore everything else.

Google Authenticator currently supports account synchronization when you sign into a Google Account inside the app. Google also supports manual transfer: the old device can export selected accounts as QR codes, which the new device imports.

If you use another authenticator app, read its own migration instructions. Some synchronize with an account; some require manual export; some intentionally keep secrets only on the device.

For critical accounts, also confirm alternate recovery methods such as:

• backup codes;
• hardware security key;
• second trusted device;
• recovery email;
• recovery phone number;
• passkey on another device.

Verification test: After the new phone has the authenticator, sign into one low-risk account using a generated code before erasing the old phone.

13. Check Password Managers and Passkeys

Password managers usually synchronize through their own account, but you still need to verify that the vault is current and that you know the master password or recovery method.

Open the password manager on another trusted device or its web interface if available. Confirm that a recent password saved on the phone appears there.

For passkeys, understand where each one is stored. Some passkeys sync through the Apple or Google credential ecosystem; others live in a third-party password manager or hardware key. Do not assume every passkey can be recovered from the general phone backup.

14. Review Banking and Payment Apps Before the Move

Banking apps often deliberately require re-registration on a new device. You may need an SMS code, card number, customer number, biometric setup, or approval from the old device.

Before erasing the old phone:

• confirm your login credentials;
• make sure the phone number on file is current;
• check whether the bank uses the old device for authorization;
• record support contact information;
• complete re-enrollment on the new phone if permitted.

Never record PINs or banking passwords in an unsecured migration checklist.

15. Save Files From Downloads and Local Folders

This is a major Android transfer gap. Google’s current Android transfer documentation explicitly says that some Downloads, hidden-folder media, apps from outside Google Play, and certain app data do not copy automatically during standard setup.

Open the Files app and inspect:

• Downloads;
• Documents;
• Audio;
• Movies;
• DCIM;
• Pictures;
• screen recordings;
• voice recorder folders;
• messaging export folders;
• PDFs;
• scanned documents;
• offline work files.

Copy important files to cloud storage or a computer.

16. Check Secure, Locked, or Hidden Folders

Private photo folders, secure containers, manufacturer-specific “Secure Folder” systems, hidden albums, and app vaults often use separate encryption and transfer rules.

Open each one and read its export or backup instructions. Do not assume encrypted local data will be copied by a normal file transfer.

If the folder contains sensitive documents, use the vendor’s secure migration method rather than moving them into an unencrypted temporary location unless you understand the risk.

17. Back Up Voice Recordings and Audio Notes

Voice recorder applications may store files locally. Recordings used for work, family history, interviews, lectures, or legal records can be irreplaceable.

Export important recordings to a computer or cloud drive and verify that the files play. Do not rely solely on the app icon appearing on the new phone; reinstalling an app does not guarantee that its local recordings return.

18. Export Important Notes That Are Not Cloud-Synced

Notes can live in iCloud, Google Keep, Microsoft OneNote, Samsung Notes, a local device database, or another service.

Test from another device or the provider’s web interface. If a note exists only locally, export or move it.

This is especially important for scanned IDs, handwritten notes, project drafts, and attachment-heavy notes.

19. Check Work Profiles and Employer-Managed Data

Google notes that backup may be restricted on devices with work profiles, work-only configurations, or company ownership.

Do not try to bypass organization policies. Ask the employer how the work account should be moved. Many business apps intentionally do not allow personal backups.

Keep business data separate from personal backup exports so confidential company information does not end up in an unauthorized personal cloud account.

20. Decide Whether You Need an iPhone Computer Backup

Apple allows iPhone backups to a Mac or PC in addition to iCloud.

A computer backup can be useful when:

• internet upload is slow;
• iCloud storage is limited;
• you want a local fallback;
• you prefer to control where the backup file is stored.

If you use a computer backup, consider encryption. Apple’s current guidance says an encrypted local backup can include saved passwords, Wi-Fi settings, website history, Health data, and call history that an unencrypted local backup does not include. Apple also warns that you need the encryption password to use the backup.

21. Protect the Encrypted Backup Password

Do not create an encrypted local iPhone backup and then store its password only in a note on the phone.

Save the password in a trusted password manager or another secure location. Test that you can locate it before erasing the phone.

An encrypted backup that cannot be unlocked is not a usable recovery plan.

22. Use Temporary iCloud Storage When Eligible

Apple offers temporary iCloud storage for eligible users who purchase a new iPhone or iPad and do not have enough normal iCloud capacity for the transfer backup.

Apple’s current support material says users can find this under Settings > General > Transfer or Reset > Prepare for New Device. The temporary backup is time-limited, so follow the dates shown by Apple and do not erase the old device before the restore succeeds.

23. Choose Between iPhone Quick Start, iCloud Restore, and Computer Restore

Quick Start direct transfer: Useful when both iPhones are available. Apple says to keep them near each other and connected to power until migration finishes.

Download from iCloud: Useful when you want the new phone usable while apps and cloud content continue downloading in the background.

Computer restore: Useful when you have a current Finder, Apple Devices, or iTunes backup.

Whichever method you choose, do not interpret the first usable home screen as completion. Cloud media and apps may still be downloading.

24. Choose Cable or Wireless Transfer on Android

Google currently supports both cable and wireless transfer during Android setup. Its help documentation says both methods can move similar categories of data, with cable commonly recommended when available.

Before transfer:

• charge both phones;
• check that the new phone has enough storage;
• connect both to Wi-Fi or the required network;
• know the old phone’s PIN;
• use a cable that supports data, not only charging.

If the cable fails, try another known data cable or use wireless transfer.

25. Read Android’s “What Won’t Copy” List Before You Start

Google’s current Android documentation is unusually helpful because it explicitly lists categories that may not copy in the standard process. These can include Downloads, hidden media folders, apps outside Google Play, app data from unsupported apps, non-Google accounts and their data, contacts and calendars synced to other services, ringtones, and some settings.

Create your own manual checklist around those exclusions. A transfer system is safest when you know its boundaries.

26. Plan Cross-Platform Moves Separately

Moving from iPhone to Android or Android to iPhone is not the same as replacing a phone with the same platform.

Google’s current iPhone-to-Android transfer guide shows that what transfers depends on the method and device generation. On supported newer Android devices, upgraded transfer can move more categories than older classic flows. Google also notes exclusions such as certain iCloud-only photos, paid apps, some purchases, Safari bookmarks, and Health data.

Before switching platforms, make a category-by-category plan rather than relying on one transfer wizard.

27. Check eSIM and Carrier Activation Before Erasing the Old Phone

Cellular service may transfer automatically, require carrier activation, or need a QR code or app. The process varies by carrier, country, phone, and platform.

Keep the old device until the new phone can:

• make a call;
• receive a call;
• send and receive SMS if your plan supports it;
• use mobile data;
• receive verification codes.

If the phone number is your account recovery method, losing carrier access can complicate the entire migration.

28. Do Not Trade In the Old Phone at the Start of Setup

Keep the old phone for at least long enough to verify the new one thoroughly. If the trade-in deadline permits, a day or two of overlap is safer than handing over the old phone as soon as the new one powers on.

The old phone can still provide authenticator codes, app approvals, locally stored files, and a reference for missing settings.

29. Verify the New Phone Category by Category

After setup, do not ask only, “Does it look right?” Use a checklist:

Category	Verification
Photos	Open several recent and older photos and videos
Contacts	Search for several known people, including recently added contacts
Messages	Open recent and older threads; verify attachments
Calendar	Check future and past events
Notes	Open notes with images or attachments
Authenticator	Use a code for a test sign-in
Password manager	Confirm recent vault changes are present
Files	Open saved PDFs, recordings, and Downloads
Banking	Complete secure re-enrollment if needed
Cellular	Test call, SMS, and mobile data

30. Confirm That Cloud Restoration Has Actually Finished

Some restore systems make the phone usable before every app and file is present.

Leave the new phone on reliable Wi-Fi and power. Watch for apps still downloading, cloud-photo synchronization, message history, or offline files that need to reappear.

If storage use is still climbing and download indicators are visible, the restore is not finished.

31. Compare Storage Usage Carefully

The new phone may use less or more storage than the old phone even when migration is successful.

Reasons include:

• cloud-optimized photos;
• cache files not restored;
• old downloads skipped;
• different app versions;
• offline media not downloaded yet;
• temporary installation files.

Use storage totals as a clue, not proof. Verify important categories directly.

32. Do Not Wipe the Old Phone Until Authentication Works

Before erasing, confirm you can sign into:

• primary email;
• Apple or Google Account;
• password manager;
• banking services;
• work account;
• messaging apps;
• social accounts that use 2FA.

The new phone should be able to stand on its own.

33. Keep a Manual Archive of Truly Irreplaceable Data

For the most valuable data, cloud backup plus device transfer may still not be enough.

Consider an independent archive for:

• family photos;
• voice recordings;
• scanned identity or legal documents;
• creative work;
• research notes;
• important exported chats;
• business records.

Store the archive on a computer or external drive and, for critical material, keep another copy in a different location or trusted cloud service.

34. Understand Why “Free Up Space” Can Change the Local Copy

Cloud-photo tools may offer to remove device copies after upload. That can be useful, but it changes what physically remains on the phone.

Before using any “free up space,” “optimize storage,” or similar feature during migration, confirm that uploads are complete and that you understand whether the original-resolution file remains available in the cloud.

Do not use cleanup tools to create storage space for a transfer until you know the backup is complete.

35. Handle Offline Music and Video Separately

Downloaded Spotify, Apple Music, YouTube, Netflix, podcast, audiobook, or map content may not transfer as files because licensing apps expect you to redownload it.

This is normal. What matters is whether the account, playlists, library, or subscriptions return. Plan time and Wi-Fi bandwidth for redownloads.

36. Check Offline Maps and Travel Documents

If you are traveling soon after switching phones, re-download:

• offline maps;
• airline boarding passes;
• hotel confirmations;
• rail tickets;
• translation packs;
• travel insurance documents.

These may not be part of the device backup even if the underlying app returns.

37. Check Health and Fitness Data Carefully

Health data can be sensitive and platform-specific.

Apple notes that encrypted computer backups can include Health data, while Apple’s iCloud ecosystem can also synchronize supported health information. Cross-platform migration may not carry health history automatically; Google’s current iPhone-to-Android page specifically lists Health data among items that do not transfer in its documented flow.

If health history matters, follow the health platform’s export or sync instructions before switching ecosystems.

38. Pair Watches and Wearables Only After the Phone Is Stable

Smartwatches, fitness trackers, earbuds, cars, and other Bluetooth devices may need to be paired again.

Do not spend time pairing every accessory before confirming that core phone data and authentication are safe. Finish the migration first, then restore accessories.

39. Check Wallets, Tickets, and Payment Cards

Digital wallet items may require re-verification on a new phone. Payment cards are often intentionally not copied as ordinary backup data.

Open the wallet app and review:

• payment cards;
• transit cards;
• boarding passes;
• event tickets;
• loyalty cards;
• digital keys.

Re-add items according to the issuer’s security process.

40. Treat Cryptocurrency Wallets as a Special Case

If you use a self-custody cryptocurrency wallet, losing the phone can be serious if the recovery phrase or hardware backup is unavailable.

Do not take screenshots of recovery phrases or place them in ordinary cloud notes. Follow the wallet provider’s recovery guidance and confirm that the recovery phrase or hardware key is stored securely offline.

A phone backup is not a substitute for the wallet’s own recovery system.

41. Test One Restore Before a High-Risk Reset When Possible

If the data is extremely valuable and you have access to a spare compatible device, a test restore can prove that the backup works.

This is especially useful for business phones, archival recordings, or complex app environments.

For ordinary personal upgrades, the new phone itself becomes the restore test: do not erase the old phone until verification is complete.

A compatible data cable can be useful for direct phone-to-phone transfer when supported. Image: J.Dncsn, Wikimedia Commons, CC BY-SA 3.0.

42. Worked Example: iPhone to New iPhone

A user has 180 GB of photos, banking apps, an authenticator, and years of messages.

Step 1: Confirm Apple Account credentials and iCloud storage.

Step 2: Run a current iCloud backup and verify the timestamp.

Step 3: Confirm iCloud Photos is synchronized.

Step 4: Verify authenticator and password-manager recovery.

Step 5: Use Quick Start with both iPhones on power and Wi-Fi.

Step 6: Leave the new phone connected while apps and photos continue downloading.

Step 7: Test messages, contacts, photos, banking, authenticator, cellular service, and password manager.

Step 8: Only then prepare the old iPhone for trade-in according to Apple’s erase procedure.

43. Worked Example: Android to New Android

A user has Google Photos, WhatsApp, downloaded PDFs, local voice recordings, and a Google Authenticator installation.

Step 1: Run Google backup and confirm “Backup complete” in Google Photos.

Step 2: Inspect Back up device folders so messaging images and screenshots are included if desired.

Step 3: Export the local Downloads and voice recordings to Drive or a computer.

Step 4: Confirm WhatsApp’s own backup or transfer readiness.

Step 5: Sync or transfer Google Authenticator codes.

Step 6: During the new Android setup, use cable transfer if convenient and select the data to copy.

Step 7: Verify files that Google says may not copy automatically.

44. Worked Example: iPhone to Android

A user changes platforms after ten years on iPhone.

Risk: The greatest danger is assuming that every iCloud category will enter Android automatically.

Plan: Use Google’s current Android Switch workflow, preferably the method supported by the new device. Review what the specific transfer method can and cannot move. Transfer or sync photos, contacts, calendars, messages, WhatsApp history, files, and account credentials according to the on-screen flow. Handle Health data, Safari bookmarks, paid apps, and other excluded data separately.

Verification: Keep the iPhone until iMessage transition, SMS reception, authentication, banking, media, and contacts all work on Android.

45. Worked Example: Emergency Backup From a Failing Phone

The phone is randomly shutting down and the charging port is unreliable.

Do not start with a full cosmetic migration.

Priority order:

1. Authenticator and account recovery.
2. Photos and videos.
3. Contacts.
4. Messages with important information.
5. Documents and recordings.
6. Password manager verification.
7. Full device backup if the phone remains stable.

Use cloud backup while the device is working and copy irreplaceable files directly when practical. If the battery is swelling, the phone is extremely hot, or it is physically unsafe, stop using it and seek professional service rather than forcing additional charging cycles.

46. Troubleshooting: The Backup Says There Is Not Enough Storage

First determine which storage is full: device storage or cloud storage.

For iPhone replacement, Apple may offer temporary iCloud storage to eligible users. On Android, review Google Account storage or copy critical files to a computer while deciding whether to purchase additional cloud storage.

Do not delete irreplaceable data from the phone until another verified copy exists.

47. Troubleshooting: Google Photos Says Backup Is Complete but Some Images Are Missing

Check:

• correct Google Account;
• Back up device folders;
• hidden or secure folders;
• other gallery apps;
• images saved in Downloads or Documents;
• recent media still processing.

Google’s current help pages specifically tell users to verify the selected backup account and device-folder settings.

48. Troubleshooting: Android Transfer Finished but Downloads Are Missing

This can be expected. Google’s documented “What won’t copy” list includes Downloads in some standard device-to-device migration scenarios.

Use the old phone’s Files app, cloud storage, or a computer to copy them manually.

49. Troubleshooting: The Authenticator Codes Are Gone

If using Google Authenticator with account sync, sign into the correct Google Account. If you used it without an account, the old phone may still be able to export codes through the transfer function.

If the old device is unavailable, use each service’s recovery process, backup codes, security key, or alternative verification method. There is no universal way to reconstruct a lost TOTP secret from the six-digit code alone.

50. Troubleshooting: The New Phone Has the Apps but Not Their Data

App installation and app-data restore are separate.

Google explicitly notes that not all apps can back up or restore all settings and data. Apple apps can also rely on their own cloud accounts rather than the main backup.

Sign into the app and check its own sync, backup, or import system. If the data remains only on the old phone, use the app’s export function before erasing it.

51. Troubleshooting: The New Phone Is Already Set Up

Some migration options are most complete during initial setup. Google notes that on certain Android versions and devices, additional transfer may be available after setup, but capabilities vary. Apple’s iCloud restore instructions generally require the new iPhone to be at the Hello/setup screen, meaning an already configured phone may need to be erased before a full restore.

Before erasing the new phone, confirm that any new data created on it has its own backup.

52. Troubleshooting: The Old Phone Screen Is Broken

If touch or display is unusable, cloud backup becomes more important because many direct-transfer methods require unlocking the old device and approving prompts.

Try:

• cloud restore from the latest backup;
• manufacturer accessibility or external-display options if supported;
• authorized repair to regain temporary access;
• a computer that was previously trusted by the phone.

A repair shop may not be able to recover encrypted data if the device cannot be unlocked, so prevention matters.

53. Troubleshooting: The Phone Was Lost or Stolen

Do not focus first on replacement convenience. Protect accounts.

Use the platform’s lost-device service, change high-risk credentials when appropriate, contact your carrier, and monitor financial accounts. Restore the replacement phone from the latest available backup.

If authenticator access was lost with the phone, use recovery codes or alternate trusted devices.

54. Create a “Before Erase” Final Checklist

• Current cloud backup completed.
• Photos and videos verified.
• Contacts verified by account.
• Calendar verified.
• Messaging-app backup or transfer completed.
• Authenticator works on new device.
• Password manager works on new device.
• Important Downloads copied.
• Voice recordings copied.
• Secure or hidden folders checked.
• Banking apps re-enrolled.
• Cellular calls, SMS, and data tested.
• Important notes verified.
• Wallet and tickets reviewed.
• Work account handled according to policy.
• New phone fully updated and stable.

55. Create a Small Independent Backup Once or Twice a Year

Phone-replacement day should not be the first time you think about backup.

For irreplaceable data, maintain periodic independent copies:

• export family photos to a computer or external drive;
• keep secure recovery codes outside the phone;
• verify the password manager;
• export important contacts;
• archive critical recordings and documents.

This reduces the pressure when a phone suddenly fails.

56. Build a Backup Routine That You Can Verify

A useful routine is:

Weekly: confirm cloud backup is enabled and not reporting an error.

Monthly: check photo backup status, review storage, and confirm the backup account.

Quarterly: verify authenticator recovery, password-manager access, and critical files.

Before travel or repair: run a manual current backup.

Before replacement or reset: complete the full category-by-category checklist.

57. What Not to Do

• Do not erase the old phone because the new phone reached the home screen.
• Do not assume every app stores data in the main device backup.
• Do not forget authenticator migration.
• Do not delete local photos until cloud status is verified.
• Do not store backup passwords only on the device being erased.
• Do not assume Android Downloads or hidden folders will transfer automatically.
• Do not hand over a trade-in before testing cellular service and two-factor authentication.
• Do not mix work data into personal cloud backups against employer policy.
• Do not factory reset a new phone to retry migration without backing up anything newly created on it.

58. A 30-Minute Fast Backup When You Are in a Hurry

If you have only half an hour before a repair appointment or emergency replacement, use this order:

Minutes 0–5: Plug in the phone, connect to Wi-Fi, verify Apple/Google account credentials, and start a manual device backup.

Minutes 5–10: Check photo backup status and recent media.

Minutes 10–15: Verify authenticator transfer/sync and password-manager access.

Minutes 15–20: Copy Downloads, recordings, documents, and other local files.

Minutes 20–25: Check messages, contacts, notes, and work data.

Minutes 25–30: Confirm backup completion and photograph or record any settings you know you will need later.

If backup has not finished, do not erase the phone merely because the appointment time arrived. Explain the situation to the repair or trade-in provider.

Frequently Asked Questions

Is iCloud Backup the same as iCloud Photos?

No. Apple treats syncing and device backup as related but separate systems. If iCloud Photos is enabled, photos are synchronized through iCloud Photos and are not simply duplicated inside the device backup in the same way as unsynced data.

Does Android backup everything on my phone?

No. Google states that Android backup can include apps and app data, call history, contacts, device settings, SMS/MMS, and additional data through supported Google apps, but not every app supports full backup and some data categories may require separate transfer.

Should I use cable or wireless transfer?

Use the method officially supported by your devices and convenient for the amount of data. A cable can be reliable for large transfers, while wireless transfer is easier when cables or adapters are unavailable. Keep both devices charged either way.

Do I need both a backup and direct transfer?

You do not always need both, but having a current backup before direct transfer provides a useful fallback if the transfer fails or the old device becomes unavailable.

Can I erase the old phone immediately after transfer?

Wait until you verify critical data, authentication, cellular service, messaging apps, photos, files, and banking access on the new phone. Some content continues downloading after setup.

Why did my apps come back but not my data?

Reinstalling an app does not guarantee that the app’s internal data was backed up. Some apps use their own accounts, exports, or encrypted transfer methods.

Will Google Authenticator transfer automatically?

If you sign into Google Authenticator with a Google Account and use its synchronization feature, codes can appear on the new device after sign-in. If you use Authenticator without an account, Google provides a manual QR-code transfer workflow from the old device.

What is the most important thing to back up first?

Prioritize irreplaceable and access-critical data: account recovery, authenticator codes, photos, contacts, important messages, documents, recordings, and password-manager access.

Should I delete photos from the old phone after they upload?

Only after you verify that the upload is complete and understand how the cloud service handles deletions and storage optimization. For irreplaceable media, an additional independent copy is safer.

What if I do not have enough cloud storage?

You can use a computer or external storage for local copies, purchase additional cloud storage, or—if eligible during an iPhone replacement—use Apple’s temporary iCloud transfer storage. Do not solve the problem by deleting important data before another copy exists.

Conclusion: Verify Before You Erase

A phone migration succeeds when the new device can operate independently of the old one. That means the photos are present, contacts are complete, messages are available, local documents have been copied, the authenticator works, the password manager opens, banking apps are re-enrolled, and cellular service can receive verification codes.

The biggest mistake is treating “backup” as one switch. Modern phones contain several overlapping systems: device backup, photo synchronization, app-specific clouds, local folders, authenticator secrets, account credentials, and carrier services. Each system may restore differently.

Your safest first step is simple: before replacing or resetting a phone, make a list of the data you would be genuinely upset to lose. Verify each category in a second location. Then create a current device backup. Transfer to the new phone. Test it. Only after the new phone proves that the important data is there should the old one be erased.

Sources and Further Reading

• Apple Support — How to Back Up Your iPhone, iPad, and iPod Touch
• Apple Support — Use Quick Start to Transfer Data to a New iPhone or iPad
• Apple Support — About Encrypted Backups on iPhone and iPad
• Apple Support — What Does iCloud Back Up?
• Apple Support — Temporary iCloud Storage for a New iPhone or iPad
• Google Android Help — Back Up or Restore Data on Your Android Device
• Google Android Help — Copy Apps and Data to a New Android Device
• Google Android Help — Copy Data From an iPhone or iPad to Android
• Google Photos Help — Back Up Photos and Videos
• Google Account Help — Transfer Google Authenticator Codes

Image Credits

• “Android and Apple comparison, front.jpg” — CeeJay95, Wikimedia Commons, CC BY-SA 4.0.
• “Google Photos freeing up phone space (October 2020) 04.png” — Alphabet/Google interface screenshot, Wikimedia Commons; public-domain eligibility noted on file page.
• “USB cable.jpg” — J.Dncsn, Wikimedia Commons, CC BY-SA 3.0.