Android 17 may soon make an iPhone-to-Android move more complete than some Android-to-Android upgrades, a sharp twist for a platform long criticized for uneven restore flows, according to 9to5Google.
The upgrade centers on Android Switch, Google’s migration tool for moving from iPhone to Pixel or another Android device. In Android 17, Google is expanding what can move across: iMessage history, media, stickers, home-screen layout, wallpaper, passwords, passkeys, Wi-Fi credentials, alarms, call history, encrypted RCS messages, files, folders, Calendar attachments, Apple Notes attachments and labels, accessibility settings, Google Account setup, and eSIM transfer where carriers support it.
Android 17 targets the parts of iPhone people fear losing
The headline feature is not technical completeness. It is emotional continuity.
A phone switch fails when the new device feels like a blank apartment. The apps may be there, but the old habits are gone. Message archives are missing. The home screen has to be rebuilt. Settings need to be rediscovered. That first hour can sour the whole switch.
Google’s move suggests a different sales pitch for Android: not just better hardware, better AI, or a cheaper device, but a lower cost of leaving iOS.
Paul Dunlop, Google’s Product Lead for Android Onboarding and Android Settings, described the Android 17 change as a major upgrade to the process used to move data from iPhone to Android. Android Authority also reports that Dunlop called it a:
“ground-up new iOS to Android switching experience for Android 17.”
That matters because Google is not merely adding another import checkbox. It is trying to compress the awkward transition period after someone leaves an iPhone.
For readers tracking how platform updates are becoming less about isolated features and more about daily-device continuity, this sits near other OS-level shifts we have covered, including the Android 17 Pixel bug, iOS 27 Indexing Stuck? Your Mac Reveals the Truth, and iOS 26 Turns AirPods Into Your iPhone Camera Remote.
iMessage history and home-screen layout attack two stubborn exit barriers
The most consequential additions are iMessage history and home-screen transfer.
Messages are not just chat logs. They are receipts, photos, family threads, work context, verification codes, travel details, and searchable memory. Losing that archive can make a new phone feel incomplete before the user even tests the camera or battery.
Android 17’s Android Switch upgrade reportedly migrates SMS, MMS, RCS messages, and iMessage history, including media and stickers. Android Authority adds that conversations and group chats can move with reactions, stickers, and threads.
The home-screen transfer is quieter but nearly as important. Android 17 can bring over the wallpaper, app layout, and related home-screen structure from the iPhone. That gives a new Android device a familiar map. Users do not need to remember where everything went. They can start from muscle memory.
That does not mean Android becomes iOS. The sources describe migration of history and layout, not continued iMessage service on Android or perfect preservation of every Apple-specific behavior. The practical win is narrower but meaningful: the user starts with more of their old phone intact.
The hard numbers are rollout limits, OS versions, and transfer gaps
There is no sourced market-share data in the supplied material, so the useful numbers here are about availability and constraints.
Google’s rollout starts with a “small percentage” of Android 17 devices. For now, 9to5Google says that means Pixel devices. The improvements are expected to expand “over the coming weeks and month,” with non-Pixel devices also getting the upgrades.
Android Authority says Android 17 stable is available on Pixel 6 and later devices. Google’s current support documentation for the older Switch to Android path says wireless transfer with the Android Switch app requires an iPhone on iOS 15 or later, while the Switch to Android app requires Android 12 and up.
The contrast with the older documented transfer model is stark:
| Data or setup item | Older Google support flow | Android 17 Android Switch upgrade |
|---|---|---|
| iMessage transfer | Cable-supported for texts, iMessages, and most iMessage content | Expanded message migration, including media, stickers, reactions, and threads per related reporting |
| Home-screen layout | Not listed as transferable | Wallpaper and app layouts transfer |
| Passwords and passkeys | Listed as not transferring | Passwords and passkeys transfer |
| Alarms | Listed as not transferring | Alarms transfer |
| Files | Listed as not transferring | Files and folders transfer |
| eSIM | Listed as carrier-handled | eSIM transfer, but not all carriers supported |
The strategic awkwardness is obvious. If Android 17 gives iPhone switchers a richer import path than some Android users get when moving between brands, Google has also exposed a weakness inside Android itself.
Google’s iPhone migration push exposes Android’s own restore problem
9to5Google makes the uncomfortable comparison directly: moving from a Pixel to a Galaxy, or from a Galaxy to an Oppo device, can still mean losing the home-screen layout and other information.
That is not a small problem. Android is spread across Google, Samsung, Oppo, Motorola, and other device makers. Each can add its own setup tools, apps, skins, and backup behavior. A same-brand upgrade can work well. A cross-brand Android move can feel less predictable.
Android 17’s new iPhone import flow appears to work around that by making Android Switch a stronger onboarding layer. Android Authority says the new experience is built into the core of Android and iOS and is wireless-first, while still supporting wired transfer.
The irony is hard to miss. Google may be making Android better at importing an iPhone than reproducing an old Android phone across manufacturers.
That is good for iPhone switchers. It is less flattering for loyal Android users who expect the platform to remember itself.
Google, Apple, carriers, and users do not want the same thing
For Google, the incentive is clear. Easier migration helps Pixel and Android partners compete for iPhone owners. It also makes the first Android session more likely to begin with a signed-in Google Account, transferred credentials, restored conversations, and fewer setup chores.
For Apple, the risk is narrower but real. If message history and familiar layouts move cleanly, leaving iOS becomes less painful. That does not erase Apple’s advantages. It does mean retention has to rely less on data gravity and more on the value of staying.
For Android OEMs and carriers, the upgrade could become a sales tool. A trade-in pitch lands better when the customer does not expect to lose years of messages or spend a night rebuilding their phone.
For users, the win is portability. The open questions are process-level. The sources say Android 17 uses native tools and can move more sensitive categories, including passwords, passkeys, encrypted RCS messages, and eSIMs. They do not spell out every security detail of how each category is handled, what fails when a carrier is unsupported, or how app developers will present cross-platform in-app data migration.
Android buyers should expect less rebuilding, not a perfect clone
For someone considering a switch, Android 17 could make the first week less punishing.
The biggest practical changes are simple:
- Messages: More conversation history should arrive, including richer media and thread context.
- Layout: The home screen can resemble the old iPhone setup instead of starting from zero.
- Credentials: Passwords, passkeys, Wi-Fi credentials, and the Google Account can move into place earlier.
- Carrier setup: eSIM transfer may work during setup, though Google says support does not cover all carriers yet.
- Apps: Developers can support transfer of in-app data through new cross-platform APIs.
That last point may become the most important over time. Reinstalling an app is easy. Restoring the state inside the app is the hard part. Android 17 gives developers a route to close that gap, but the source material does not say how many will support it or how quickly.
The watch item is adoption. If the rollout expands beyond Pixel devices, carriers support eSIM transfer broadly, and major app developers use the new migration APIs, Android Switch becomes more than a setup utility. If those pieces lag, Android 17 still improves the iPhone exit path — but unevenly.
The clearest test is simple: whether a former iPhone user can start using an Android phone on day one without feeling like their digital history was left behind.
Key Takeaways
- Android 17 could make leaving iPhone feel less disruptive by preserving more personal data and device setup details.
- Google is targeting emotional friction points like message history and home-screen familiarity, not just technical migration.
- A smoother switch could strengthen Android’s appeal to iPhone users considering Pixel or other Android devices.
