Hey @airntufts,
As long as your app’s bundle ID (Apple) or package name (Google) and in-app product identifiers stay the same, RevenueCat will keep managing your subscriptions without interruption, even as you migrate developer accounts.
As you mentioned, Apple lets you convert an individual developer account to a business one. If your app remains in the same account (just upgraded), it’s usually seamless:
- your bundle ID stays the same
- you may need to regenerate App Store Connect credentials (API key, shared secret, in-app purchase key)
- update these credentials in RevenueCat after conversion
- no need to update webhooks or user data if your RevenueCat project is unchanged
NOTE: If you transferred your app to a new Apple Developer Account completly, you would need to regenerate and re-upload your credentials to RevenueCat. These are the app-specific shared secret, the in-app purchase key, and the App Store Connect API key. Also, you’d want to make sure the Paid Applications Agreement is signed with Apple on the new account.
One thing you can do ahead of time, if you want to double-check before updating your production project, is to create a second RevenueCat app and plug in the new credentials. This way you can validate that purchases work without regressing.
Google requires you to transfer apps from your personal to business account, which is a bit more involved:
- create new service account credentials (JSON key) under the new business account
- upload these new credentials to RevenueCat after the transfer
- either transfer your Google Cloud project or make sure the RevenueCat service account is correctly authorized in the new Play Console (API access, financial data permissions)
- allow up to 36 hours for new credentials to propagate. During this time:
- users can still access existing purchases
- new purchases may temporarily fail until credentials go live
Once more, something to consider and to make sure everything is up and running before turning on the switch, is to use a temporary RevenueCat project to test your new Play Console setup before updating your live app. That way, you can catch any issues before impacting production.
And as to some final checks:
- confirm credentials are updated in RevenueCat after the transfer;
- use
restorePurchases() or syncPurchases() (as appropriate and based on the Restore Behavior and Restoring Purchases) in a test build to verify everything’s working - monitor logs in RevenueCat for any failed events;
- test with sandbox/test accounts to be extra safe.
Best,
