Migration6 min read

Moving a live app off RevenueCat, in phases

Six phases, each with a way back, and why subscribers never notice the move from RevenueCat or Adapty to Xee.

Changing the code that takes your money is the change people put off longest. The risk is real: a subscriber who paid yesterday opens the app today and sees a paywall. So the move to Xee is built to never have that moment.

The xee-migration skill does the work in your coding agent. It first lists every call your app makes to the old SDK and writes a plan, call by call, for your yes. Then it moves in six phases. Each one ships on its own, and each has a way back.

1. Set up Xee next to the old SDK

Xee is added and activated. Nothing reads from it yet. Your app behaves exactly as before.

2. Move paywall content

The text, prices and switches your paywall reads from the old platform's remote config move into Xee values, with their live values as defaults.

3. Run both for access, with a one-time restore

For a while the app asks both platforms whether a user has access, and grants it if either says yes. A one-time restore brings each existing subscriber's purchases into Xee. Nobody loses access, even if one side is behind.

4. Move purchases

New purchases go through Xee, which checks each one with Apple on the server.

5. Point Apple's notifications at Xee

Renewals, refunds and billing issues now reach Xee directly from App Store Server Notifications.

6. Remove the old SDK

Only when Xee has seen every subscriber does the old SDK come out. Until then, going back is one change.

What you do

Say yes or no at each step. The skill edits, switches and removes nothing without that yes. If you want a person with you for it, the Xee team can plan it with you.

Ready to grow for free

Every agent comes standard, and it is free until your app makes $5K a month.