Migration guide

Migrate from Adapty to Tierux

An AI agent does the heavy lifting — mapping Adapty products, access levels, and paywalls onto Tierux in minutes. What's left is your own validation and testing. Here's the step-by-step path.

Step 1: Inventory your Adapty setup

Export your Adapty configuration — products, access levels, placements, and paywall designs. Note which products grant which access levels, your trial and introductory offers, and any paywalls in active use. This becomes the spec you hand to the Tierux agent. Skip A/B test configs — they don't carry over.

Step 2: Recreate in Tierux via MCP agent prompt

Connect the Tierux MCP server to your AI agent. Give it the spec from step 1 and a single prompt: “Recreate this Adapty setup on Tierux.” The agent maps access levels to entitlements, recreates product mappings and trial configurations, and rebuilds your paywall — showing a preview for approval at each step.

Step 3: Swap SDKs, run both in parallel

Integrate the Tierux SDK alongside the Adapty SDK. During cutover, verify purchases against both platforms and confirm Tierux entitlements match Adapty access levels for the same users. Store subscriptions are untouched — both tools just observe them — so subscribers keep uninterrupted access.

Step 4: Decommission Adapty

Once Tierux correctly reflects entitlement state across your subscriber base — active, grace period, cancelled, expired — cut over exclusively to Tierux. Remove the Adapty SDK and cancel the subscription. Your entitlement data stays queryable via the Tierux REST API.

What the agent handles

Store configuration

Google Cloud service account, Developer API, Pub/Sub for RTDN — automated over MCP. Apple needs your Bundle ID plus one manual notification-URL step.

Access level → entitlement mapping

Each Adapty access level becomes a Tierux entitlement, and your Google Play and App Store products are mapped to it — including trial periods and introductory offers.

Paywall recreation

Your paywall's packages, pricing display, and copy are recreated on Tierux's remote paywall config. Preview before anything is committed. A/B test variants don't carry over — pick your winning variant and bring that.

Integration code

The agent writes the swap: SDK calls, the server-side verification endpoint, and entitlement checks tailored to your codebase. Review and test before shipping.

Also see: Tierux as an Adapty alternative · Tierux vs Adapty · migrating from RevenueCat.

Frequently asked questions
How do I migrate from Adapty to Tierux?
Migration happens in four steps: 1) Inventory your products, access levels, placements, and paywalls in Adapty, 2) Recreate them in Tierux via an MCP agent prompt — Adapty access levels map to Tierux entitlements, 3) Swap SDKs and run both platforms in parallel during cutover, and 4) Decommission Adapty once you've validated. The agent handles the recreation; you handle the quality assurance.
What maps to what between Adapty and Tierux?
Adapty access levels map to Tierux entitlements — both answer 'does this user have premium?'. Adapty products map to Tierux product-to-entitlement mappings. Adapty paywalls and placements map to Tierux's remotely configured paywalls. A/B test configurations don't carry over — Tierux doesn't ship paywall experiments yet.
Can I run Adapty and Tierux side by side during migration?
Yes. Run both platforms in parallel during cutover: verify purchases against both, confirm that Tierux entitlements match Adapty access levels for the same users, and cut over incrementally. Your subscribers keep uninterrupted access throughout.
Will my subscribers lose access during migration?
No. Store subscriptions live with Google Play and the App Store, not with Adapty — so migrating your verification layer doesn't touch the underlying purchases. By running both platforms in parallel and validating entitlement state before cutover, subscribers never see an interruption.

Ready to migrate?

Your AI agent does the setup in minutes. What's left is your own validation and testing.

Start free