Migrating an iOS app from paid upfront to subscription: what Apple’s rules mean for your existing customers

Switching your iOS app from a one-time paid download to a subscription model requires navigating Apple’s user-protection rules, pricing from scratch, and communicating the change without losing existing customers. This guide covers all three.

The economics of paid-upfront iOS apps have become increasingly difficult to sustain. Revenue resets to zero between acquisition spikes, update expectations are high, and the App Store's merchandising systems increasingly favour apps that build long-term user relationships. It is no surprise that the number of developers migrating from paid-upfront to subscription is growing year on year.

But the transition is not simply a matter of adding a new product type in App Store Connect and flipping a switch. Apple's guidelines, your existing customers' legitimate expectations, and the mechanics of StoreKit combine to create constraints that shape every decision in the process. This guide walks through what you are actually permitted to do, how to price your new subscription, how to communicate the change, and what to watch in the first 90 days after launch.

The constraint you cannot ignore: existing buyers retain what they paid for

Apple's App Store Review Guidelines are explicit on the foundational point: if a user has already purchased your app or a feature within it, you may not subsequently restrict access to that purchase without providing a refund. The practical consequence for a migration is significant.

Suppose your app was available for $4.99 as a paid download, including a full feature set. You decide to go free with a subscription paywall. New users, downloading after the change, must subscribe. But users who paid $4.99 before the change must retain access to the feature set they purchased — indefinitely. You cannot require them to subscribe to regain access to what they already own.

This constraint actually points toward a workable product architecture. Many developers who have successfully made this transition use the following structure: the app is free to download; users who purchased before the migration date are identified via StoreKit 2's Transaction.currentEntitlements or original-purchase-date in the transaction history and granted a permanent entitlement; new users encounter a subscription paywall. Subscription-only features — those introduced after the transition — are unavailable to the grandfathered cohort unless they voluntarily subscribe.

This structure respects Apple's guidelines and user expectations while building a subscription business going forward.

What Apple permits — and the technical implementation

Beyond the core constraint, there are several things Apple permits that developers sometimes overlook when planning a migration:

Making the app free. You can change a paid app's price to free at any time in App Store Connect. This is an ordinary price change, processed within hours. Once free, all new downloads arrive without an upfront charge and your subscription becomes the sole monetisation mechanism for new users.

Adding an auto-renewable subscription product. Auto-renewable subscriptions are a separate product type in App Store Connect, organised into subscription groups. The structural decisions — how many tiers, which durations to offer, how groups relate to each other — need to be made before you configure anything in App Store Connect. The subscription group architecture guide covers those decisions in full.

Introductory offers for new subscribers. Apple allows introductory pricing (free trials, discounted recurring periods, discounted upfront periods) for users who have not previously subscribed to a product in the same subscription group. For a migration, this is the primary friction-reduction tool for incoming new users. The introductory offers mechanics guide covers eligibility rules, offer types, and App Store Connect configuration.

Promotional offers for existing users. If you want to invite grandfathered paid customers to subscribe voluntarily at a discounted rate, Apple's promotional offer system is the mechanism — it requires server-side signature generation and lets you target specific cohorts without making the offer publicly visible.

Pricing your subscription: solving the anchor problem

Paid-upfront developers face a specific pricing challenge: their existing users paid a defined one-time amount, and that number becomes a psychological anchor — for users and developer alike. Setting your subscription price in relation to the old paid price is usually a mistake. A $4.99 paid app does not imply a $4.99 per year subscription is fair, nor that $4.99 per month is defensible. Start instead from the value delivered per period.

What would a user realistically get from your app in a month? In a year? What do directly comparable apps charge? What does the price represent in markets where purchasing power differs substantially from the US? These questions produce a defensible price, rather than one derived from an arbitrary historical data point.

Lead with annual pricing. Monthly subscriptions have systematically higher churn than annual subscriptions across nearly every app category. Published cohort analyses from RevenueCat have shown that annual subscribers retain at substantially higher rates year-over-year compared to monthly subscribers within the same apps. For a migration scenario where you are trying to establish a subscriber base from scratch, annual pricing minimises churn during the critical first months when your subscription mechanics are untested.

