What actually moves when you transfer an app.
Apps change hands more often than you’d think. Someone sells a side project, an agency hands a finished app to its client, or a solo developer finally moves everything from a personal account to a company one. Both stores have a built-in transfer for this, and the store page itself moves in a day or two. What doesn’t move is the part that bites, and a couple of those things can only be handled before you press the button.
What both stores carry across
The good news first: a transfer is not a re-listing. On the App Store, Apple says the app keeps its reviews and ratings during and after the transfer, and existing users keep receiving updates. The bundle ID goes with it (it can’t change once a build has been uploaded anyway), and so does the App ID. If the old owner used a wildcard App ID, Apple converts it to an explicit one that matches the bundle ID.
Google Play is broader. Its help page says it moves “all users, statistics, data, comments, ratings, subscriptions, and related app information” to the new account, including download statistics, content ratings, the store listing and the policy declarations you filled in on the App content page. Your package name, your install base and your rating all survive.
Neither store requires you to pull the app from sale. Users never see that anything happened, except for the seller name on the listing.
What stays with the old owner
Money and history mostly stay where they were earned. On Apple’s side, the original owner keeps the payment and sales records from before the transfer, and the new owner only sees transactions from after it. The original owner can still look at historical numbers in Sales and Trends but loses App Analytics for the app. Google draws the same line: orders created before the transfer remain in the original account, so refunds for those orders have to go through that account. Earnings reports, estimated sales reports and bulk exports don’t move at all. If you’re selling, download them first. If you’re buying, ask for them, because they’re your only proof of what the app actually earned.
A few other things are left behind or reset:
- Test tracks. On Play, internal, closed and open testing groups and internal sharing don’t transfer, so testers may need to opt in again. Apple goes further: you have to switch TestFlight off before starting, by removing every build and tester and clearing the test information fields in every localization.
- Game Center. Apps in a Game Center group are removed from it, leaderboards and achievements revert to their original status, and matchmaking configuration isn’t transferred.
- Apple Pay. The merchant ID stays with the old account.
- Promotions on Play. They don’t move, though promo codes already issued keep working.
- Connected services. Google is explicit that permissions and linkage for integrated services don’t follow the app. Firebase projects need unlinking from the old account and linking to the new one, Google Cloud projects (Play Games Services included) need the new account added as an Owner, and ad SDKs like AdMob need updating so ad revenue is credited to the new owner.
Apple’s checklist before it will even start
App Store Connect checks eligibility when you begin, and the transfer simply won’t start until every item passes. Both accounts must be in a settled state (not pending or changing) and both must have accepted the latest paid and free apps agreements. Beyond that, Apple lists these conditions:
- At least one version of the app has been released on the App Store.
- The app isn’t on pre-order in any country or region.
- No version is mid-pipeline: Waiting for Review, In Review, Accepted, Pending Developer Release, Pending Apple Release or Processing for Distribution all block it.
- Every in-app purchase is Approved, Ready to Submit, Developer Removed from Sale or Rejected.
- None of the app’s in-app purchase product IDs match product IDs on any app the recipient already owns.
- It isn’t an Apple Arcade app, or a sandboxed Mac app sharing an app group container with other Mac apps.
The product ID rule is the one that catches agencies. If you build several apps for one client from a shared template and every one of them sells premium_monthly, the second transfer into that client’s account will be refused. Prefix product IDs with the bundle ID from day one and it never comes up.
Once started, the recipient has 60 days to accept. After acceptance, Apple says the transfer can take up to two business days, and during that time the app shows Processing App Transfer: metadata, pricing, rights and in-app purchases are locked, and any open App Review thread is closed. Don’t start a transfer the week you need to ship a fix. Afterwards, the new owner has to create fresh provisioning profiles in their own account before uploading a build.
Sign in with Apple is the step you can’t redo
Everything above is paperwork. This one can lose you users. The user identifier Sign in with Apple gives your app is scoped to the developer team. When the app moves to a new team, the same person gets a different identifier, and your backend has no way to know that the “new” user is someone who already has an account and a purchase history.
Apple provides a migration path, and it has to be started by the old owner. Before the transfer, the original team asks Apple for a transfer identifier for each of its users, scoped to the recipient team, and stores it alongside the user record. After the transfer, the new team exchanges each transfer identifier for its own team-scoped identifier and updates its database. Apple’s migration tooling only stays available for 60 days after the transfer completes, and users who sign in during that window come through with the transfer identifier in their token so they can be matched.
If the old owner never generated those identifiers, or the new owner doesn’t finish within the window, existing Sign in with Apple users can end up looking like strangers: a fresh empty account, no saved data, a paid subscription that seems to belong to nobody. Apple’s developer forums have a run of threads from teams asking how to recover users after skipping this step, and none of them gets an easy answer. If your app offers Sign in with Apple (and plenty of apps have to), put the migration in the sale agreement as a named deliverable with a date.
Subscriptions need one smaller piece of handover too. Apple advises the original owner to generate an app-specific shared secret before the transfer and give it to the recipient, who generates a new one afterwards so people outside their organization no longer hold it.
Google’s side: two transaction IDs and a form
Play transfers are requested through a form in Play Console rather than a button on the app. Both accounts must be registered and active, and if the app is paid or sells in-app products, the receiving account needs an active payments profile. The odd requirement is the registration transaction ID for both accounts, the receipt from the one-off developer registration fee, with its prefix removed. If you registered years ago, finding it in your Google payments history is usually the slowest part of the whole process. Google says support reviews and responds within two business days.
Two details are easy to miss. Signing keys don’t change, so if the new owner doesn’t want to rely on keys the seller once held, they can request a new upload key, or a new signing key for new installs through a key upgrade. And if the receiving account’s default currency is different, Google unpublishes apps whose only paid content is in-app purchases until the new owner publishes again. Paid apps have their prices converted automatically.
The listing comes along, the source files don’t
The store page arrives intact on both platforms, but the files behind it usually don’t. The new owner gets the published screenshots, not the design files they came from, so the first update that changes a screen means rebuilding the set from scratch. If you’re buying, ask for those along with the reports. If they don’t exist, rebuild the set once, in a tool your account owns, and the next transfer won’t have this problem.