Skip to main content
Solved

How to migrate old subscriptions when i don't have complete data?

  • October 15, 2021
  • 2 replies
  • 233 views
R
Forum|alt.badge.img+4

Hey thanks for listening. I have been using Google play billing library since past 2 years and now switching to Revenue cat. I have few questions regarding migrating subscribers of my app.

 

So there are two types of subscribers 1. monthly and 2. annual subscribers. I have saved their data in firebase realtime database and nowhere else.


Your docs were really helpful in integrating the Purchase SDK of RevenueCat but what i am not able to understand is about migrating these active subscribers (around 20).

 

  1. Won’t the RevenueCat automatically be able to communicate with Google Play Servers and check if a user is premium user and active?
  2. If not and if i have to manually update the data (which is incomplete as i don’t know about the app_user_id) then what is the best possible way to handle this?

Best answer by sundeep

Hi @Rishabh Jain,

Have you checked out our Migrating Subscriptions doc yet? Could be useful to go over, there’s also a handy flowchart in there that walks you through different options: https://docs.revenuecat.com/docs/migrating-existing-subscriptions


It sounds like you don’t have too many users to migrate over, so if you don’t have very complete data in your own infrastructure, you could try client-side migration where you call syncPurchases if the subscription exists in your old system but not in RevenueCat:
https://docs.revenuecat.com/docs/migrating-existing-subscriptions#client-side-migration

This will create the user in RevenueCat and grant them the appropriate entitlements associated with their purchases.

View original
Did this post help you find an answer to your question?

2 replies

sundeep
RevenueCat Staff
Forum|alt.badge.img+8
  • sundeep
  • RevenueCat Staff
  • 138 replies
  • Answer
  • October 18, 2021

Hi @Rishabh Jain,

Have you checked out our Migrating Subscriptions doc yet? Could be useful to go over, there’s also a handy flowchart in there that walks you through different options: https://docs.revenuecat.com/docs/migrating-existing-subscriptions


It sounds like you don’t have too many users to migrate over, so if you don’t have very complete data in your own infrastructure, you could try client-side migration where you call syncPurchases if the subscription exists in your old system but not in RevenueCat:
https://docs.revenuecat.com/docs/migrating-existing-subscriptions#client-side-migration

This will create the user in RevenueCat and grant them the appropriate entitlements associated with their purchases.

G
Forum|alt.badge.img+4
  • Giovanni
  • New Member
  • 3 replies
  • April 27, 2022
sundeep wrote:

Hi @Rishabh Jain,

Have you checked out our Migrating Subscriptions doc yet? Could be useful to go over, there’s also a handy flowchart in there that walks you through different options: https://docs.revenuecat.com/docs/migrating-existing-subscriptions


It sounds like you don’t have too many users to migrate over, so if you don’t have very complete data in your own infrastructure, you could try client-side migration where you call syncPurchases if the subscription exists in your old system but not in RevenueCat:
https://docs.revenuecat.com/docs/migrating-existing-subscriptions#client-side-migration

This will create the user in RevenueCat and grant them the appropriate entitlements associated with their purchases.

Hi there.

I have the same question, but I have about 100 users. I also have their tokens but not the app_user_id. 

The difference is that I’m also migrating from Java to Flutter, so it is complicated for me to understand the documentation.

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings