If you have apps that you want to transfer to a different Google Play Developer account, you can submit a transfer request after reviewing the instructions below.
Get your app ready to transfer
For all developers:
The original account and all apps being transferred must comply with all policy guidelines.
For developers enrolled in the 15% service fee tier:
When an app is transferred between developer accounts in separate account groups, all of the app’s earnings will be included in each account group’s total earnings for that calendar year.
For example, if a developer account in account group A has an app that has earned $100,000 (USD) in earnings this year that is then transferred to another developer account in account group B, the $100,000 (USD) earnings will be included on both account group A and account group B’s total earnings for purposes of calculating the first $1 million (USD) in earnings for this year.
When you transfer apps to a different account, your apps’ users, download statistics, ratings and reviews, content ratings and store listing information are all transferred to your new account.Your bulk export reports, payout reports and earnings reports won't transfer with the app, so you may want to download any reports that you'll need later. New versions of these reports will be created once the app transfers to a new account.
Before you can submit a transfer request from your original account to a different account (known as your target account), both Google Play Developer accounts need to be registered and active.
To confirm that an account is active, make sure that:
- Original account: You're able to sign in.
- Target account: Your registration is complete. If you see the message 'Why can't I publish' in the app header, review the information provided to resolve any missing information.
Note: If you create a new target account, you need to pay a $25 USD registration fee. After the transfer is complete, if you want to close your original account, our support team can refund the registration fee for that account.
You'll need the registration transaction ID for the target account. To find the transaction ID, search the target account owner's email inbox for 'developer registration fee'.
If you can’t find the transaction ID email receipt:
- With the target account owner's email address, sign in to Google Payments.
- At the left menu, select Activity.
- Find and select the transaction for your developer account registration.
- Tip: Search your transactions for 'Google Play Developer'.
- Your transaction ID is listed near the bottom of the transaction details.
Registration transactions IDs are typically in one of the following formats:
Additional requirements for select apps
For apps using Play app signing, both the original owner and target account may wish to consider the security of both the upload key and the app signing key.
- Upload key: If there is a concern using the same upload key before and after the transfer, the target account can request a new upload key as per the instructions outlined under 'Lost or compromised upload key?'
- App signing key: If there is a concern using the same app signing key before and after the transfer, the target account can request a new signing key via key upgrade for new installs. Google Play would then use the new key to sign new installs and app updates. There are some important considerations before requesting a key upgrade. Instructions can be found under 'Upgrade your app signing key for new installs'.
If you're transferring paid apps or apps with in-app products, your target account needs to have an active payments profile.
If you're using a different default currency on your target account, here are two conditions that apply to your transfer:
- In-app purchases only: You need to add a price in the new default currency for each in-app product. After your app is transferred to your target account, the app will be unpublished until you publish it again. Once you've verified the new prices on your target account, publish the app again.
- Paid apps: Default currency changes will be automatically applied to app prices.
Tip: If you're only transferring free apps and have completed the previous steps, move on to the next step.
If your app uses any integrated services, including Google Analytics, Firebase and Google Play game services, make sure that you update your account settings and apps.
- Google Analytics: Add permissions for your target account to your Google Analytics account.
- Google Developers Console projects: Add your target account as an owner for your Google Developers Console projects. These projects can include Google+ sign-in, Google Play game services and other Google APIs.
- Firebase projects: Unlink any Firebase projects from the original Play Console account and link the projects to the target account.
- Ad SDK integrations (including AdMob): Once your apps have been transferred to your target account, to make sure that ad traffic is credited to the correct account, all ad SDK integrations will need to be updated in your apps' APK files.
- APK translations: If you have any translation projects in progress using Google Play's translation service, they need to be completed before your app(s) can be transferred.
- Managed Google Play: To transfer a private app, make sure that the account to which you want to transfer your app is associated with your organisation. Before the transfer can be completed, you'll need to temporarily unpublish your app and remove organisation restrictions. Our support team will work with you to minimise the time that your app isn't visible. Existing users will still be able to use and reinstall the app during the transfer process.
Tip: If you need help transferring a game services project, contact our support team.
Submit your transfer request
After you've completed the steps above, you're ready to submit your transfer request. Our support team reviews and replies to transfer requests within two working days.