Hey @Jerry Seigle, welcome!
Doing a server-side import of your data is not required, but it does have benefits. If you’re unable to get the data exported from Nami, don’t worry you can still start to migrate things over client-side. I’ll try to explain the differences below.
Pre-read: https://docs.revenuecat.com/docs/migrating-existing-subscriptions
Client-side migration:
This is essentially syncing the purchases from the device the first time one of your customers opens the next version of your app containing RevenueCat. The main drawback with this approach is you’ll never know for sure if all of your subscribers have actually been migrated. For example, if you have 400 active subscribers, the truth is maybe 10 don’t open the app for months or years (or never). Those subscribers never show up in RevenueCat.
The impact this has is mostly all on the analytics side. Charts and Lists will show a lower number of subscribers and revenue than you actually have. However, it should not impact subscription status at all, since the customers that have not been migrated aren’t using RevenueCat for subscription status (they’ll still be on your old system). This does mean though that you should keep the old system around for these customers.
Server-side migration:
This is almost always the preferred option, if possible. I would hope Nami would allow you to export the iOS receipts and Android purchase tokens if you’re closing down your account. With a server-side migration you know for sure that all of your subscribers are in RevenueCat. The main benefits here are improved analytics in a single place, you can completely shut down the old system, and you don’t have any migration code in your app which could mean less chance for bugs.
The route you choose is up to you. I did a client-side migration with one of my apps because I didn’t have receipts and things are fine.
Last question If I have to import something (I only have 400 active users) how long would the import process take before everything is reflected in RevenueCat
If you’re doing a server-side migration, I’d write a little script that hits our POST /receipt API and you’d be migrated in 400 API calls (very quick). We do bulk imports manually on our end but our queue is pretty backed up right now as we’re running some really large imports.