How do I transfer my data and apps to a new phone in 2027?

The outcome you should expect

When a transfer works as designed, you power on the new phone, pick your language and region, connect to Wi-Fi, and the setup assistant asks whether you want to restore from a backup or set up as new. Choosing restore is the single decision that triggers everything else: contacts, call history, SMS and RCS or iMessage threads, photos and videos, calendar entries, notes, saved Wi-Fi passwords, alarms, accessibility settings, and the list of apps you previously had installed all come across.

What the operating system actually does is worth understanding, because it explains most surprises. Neither iOS nor Android copies an app's binary from the old device. Instead, the new phone reads the backup's manifest of installed apps, then downloads a fresh copy of each one from the App Store or Google Play. Separately, it restores that app's private data — saved logins, game progress, documents, preferences — from the backup, but only if the developer wired their app into the platform's backup APIs. So the app you get on the new phone is always the current version from the store, not the version you had, and its data arrives only if the developer cooperated.

For a typical user with 50-150 installed apps and under 100GB of photos, video, and messages, the whole process lands somewhere between 30 and 90 minutes of mostly unattended waiting. The phone is usable within the first 5-15 minutes for calls and messages; the long tail is app downloads and photo library streaming, which continue in the background while you use the device.

What you should not expect is a byte-for-byte clone. A predictable set of categories never transfers cleanly. Hardware-bound authenticator apps that generate time-based codes locally will not carry their seeds unless the developer added account-based sync. DRM-protected downloads — offline Netflix or Spotify libraries, purchased movies — do not move; you re-download them under the same account. Home screen widget layouts and folder arrangements sometimes reset to a default grid. And apps whose developers never implemented cloud sync open completely blank, as if freshly installed, because functionally they are.

Cross-ecosystem moves are a different animal. Apple's Move to iOS and Google's Android switching tools handle contacts, photos, calendar, and basic messages reasonably well, but they cannot move app data at all. An Android app and its iOS counterpart are separate pieces of software even when published by the same company, so there is no shared container to restore from. Budget 1-3 hours of manual sign-ins across the following week if you use 50 or more apps heavily.

What drives that outcome

Three variables explain nearly all of the variance in how a transfer goes: platform continuity, backup freshness and completeness, and how each individual app implemented backup support.

Platform continuity is the dominant factor. When you stay on the same platform, the OS vendor controls the entire backup format, and every app's restore hooks are calibrated against one known system. Apple's device-to-device migration and Google's restore flow both operate on a schema the vendor designed. The moment you cross platforms, the transfer tool can only move what is platform-agnostic: contacts via vCard or a similar interchange format, photos as files, calendar via CalDAV-style export, and plain text messages. Everything else depends on the publisher having built a separate cross-platform sync layer. Messaging apps, cloud storage, note apps, and password managers usually have; games, niche utilities, and older apps usually do not.

Backup freshness and completeness come second. Both iCloud and a standard Google Account ship with small free storage tiers — commonly 5GB and 15GB respectively — and photo libraries routinely exceed that. When storage runs out, the backup process does not always shout about it. It may back up contacts and settings while silently excluding the photo library, or stop syncing messages weeks ago. The restore on the new phone then succeeds, reports no error, and simply has nothing to bring over for those categories. Checking the "last backup" timestamp and your remaining storage headroom before you start is the highest-leverage five minutes in the whole process.

The third driver is app-level engineering. Every developer independently decides whether to hook into the OS backup APIs — CloudKit and the ubiquitous key-value store on iOS, Auto Backup and Backup Transport on Android. Large, well-maintained apps almost always do. Abandoned or small-team apps frequently do not, which is why you occasionally open a freshly transferred app and find it asking you to create an account you have had for six years.

There is also a device-capacity dimension. If the new phone has less storage than the old one, the restore flow may refuse a full app reinstall and instead prompt you to select which apps and how much of the photo library to bring. That is a design decision, not a bug, but it changes the transfer from a one-tap operation into a triage exercise.

Benchmarks and realistic ranges

For a same-platform transfer over solid home Wi-Fi with modern hardware, these are reasonable expectations.

The OS-level restore of core data — contacts, messages, settings, calendar, saved passwords, and photo metadata — typically completes in 5-20 minutes. This portion is small in bytes because it is mostly structured records, not media.

