Connected stores
Apple + GoogleSelect subscriptions and one-time products from your store catalog.
Move subscription infrastructure without moving blind.
Bring your products, access rules, and purchase evidence. Review the catalog, verify existing purchases, and choose when to switch.
Available in staging · Source configuration stays under your control.
Preview first
Every changeSee additions, existing entries, and conflicts before applying.
Resume purchases
CLI checkpointsContinue interrupted verification without redoing completed records.
A practical path from your existing integration.
Configuration and verified purchases have distinct import steps. Keep your customer IDs stable and validate the cases that matter before releasing.
Migration workflow
Connect. Preview. Verify. Switch.
Start with the catalog, then move verifiable store evidence under your existing App User IDs.
ConnectMatch your store identities
PreviewReview catalog additions
VerifySubmit existing purchases
SwitchRelease after validation
Store catalog
Choose products from the source.
Apple subscriptions and in-app products. Google subscriptions, base plans, and modern one-time products.
Optional access mappingRegister products before their first purchasesupported
Complete paginationA failed page stops the importchecked
RevenueCat
Bring the configuration you already have.
The CLI reads matching products, entitlements, offerings, and packages through RevenueCat's V2 API. The source key stays on your computer.
cherrysub migrate revenuecat APP_ID \ --source-project RC_PROJECT_ID # Review first, then add --apply.
Verified purchases
Continue where the last run stopped.
Submit StoreKit 2 transactions and Google purchase tokens. A private checkpoint remembers accepted records without storing raw purchase evidence.
cherrysub migrate purchases purchases.csv \ --apply --checkpoint progress.jsonl # After interruption, add --resume.
Conflict handling
Keep your access policy intact.
Existing entries are preserved. Stale previews and conflicting mappings block application. A catalog import commits its additions together.
Product identityExact app, store, and product identifierspreserved
Google base plansDifferent entitlement policies require reviewchecked
Current product setActivate the imported set only when requestedexplicit
Know what moves
An honest migration boundary.
Portable CSV/JSON covers other catalogs. Purchase verification uses authoritative store evidence; history, customer aliases, paywall layouts, experiments, and targeting need a separate plan.
Use the complete guide for templates, exact limits, permissions, checkpoint recovery, and the cutover checklist.
Start with a catalog preview.
Choose your app, connect the source, and see exactly what will be added.