Replace an Apple business app without losing data

Article created October 20, 2026 · Source reviewed October 20, 2026 · Official source: Apple Developer · Topic: business apps, migration, MDM, and continuity

In its October 13, 2026 Developer agreement, Apple defined an App Replacement Entitlement: when a replacement app first launches, a system sheet can offer the user a choice to move data and settings from the original app and then delete it. For an organisation, the mechanism can reduce visible disruption, but it does not replace a migration plan, MDM control, or data validation.

1. What Apple specifically permits

Apple restricts this entitlement to an original app and replacement app under the same Apple Developer Program membership. Both must have substantively the same primary purpose and functionality. The mechanism Apple describes operates at first launch of the new app and gives the user a choice to move data and settings, then delete the old app.

The announcement alone does not publicly describe transferable data formats, supported platforms, the entitlement request process, or behaviour under silent deployment. Teams should therefore confirm these points in the documentation and permissions actually supplied to the project before making commitments to the business.

2. What the mechanism does not solve

A business-app migration often involves more than its local container: federated authentication, certificates, keys, server data, deep links, notifications, extensions, compliance, licences, and MDM rules. A system-assisted transfer does not prove that a session remains valid, remote data is consistent, or dependencies have been recreated.

Deleting the original app should be a controlled outcome, not the project’s starting point. Before cutover, the organisation needs to distinguish data that will be moved, resynchronised from a service, exported separately, or intentionally left behind.

3. What does this announcement change for a Belgian or French organisation?

For an SMB, it opens a clearer path to replacing an internal app without requiring a complex procedure from every user. For a mid-market organisation, large enterprise, or public body, it primarily requires new coordination among the publisher, mobile team, Apple Business Manager owner, MDM, identity, security, and support.

In Belgium and France, the transfer still needs to be documented according to the nature of the data and organisational policy. The entitlement does not change responsibility for personal data, retention duties, or the need to inform users. A cross-border migration or one involving a processor must continue to follow the usual GDPR and contractual controls.

4. Underside analysis: separate app replacement from deployment

Our view is that the entitlement provides a transition experience, not a fleet strategy. Apple Business Manager and MDM determine how the new app is assigned and installed; the app orchestrates the permitted transfer; directory and business services restore access; support handles exceptions. Blurring these layers creates devices where both apps coexist, neither is configured correctly, or the old app disappears before validation.

This method complements our guide to the MDM self-service app catalogue and our analysis of business apps on the new Apple OS releases. Replacement should become a tested lifecycle scenario, with a pilot cohort and measurable criteria.

5. Recommended migration plan

• Confirm app, platform, and identifier eligibility with Apple before designing the journey.
• Map local data, server data, settings, identity, certificates, extensions, notifications, and MDM dependencies.
• Define a successful transfer and how service will be restored if the new app fails.
• Deploy both apps to a pilot ring, test first launch across several data states, and observe MDM inventory.
• Remove the old app from assignments only after validating data, identity, business functions, and support.
• Measure migrated, declined, offline, and failed devices, retaining an exception process until closure.

Official sources: Apple’s Developer agreement update dated October 13, 2026 and the Apple Developer Program License Agreement, reviewed October 20, 2026.