Skip to content
AppDues
Log in
Contact salesSign up

Converting a Paid iOS App to Subscriptions Without Losing Existing Buyers

Moving from a one-time purchase to a subscription changes how you fund ongoing work, but the harder problem is fairness: people who already paid should not be charged again for the same premium access. This guide explains how to map legacy buyers to an entitlement, detect their original download version, and gate features through one clear access check.

Why the model change matters

A low one-time price leaves little room to fund years of maintenance. A subscription ties payment to continued use, so support can continue while the app remains in use, even if someone reinstalls it long after first downloading it. The trade-off is that existing paid customers need a clear, durable path to the features they already bought.

Protect existing customers first

Decide the boundary before writing code. Legacy buyers keep the old premium features; new subscription-only features can be reserved for subscribers. That distinction prevents the awkward case where someone buys the paid app shortly before the switch and is then asked to pay again immediately. Document which features fall on each side of the line.

Set up one entitlement for migrated premium access

Register the app, install the SDK, and create one entitlement for the migrated premium features. An entitlement is simply a named grant of access that can be active or inactive. For subscribers it stays active during the paid term and ends when that term ends; for legacy buyers it is granted based on their original download version instead of a purchase date.

Use the original download version to identify legacy buyers

Apple stores purchase data in a binary receipt. The field that matters here is the build number from the version first downloaded. If that build predates the subscription switch, treat the user as a legacy buyer. Parsing and validating that receipt on the device is fragile, because a modified device can present a fake local receipt, so server-side validation is the safer design when you do it yourself.

Sync before you trust the legacy check

With a managed SDK, receipt validation and syncing can be handled server-side, and the original download version becomes available on the customer record after transactions are synced. If that value is missing because transactions have not been restored or no receipt is present, keep premium features restricted until it can be verified. Sync after configuring the SDK, and only when a receipt is actually present.

Build one access manager as the source of truth

Create a single access manager that owns the decision. Register each entitlement together with the build versions that should grant it, early in the app lifecycle. The check then works in order: if the entitlement is active through the subscription system, grant access; otherwise compare the original download version against the registered legacy versions; otherwise deny access. Returning both a boolean and the customer record lets callers show premium content or, when access is denied, offer purchase restoration or a paywall. Because the SDK caches customer data, this check can be called wherever premium content is shown.

Extend and test the migration

The same pattern extends cleanly: register a different entitlement for a different set of legacy versions if access needs to differ by era. Keep a checklist before release: confirm the entitlement name, list every paid build number, verify sync runs after SDK configuration, test the missing-receipt path, and test sandbox separately because the original version is reported differently there.

Access decision checklist
User typeHow access is decidedResult
Current subscriberEntitlement is active through the subscription systemPremium access granted
Legacy paid buyerOriginal download version matches a registered paid buildPremium access granted
Unverified userCustomer record or original version is missingAccess withheld until sync/verification
New non-subscriberNo active entitlement and no matching legacy buildShow paywall or restore option

Decision summary derived from the entitlement and original-version logic described in the guide.

Frequently asked questions

How do I tell whether a user bought the paid version?

Check the first-download build recorded in the receipt data. If that build belongs to the paid era, grant the legacy premium entitlement; otherwise require an active subscription. When the value is missing, sync purchases first and keep premium locked until verification succeeds.

Why not just parse the receipt on the device?

Client-side checks alone are not trustworthy because a modified device can fake its local receipt. Server-side validation is the safer route when you handle receipts yourself.

What changes in sandbox testing?

In sandbox, the first-download version is reported as 1.0, so paid-version detection can behave differently from production. Test that path separately and expect a workaround may be needed.