RevenueCat helps you build payments and subscriptions in your mobile apps - from simple in-app-purchases to complex multi-channel subscriptions. Follow our development quickstart to start building your integration.

Get Started

Migrating Subscriptions

How to migrate subscriptions from your existing setup

If you already have an existing app that is using subscriptions, it's easy to migrate them over to RevenueCat. You can use the Purchases SDK to replace all of your in-app-purchase code, or you can just use it along side your current stack to track in-app-purchases and benefit from our charting, webhooks, and other integrations.

Client Side Migration

This section assumes you've followed our Quickstart section of our Getting Started guide to install and configure our SDK.

The Purchases SDK automatically detects new transactions and sends them to RevenueCat. However, when migrating from an older system, you need to tell Purchases to sync to ensure we are tracking your subscribers correctly.

The way to do this is: if your existing subscription code knows you have a subscription, but RevenueCat does not, then restore transactions.

See the following pseudo example.

const isSubscribedInOldSystem = oldTracking.isSubscribed();
const isSubscribedInRevenueCat = purchaserInfo.hasActiveEntitlement("my_entitlement_name");

// If the old system says we have a subscription, but RevenueCat does not
if (isSubscribedInOldSystem && !isSubscribedInRevenueCat) 
  // Tell Purchases to restoreTransactions. 
  // This will sync the user's receipt with RevenueCat.

When a subscriber launches with the first version containing Purchases it will trigger a restore. Once the restore is complete, it won't be triggered again.

Use RevenueCat Backend Only

In some cases, if you have already built a functioning subscription system, it may not be possible or feasible to use the Purchases SDK to make purchases. However, you can still use the SDK to get access to the advanced charting, webhooks, and attribution that RevenueCat can provide.

By simply setting up and instantiating an instance of Purchases, any receipt will automatically be recorded and stored in the RevenueCat backend. It's important that you still implement the delegate/listeners (even if they're empty) and set finishTransactions to false. This lets Purchases know that another system is in place to validate purchases.

let purchases = RCPurchases(apiKey: "my_api_key")
purchases.delegate = self
purchases.finishTransactions = false


If you aren't using Purchases SDK to make the purchase. Be sure to the listener/delegate and finishTransactions to false.

Configure entitlements for accurate pricing

If you aren't using Purchases SDK to make the purchase. Make sure you've properly configured entitlements in the dashboard to get accurate pricing information.

Capturing Old Data

If you wish import historical data from users who no longer use your app you can send us a bulk receipt file for import. Email us for details.

Next Steps