App redownload is the long pole. If you have 100 apps averaging 150-250MB each, that is roughly 15-25GB of downloads. On a 50-100 Mbps connection, expect 30-60 minutes. On a congested network, a shared connection, or a mobile hotspot, double or triple that. The phone will often let you start using it while downloads continue, so the wall-clock time until "fully done" is longer than the time until "usable."

Photo and video libraries are the other major sink. A library over 20,000 photos, or one heavy on 4K video, can add an hour or more — and much longer if the phone is streaming originals from cloud storage on demand rather than transferring device-to-device. This is where the difference between a cloud restore and a direct migration is most visible.

Direct cable transfers are consistently 2-4x faster for the bulk data portion because they bypass your internet connection entirely. A USB-C to USB-C cable between two modern Android phones, or a Lightning or USB-C cable between two iPhones, moves data at local bus speeds rather than upload/download speeds. If you are moving 200GB or more, wiring the two phones together is worth the extra two minutes of setup. Note that the cable only accelerates the device-to-device portion; app downloads still come from the store over your internet connection.

Cross-platform transfers benchmark worse on completeness even when they are fast on the data they do move. In practice, users report that the large majority of contacts, photos, and calendar entries arrive cleanly, but essentially none of the individual app data — saved logins inside third-party apps, in-app purchase history within those apps, local app files — transfers automatically. For a heavy app user, that means 1-3 hours of manual sign-ins spread across the first week, plus the friction of re-establishing payment methods, notification preferences, and widget layouts.

These are ranges, not promises. The single biggest lever you control is whether the old phone's backup was complete before you started.

Risks, edge cases, and failure modes

The most common failure is running out of cloud storage mid-backup, which silently truncates what is available to restore. You will not see an error on the new phone. You will notice weeks later that a batch of photos or a stretch of messages is missing. Before you begin, check your cloud storage headroom and either buy a temporary storage bump for the migration month or do a direct device-to-device transfer for anything storage-constrained.

Two-factor authentication is the sharpest edge case and the one most likely to cost you real time. Authenticator apps that generate time-based codes tied to that specific device — rather than syncing seeds to an account — will not transfer their codes. If you do not have backup codes saved separately, you can be locked out of banking, email, and work accounts until you complete each service's account-recovery flow, which can take days for financial institutions. Audit this before you wipe the old phone, not after. The safe sequence is to open every 2FA-protected account, generate or retrieve backup codes, and store them somewhere you can reach from a second device.

Encrypted local backups — as opposed to default cloud sync — sometimes fail quietly. If you forget the backup's encryption password, the restore may report success on the outer file structure while individual encrypted app data blocks fail to decrypt, reverting those apps to a blank state. There is no recovery path for a forgotten local backup password; the data is effectively gone. If you use encrypted local backups, store the password in a password manager before you need it.

Storage-tier mismatches cause a subtler problem. If the new phone has less capacity than the old one, the restore may refuse to complete a full app reinstall and instead prompt you to selectively choose which apps and how much photo library to bring over. Plan for this if you are not buying an equal-or-larger device. The practical workaround is to offload older photos and videos to cloud storage or an external drive before the transfer, so the new phone only has to absorb the recent library.

SIM and eSIM transitions are a separate process from data transfer entirely. Most modern setup flows bundle a prompt to move your cellular plan alongside the data restore, but on some carriers this remains a manual step — you may need to scan a QR code from the carrier, log into the carrier app, or call support. Skipping it leaves you with a new phone that has all your apps and data but no cell service. On eSIM-only devices there is no physical card to move, so the carrier's provisioning flow is the only path.

A final edge case: interrupting the app download phase. Force-closing the setup screen or powering off mid-restore can leave some apps in a corrupted, half-installed state. They will appear on the home screen, tap open to a blank or crashing screen, and require manual deletion and reinstall. Let the process run to completion, even if the phone is usable before it finishes.

A practical rollout plan

Treat the transfer as three distinct phases — prepare, transfer, verify — rather than one tap. The preparation phase is where nearly all preventable failures are avoided.

Prepare, the night before. Confirm the old phone's cloud backup is current: check the "last backup" timestamp and available storage headroom, and force a fresh backup if it is more than a day old. Write down or screenshot your 2FA backup codes for banking, email, and work accounts. Confirm your password manager is synced and that you can log into it from a second device. Note your home Wi-Fi password if it is not already synced through iCloud Keychain or Google's saved-password sync. Charge both phones to at least 50%, ideally to full. If you are moving 200GB or more, find a USB-C or Lightning cable that connects the two devices.