Position monthly as the high-commitment fallback, not the entry point. If you offer both monthly and annual, price the monthly option so the annual plan is clearly the better deal — typically pricing the monthly at a rate that makes annual look like a two- to three-month saving. This anchors users toward the annual option while leaving a lower-commitment path available for those who genuinely want it.

Price per territory, not per USD equivalent. If your paid app was distributed globally, your existing user base includes customers from markets where a US-equivalent subscription price represents a meaningful daily cost. Apple's territory pricing controls give you per-region flexibility, and the AppsOps pricing tool surfaces current App Store price tiers across territories to make the purchasing-power comparison concrete. Research from Phiture and others in the mobile growth space has consistently found that PPP-adjusted pricing reduces churn in emerging markets without proportionally reducing revenue when the price is still set meaningfully above the floor.

Communicating the change: what to say and when

Developers who handle migrations poorly almost always fail on communication rather than product mechanics. The rules of the product become clear once you understand Apple's guidelines; communicating them to users who have no reason to assume you won't take something from them is the harder problem.

Announce in-app before the change goes live. A banner or non-blocking modal in the app — visible when users open it — is more reliable than App Store update notes or email (which requires an opt-in list you may not have). The message should state what is changing, when it takes effect, and what existing users will specifically retain. Concrete language outperforms vague reassurance: "your current feature set stays unlocked forever, no subscription required" lands differently than "we appreciate your continued support."

Give at least 30 days' notice where possible. Surprise is the primary driver of angry reviews during model transitions. A 30-day notice period gives users time to make a considered decision, reduces the impulse-review rate immediately after launch, and gives you time to address early questions in support and review channels before the broader user base encounters the change.

Use App Store update notes honestly. The version that introduces the subscription should describe it plainly. "This update introduces a subscription model for new users. Existing purchasers retain full access to all current features." is the right register — factual, not defensive, not marketing language. App Store reviewers and users both read update notes, and evasive language there generates distrust that in-app messaging cannot easily repair.

Respond to reviews during the transition window. App Store Connect allows developer responses to reviews. During a model change, this channel matters more than usual. A prompt, honest response to a negative review — acknowledging the concern, clarifying what grandfathered users actually retain — sometimes results in a rating update. Users who are ignored rarely change their rating.

Metrics to watch in the first 90 days

A model migration produces a concentrated window of signal. The risk is over-reacting to early noise or under-reacting to genuine structural problems. Knowing which metrics lead and which lag prevents reactive decisions that fix the wrong thing.

Trial start rate. What percentage of new free-download users begin a trial? A rate below roughly 10–15% for a productivity or utility app with a prominent paywall more often signals a paywall presentation or onboarding problem than a price problem. Fix the presentation before adjusting the price — the two have different root causes and different fixes.

Trial-to-paid conversion rate. Of trial starters, what percentage convert to a paying subscription? This is the primary signal for whether your value proposition is clear by the time users reach the trial end. Industry practitioners including RevenueCat have noted that 7-day trials tend to convert at higher raw rates than 3-day trials for many productivity app categories, though the right duration is always category-dependent and worth testing systematically.

Refund rate in the first two weeks. A spike in refund requests immediately after launch typically signals communication failure — users who feel they were misled by the change. Apple's finance reports in App Store Connect include refund data. If refund rates are materially elevated above your paid-app historical baseline, review your in-app messaging and App Store listing copy before making any pricing changes.

Rating trajectory. App Store rating averages can drop sharply during a migration announcement period. Distinguish between reviews that cite communication issues (addressable) versus reviews that cite price (harder to resolve without structural change). The former should trigger messaging and copy revisions; the latter should be weighed against conversion and retention data before acting.

For deeper guidance on reading the underlying data in App Store Connect's reporting tools, the Sales and Trends reporting walkthrough covers the dashboards most directly relevant to subscription health in the first months after launch.

Sources and further reading

• App Store Review Guidelines — Apple Developer (section 3.1 covers in-app purchase rules)
• StoreKit documentation — Apple Developer (transaction history, entitlements, subscription APIs)
• In-App Purchase overview — Apple Developer
• The State of Subscription Apps 2024 — RevenueCat (annual benchmark report)
• iOS subscription tutorial with StoreKit 2 — RevenueCat Engineering Blog
• Phiture Mobile Growth Stack — subscription retention and paywall strategy resources