Move from RevenueCat to openpurr without losing a subscriber
Keep the Purchases SDK your app already uses. Import your existing customers from RevenueCat's export: openpurr fetches every purchase from Apple and Google itself. Old app versions keep working while people update.
Updated
In short
- openpurr is a self-hosted, open-source RevenueCat alternative. It works with the official, unmodified RevenueCat Purchases SDK.
- Your app adds one line (the SDK's proxy URL) and a one-time
syncPurchasescall. The rest of your purchase code stays the same. openpurr importbrings existing customers over from RevenueCat's export. The purchases themselves are fetched from Apple and Google, not copied.- App Store apps can use RevenueCat's Scheduled Data Export. Google Play needs a migration export from RevenueCat Support, the only one with purchase tokens.
- Both backends stay up to date until most people have updated the app, so nobody loses access.
- On Cloudflare's free plan, the import handles about 2,500 customers a day. On Workers Paid, a large import takes hours.
How a RevenueCat migration works
openpurr doesn't copy purchase records out of RevenueCat. It only needs to know who owns which purchase, then asks the stores, exactly as it does when your app posts a purchase.
The import
RevenueCat's export says which app user owns which store purchase. openpurr import asks Apple and Google for each purchase and records the store's answer for that user. It brings everyone over at once, including people who never open the app again.
The app update
The new version points the Purchases SDK at openpurr and sends each customer's purchases once with syncPurchases. That catches anyone the export missed, and anyone who bought after it was made.
Both backends, for a while
Old app versions keep talking to RevenueCat until people update. RevenueCat forwards Apple's notifications to openpurr, and a second Pub/Sub subscription does the same for Google, so both stay current.
What changes in your app
Set the proxy URL before configure, and send each customer's purchases once. The same two changes work on Android, Flutter and React Native; the guide has the code for each.
// Before configure(): the only line most apps add
Purchases.proxyURL = URL(string: "https://purchases.example.com")!
Purchases.configure(withAPIKey: "appl_…")
// Once per install: send this customer's purchases to openpurr
let synced = "openpurr.synced"
if !UserDefaults.standard.bool(forKey: synced) {
Purchases.shared.syncPurchases { _, error in
if error == nil { UserDefaults.standard.set(true, forKey: synced) }
}
}Importing customers from RevenueCat
The openpurr CLI reads RevenueCat's columns as they are: app user IDs, App Store transaction IDs, Google Play purchase tokens, and attributes such as $email.
npm install -g @openpurr/cli
openpurr login --url https://<your back office>
# Check the first rows: asks Apple and Google, writes nothing
openpurr import revenuecat-export.csv --dry-run --limit 50
# Import everyone. Stop any time; run it again to carry on.
openpurr import revenuecat-export.csvNobody loses access
A purchase the app has already sent for a customer stays theirs; the import never moves it.
No duplicate webhooks
Imported purchases aren't new, so openpurr sends no events for them.
Honest charts
Imported customers are dated from their first purchase, not counted as new on import day.
Your app keeps working
On Cloudflare's free plan, the import stops at 90% of a daily limit and carries on the next day.
Stop and resume
Progress is saved. Importing a row twice changes nothing, so a newer export can be run again.
Try it first
A dry run asks the stores and reports what would happen, writing nothing.
How to migrate from RevenueCat in seven steps
Both backends keep running until you're ready to switch, so customers on older app versions keep their access.
Set up openpurr
Deploy openpurr Lite to your Cloudflare account, give it App Store and Google Play API access, and recreate your products, entitlements and offerings with the same identifiers. You can even keep your RevenueCat public SDK keys.
Keep both backends informed
Set openpurr as RevenueCat's Apple Server Notification Forwarding URL, and add openpurr's push subscription to your Play notifications topic.
Get your export
App Store only: RevenueCat's Scheduled Data Export has what's needed. With Google Play, ask RevenueCat Support for a migration export, since only that one has purchase tokens. The guide has a request you can copy.
Import
Run
openpurr import, with a dry run first. Problems with single rows go to a report and don't stop the import.Ship the app update
Add the proxy URL and a one-time
syncPurchases. Release it once the import has finished.Check
openpurr doctorchecks the setup. Look up customers you know, and compare active subscriptions with RevenueCat's charts.Finish the switch
Once most customers have updated, point Apple and Google straight at openpurr, turn on openpurr's webhooks, and turn off RevenueCat's.
What moves from RevenueCat, and what doesn't
| Subscriptions and purchases, with renewals, refunds, grace periods and expiry | Yes, fetched from Apple and Google |
|---|---|
| Who owns which purchase | Yes, from RevenueCat's export |
| App user IDs, including anonymous ones | Yes, unchanged |
| Customer attributes ($email, $displayName and your own) | Yes, from an Audience export |
| Products, entitlements and offerings | You recreate them, with the same identifiers |
| Chart history before the switch | Partly: keep RevenueCat's chart CSVs for your records |
| Paywalls, experiments, integrations, Customer Center | No: openpurr doesn't have them |
RevenueCat migration FAQ
Do I have to change my purchase code?
No. openpurr works with the official, unmodified RevenueCat Purchases SDK. The app update adds the proxy URL before configure, and a one-time syncPurchases call. getOfferings, purchase, restorePurchases, logIn and the rest stay as they are.
Do I need RevenueCat's help to migrate?
For App Store apps, no: RevenueCat's Scheduled Data Export has the transaction IDs openpurr needs. For Google Play, yes: according to RevenueCat's documentation, only a migration export prepared by RevenueCat Support includes the purchase tokens Google requires.
What about customers who never update the app?
The import covers them: their purchases are fetched from Apple and Google and assigned to the same app user IDs. While they're still on an old app version, that version talks to RevenueCat, which is why both backends stay informed until most people have updated.
How long does an import take?
Each customer takes about 30 database row writes. On Cloudflare's free plan, that's about 2,500 customers a day, and the import pauses itself at the daily limit and resumes the next day. On Workers Paid ($5 a month), a large import takes hours.
Is my data copied from RevenueCat?
Only the mapping of app users to store purchases, plus attributes if you import them. The purchases themselves come straight from Apple and Google, so openpurr records the stores' current truth, renewals and refunds included.
Ready to switch?
The guide walks through every step. If something in your setup doesn't fit, open an issue: migrations shape what gets built next.