Transfer, 30 minutes to a few hours. Power on the new phone and choose "restore from backup" rather than "set up as new." That single decision is what triggers a real transfer of apps and data instead of a blank slate. If you have 50GB or more of photos, use a cable connection rather than Wi-Fi to cut the wait roughly in half. Let the phone finish downloading apps in the background rather than force-closing the setup screen. If the setup flow offers to transfer your cellular plan, accept it; if not, note that you will need to contact your carrier afterward.

Verify, over the first day or two. Open your most important apps first — banking, primary email, messaging, and any 2FA authenticator — and confirm they are logged in and current before doing anything else. This is when you catch the handful of apps that did not carry data over. Check that your photo library count roughly matches the old phone. Test that you can send and receive both SMS and RCS or iMessage. Keep the old phone charged and untouched — do not factory reset it — for at least one to two weeks as a safety net. If you discover a gap later, you can pull the missing data directly from the old device rather than relying on a backup that may have already rotated out.

Only after you are confident everything arrived should you wipe the old phone, and only after you have signed out of your accounts on it, especially any Find My or device-tracking service that would otherwise lock the device to your account.

Related questions

Can I transfer data from an iPhone to an Android phone or vice versa?

Yes, using Apple's Move to iOS or Google's cross-platform migration tool, but expect only contacts, photos, calendar, and messages to move. Individual app data and app-specific purchases generally do not carry across ecosystems.

Do I need Wi-Fi to transfer to a new phone?

No. A direct cable connection between the two phones is usually faster and does not depend on internet speed, especially for large photo and video libraries. You still need internet for app downloads from the store.

Will my apps automatically be logged in after transfer?

Most mainstream apps restore your login through the cloud backup, but some — especially banking apps and hardware-tied 2FA apps — require manual sign-in again for security reasons.

How long should I keep my old phone before wiping it?

One to two weeks is a safe buffer. That gives you time to catch and pull over anything that did not transfer cleanly before the data is gone for good.

What happens to subscriptions and in-app purchases when I switch phones?

Purchases tied to your App Store or Google Play account restore automatically on the new phone, since they are licensed to your account rather than the device.

FAQ

Do I lose text messages when I transfer to a new phone? No, as long as your old phone's backup included message history. Both iOS and Android back up SMS, RCS, and iMessage threads by default, and they restore as part of the standard transfer. The exception is if your cloud storage was full and messages were silently excluded from the last backup — check the backup timestamp before you start.

Is it safe to use public Wi-Fi for a phone transfer?

It is better to avoid it. Use a trusted home network or a direct cable connection. A phone transfer moves large volumes of personal data, and a weak public network adds both privacy risk and instability that can interrupt a multi-gigabyte restore partway through.

What if my new phone has less storage than my old phone? The setup process will typically let you choose which content to prioritize — recent photos over the full library, for example — rather than failing outright. You will need to manage the remainder manually afterward, offloading older media to cloud storage or an external drive.

Can I transfer apps without transferring photos? Yes. Most transfer tools let you select categories of data to restore, so you can bring over apps and contacts while leaving a large photo library in cloud storage to download later or not at all.

Why did some of my apps come over empty with no saved data? That app's developer likely did not implement the operating system's backup APIs for that data, which is common in smaller or infrequently updated apps. You will need to manually re-enter the data or reconnect the app's account.

Should I write down my Wi-Fi passwords before switching phones? It is a good safety net even though most saved passwords sync automatically through iCloud Keychain or a Google Account. A rare sync failure otherwise leaves you locked out of your home network until you reset the router.

Sources

• https://support.apple.com/en-us/HT204606
• https://support.google.com/android/answer/6193424
• https://support.google.com/photos/answer/6193313
• https://support.apple.com/en-us/HT203977
• https://www.verizon.com/support/data-transfer-faqs/
• https://www.samsung.com/us/support/answer/ANS00062633/
• https://support.google.com/accounts/answer/183723
• https://support.apple.com/en-us/102659

Related on PULSE

• How do I back up my phone before a factory reset?
• What's the difference between cloud backup and local backup for mobile devices?
• How do I set up two-factor authentication on a new device without losing access?
• Should I buy a phone with more storage or rely on cloud storage?
• What should I do before trading in or selling my old phone?
• How do I move my smart home app logins to a new phone?