Migration guide

Migrate from RevenueCat to Tierux

An AI agent configures Google Play infrastructure and maps your products, prices, and entitlements onto Tierux in minutes. App Store Connect product and notification setup remains manual, and validating the result before cutover is on you. Here's the step-by-step path.

Step 1: Inventory your products & entitlements in RevenueCat

Export your current RevenueCat configuration — products, entitlements, offerings, and packages. Note which entitlements map to which products and your pricing tiers. This becomes the spec you'll hand to the Tierux agent. Trial and introductory-offer configurations aren't recreated by the agent — note those separately to set up directly in Play Console / App Store Connect.

Step 2: Recreate in Tierux via MCP agent prompt

Connect the Tierux MCP server to your AI agent with your API key. Give it the spec from step 1 and a single prompt: "Recreate this RevenueCat setup on Tierux." The agent creates your store configuration, maps products to entitlements, builds your paywall, and shows a preview for approval — in minutes, not weeks.

Step 3: Swap SDKs, run both in parallel during cutover

Integrate the Tierux SDK alongside your existing RevenueCat SDK. During the cutover period, verify purchases against both platforms and validate that entitlements match. Your subscribers maintain uninterrupted access — both platforms run side by side while you confirm correctness.

Step 4: Decommission RevenueCat

Once you've validated that Tierux correctly reflects all entitlements across your subscriber base — active, grace period, cancelled, and expired — cut over exclusively to Tierux. Remove the RevenueCat SDK and cancel your RevenueCat subscription. Your data remains accessible via the Tierux REST API.

What the agent handles

Store configuration

Google Cloud service account, Developer API, Pub/Sub setup — automated. Apple requires your Bundle ID plus one manual notification-URL step. The agent handles what RevenueCat's guide walks you through manually across two consoles.

Product mapping

Your Google Play and App Store products are mapped to Tierux entitlements. The agent creates the product-to-entitlement relationships; trial periods and introductory offers aren't configured by the agent — set those up directly in Play Console / App Store Connect.

Paywall recreation

Your paywall configuration — packages, pricing display, and feature lists — is recreated on Tierux. Preview the result before the agent commits anything to production.

Integration code

The agent writes the integration code for your app — the SDK calls, verification endpoints, and entitlement checks — tailored to your existing codebase. Review and test before shipping.

Frequently asked questions
How do I migrate from RevenueCat to Tierux?
Migration happens in four steps: 1) Inventory your products and entitlements in RevenueCat, 2) Recreate them in Tierux via an MCP agent prompt (the agent does the work in minutes), 3) Swap SDKs and run both platforms in parallel during cutover to validate, and 4) Decommission RevenueCat once you've confirmed everything works.
Can I run RevenueCat and Tierux side by side during migration?
Yes. The recommended approach is to run both platforms in parallel during cutover. Verify purchases against both RevenueCat and Tierux, validate that entitlements match, and cut over incrementally. This ensures zero downtime for your subscribers.
How long does migrating from RevenueCat take?
The AI agent configures Google Play infrastructure and handles product recreation and integration in minutes; App Store Connect product and notification setup remains manual. After that, validation is on you — typically 1–2 weeks of parallel running to ensure entitlements match, edge cases are covered, and your team is comfortable cutting over.
Will my subscribers lose access during migration?
No. By running both platforms in parallel, your subscribers maintain uninterrupted access. Purchase verification happens against both RevenueCat and Tierux during the cutover period. Once you've validated that Tierux correctly reflects all entitlements, you switch exclusively to Tierux and decommission RevenueCat.

Ready to migrate?

Your AI agent configures Google Play infrastructure and Tierux-side setup in minutes; App Store Connect product and notification setup remains manual before you validate and cut over.

Start free