App Transfer Between Developer Accounts
Moving an app to another company means two different processes, one per store, each with its own trap. We run both, and relink what breaks afterwards.
Moving an app to another company means two different processes, one per store, each with its own trap. We run both, and relink what breaks afterwards.
We transfer apps between developer accounts on Google Play and the App Store. Usually because a product is changing hands: an acquisition, a founder handing an app to a company, or an agency passing an app back to its owner.
We have run this for client apps, and the two stores fail in opposite ways. Google gates on paperwork. Apple gates on the state of the app.
Finding one number. Google asks for the registration transaction ID of both accounts: the order ID from the $25 payment made when each account was created, with its prefix stripped. For an account set up years ago, finding it is most of the job. Google then reviews the request within two business days.
Our Google Play transfer guide covers where that number hides.
Taking things apart first. Apple will not start a transfer until TestFlight is fully torn down in every localisation, Xcode Cloud data is removed, nothing is mid-review, and no In-App Purchase ID clashes with the receiving account. The receiving side then has 60 days to accept.
Our App Store transfer guide lists everything that blocks it.
The parts users can see. Reviews, ratings, the install base and the app's identity carry over on both stores, and the app stays on sale throughout.
A few days to a few weeks. It depends mostly on how quickly old account records can be found and how fast the receiving side accepts.
It is quoted after a short call, once we know which stores are involved and whether the app uses subscriptions, Sign in with Apple or shared iCloud data, which are the parts that add work.