Migration has three steps:
- Switching to Adapty SDK.
- Changing Apple/Google server2server notifications webhook.
- Move historical data to Adapty to save statistics.
Let's quickly go through each part.
All you need to do is import Adapty SDK into your app and replace your legacy methods for making purchases, restoring purchases, and checking user subscription status with Adapty methods.
Your subscribers will migrate automatically
If a user was subscribed via, for example, your in-house solution and then you released a version with only Adapty SDK, his subscription status will be restored automatically.
You don't need to migrate historical data to sync subscriber status with an app.
It's important to set App Store Server Notifications to Adapty for proper work.
Get a raw Apple events
When migrating to Adapty, first you may want to give Adapty a try, we understand it. If for any reason you need raw Apple Events, for example, for your BI or for your legacy solutions, just set a URL where you'd like Adapty to forward raw events.
Moving historical data is optional and won't affect your subscribers state. However, there's a number of reasons why it's better to do so:
- Analytics will work correctly instantly. Adapty matches subscribers by original transaction ID and we don't count events that came from Apple webhook without exposing to Adapty SDK before.
- You'll get all your users and subscribers with properties ready to use. It's nice to have all users in one place, to further use in Segments, Promo Campaigns and Profiles/CRM.
Feel free to explore our guide on how to migrate historical data to Adapty.
Updated 7 months ago