How to transfer app ownership on Google Play
In short
To transfer app ownership on Google Play, the seller submits a transfer request from their Play Console developer account, giving the buyer's account details and registration transaction ID, and the buyer approves it. Google's support team responds within two business days of the approval. Users, ratings, reviews and subscriptions move. Earnings reports and old orders do not.
Can you transfer an app to another Google Play developer account?
Yes. Google supports it directly, and its Play Console help has a page called "Transfer apps to a different developer account". When you transfer app ownership on Google Play, the app moves from the seller's developer account (Google calls it the original account) to the buyer's (the target account). The developer account itself stays with whoever opened it. The buyer needs their own.
That is the right shape for a sale. The buyer ends up with the app in an account that has their identity, their payments profile and their history, and nothing of the seller's.
What do both accounts need before you start?
Google lists three conditions:
- Both the original and the target developer account are registered and active.
- Both accounts, and every app being transferred, comply with Google Play policies.
- If the app is paid or sells in-app products, the target account has an active payments profile.
A buyer without a developer account has to open one first. Google charges a US$25 registration fee for a new account. The buyer should also check that their account has finished registration and is not showing a "Why can't I publish" message, because Google asks for that before a transfer.
What should the seller do first?
Download the reports. Google is clear that bulk export reports, payout reports and earnings reports do not transfer, so anything the seller needs for their own books, and anything the buyer was promised as evidence, has to be exported before the request goes in. Google also asks the seller to review policy compliance and their service fee tier, and to confirm they can sign in to the original account.
If translation projects are in progress, finish them before the transfer.
How do you transfer app ownership on Google Play?
- The buyer finds the registration transaction ID for their developer account. Google says it is usually in the "developer registration fee" email or in Google Payments activity, and that any prefix should be removed before it is submitted.
- The buyer sends the seller that ID and their developer account details.
- The seller signs in to the original account and submits the transfer request through the app transfer page in Play Console, naming the apps to move.
- The buyer reviews the request in the target account and approves it.
- Google's support team reviews the request. Google says it responds within two business days once the target account owner has approved.
Google's help page has the link to the request form and the current wording of each field. Use it as you go, because the form is the part most likely to change.
What moves with the app and what does not?
| Moves with the app | Does not move |
|---|---|
| Users and download statistics | Bulk export, estimated sales and earnings reports |
| Ratings, reviews and comments | Orders created before the transfer, which stay in the original account |
| Content ratings and store listing information | Promotions, although promo codes already issued still work |
| Subscriptions | Test groups, which have to be set up again |
| App content policy declarations already submitted | Permissions and links to integrated services |
The last row is where most of the buyer's work sits. Google says integrated services have to be updated by hand: add the target account to the Google Analytics and Google Cloud projects, unlink Firebase projects from the original account and link them to the target, and update ad SDK integrations in the app. For Game Services projects, Google says to contact support.
What are the special cases to check?
Paid apps and in-app products. If the target account uses a different default currency, Google updates paid app prices automatically. An app that only sells in-app purchases is unpublished after the transfer and has to be republished once prices are checked. Plan that gap, and tell the buyer about it before it happens, not after.
Signing keys. With Play App Signing, the new owner can request a new upload key, and can request a new app signing key for new installs through a key upgrade. The buyer should do the first of those early, so the seller's upload key stops being a way into the app.
Service fees. Google notes that where the 15% service fee tier applies, a transferred app's full earnings for the calendar year count towards the total for each Account Group involved. If the app earns meaningful money, both sides should read that part of Google's page and ask Google about anything unclear.
Private apps. For managed Google Play private apps, the target account has to be associated with the organisation, and private apps created with the managed Google Play iFrame cannot be transferred.
What should you do before and after in a business sale?
Run the transfer inside escrow. On Indiemaker, payment and handover go through Escrow.com, and the buyer's money is held until the transfer is done. The order that protects both sides: funds confirmed as held, seller submits the request, buyer approves, Google completes it, buyer confirms the app is in their Play Console and that they can upload a release. How escrow works covers who confirms what.
Before the request, the buyer should have the earnings reports they were shown during due diligence saved as files, because those reports will not be in their account later.
After the transfer, the buyer works through the linked services one at a time: Firebase, Google Cloud, Analytics, ad networks, and the backend the app talks to. The Play transfer does not touch servers, databases or the code repository. Those follow the wider sequence in how to hand over a software business, and the full list of moving parts belongs in a stack transfer checklist. Rotate every key and password once each service is in the buyer's name.
Keep the seller reachable until the buyer has shipped one update on their own. If the seller later closes the original account, Google says its support team can refund that account's registration fee. If the app also ships on iOS, the process is different: see moving an app between Apple developer accounts.
Sources
- Transfer apps to a different developer account - checked 17 November 2026
Related: transfer/apple-developer-app, how-to-hand-over-a-saas-business, stack-transfer, how-escrow-works-on-a-six-figure-transfer
When you are ready to read real listings.
Everything on sale, on the same fields, from $1,000 to $500,000.