Apple is building a new way for developers to retire an old app and hand its data straight over to a replacement, without making users start from scratch. The feature is showing up in code found inside the iOS 27.2 beta.
Some developers occasionally sunset an app and launch a new one in its place. Even when the transition is handled well, users often still have to manually move data that isn’t stored in the cloud. 9to5Mac spotted the change in the first iOS 27.2 beta.
The Feature Only Works Between a Developer’s Own Apps
Apple has built a boundary into the system. This migration flow only works when a developer replaces one of its own apps with a designated successor. It won’t move data between apps built by two different developers, even in the same category. 9to5Mac says it will keep watching the iOS 27.2 beta cycle for more details on how developers implement the feature.
iOS Will Ask Before Moving Data to the New App
With iOS 27.2, Apple is adding a system-managed migration flow that transfers an app’s data and supported settings to its designated successor. The old app gets deleted once the transfer finishes.
Based on the beta code, users will see an alert along these lines:
The developer recommends moving your existing app data and settings to the new app. iPhone can do this for you now, before you start using your new app. Afterwards, the old app will be deleted from this iPhone.
Two options follow: “Move App Data and Settings” or “Don’t Move Anything.” Users who decline get a second warning that some preferences, including notification and location settings, may need to be set up again from scratch.
The Migration Covers Settings Apps Cannot Move on Their Own
This isn’t limited to files sitting in local storage. Based on the current implementation, iOS can carry over a wide range of system-level permissions and preferences that normally reset when you install a fresh app:
- Privacy, location, and Health authorization decisions
- Notification settings, including accessory notification settings
- Per-app Do Not Disturb and Focus settings
- App locking and protection settings
- CarPlay icon order and compatible widget layouts
- Live Activities and accessory Live Activities
- Access to associated accessories
- LaunchServices preferences, fonts, capture-related defaults, telephony data, and Secure Element services
That list covers all the settings users forget that they exist until they’re gone. Right now, switching apps means re-granting permissions one by one and hoping you remember which toggles mattered.
Our Take
I think this is a smart, narrow fix for a problem Apple rarely gets credit for solving well. App replacements aren’t common, but when they happen, the friction falls entirely on the user, not the developer. Handling the migration at the system level means Apple controls the permission handoff instead of leaving it to each developer’s own onboarding flow.
