This guide explains how Google Play developers can transfer apps to a different Google Play developer account. Before submitting a transfer request, make sure both the original target accounts are registered and active, compliant with all Google Play policy guidelines, and configured with an active payments profile if transferring paid apps or apps with in-app products.
Prepare your app for 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, Google Play transfers your apps' users, download statistics, ratings and reviews, content ratings, and store listing information to your new account.
Bulk export reports, payout reports, and earnings reports do not transfer with the app, so download any reports you need before starting the transfer. Google Play creates new versions of these reports after the app transfers to the new account.
Before you submit a transfer request from your original account to a target account, both Google Play developer accounts must be registered and active.
To confirm an account is active, check the following criteria:
- Original account: You can sign in to the account.
- Target account: Your registration is complete. If the app header displays the message "Why can't I publish," review the provided details to resolve missing information.
Note: Creating a new target account requires a US$25 registration fee. After the transfer is complete, if you want to close your original account, support can refund the registration fee for the original account.
You need the registration transaction ID for both the original account and the target account. To find the transaction ID, search the target account owner's email inbox for "developer registration fee."
If you can't locate the transaction ID email receipt, follow these steps:
- Using the target account owner's email address, sign in to Google Payments.
- In the left menu, select Activity.
- Find and select the registration transaction for your developer account.
Tip: Search your transactions for “Google Play Developer.”
- Locate your transaction ID near the bottom of the transaction details.
Registration transaction IDs typically use one of the following formats:
01234567890123456789.token.01234567890123450.G.123456789012345Registration-1234ab56-7c89-12d3-4567-8e91234567f8PDS.1234-5678-9012-3456
0.G. or the characters before token or Registration).Additional requirements for select apps
For apps using Play App Signing, evaluate the security of both the upload key and the app signing key.
- Upload key: If you have security concerns about using the same upload key before and after the transfer, the target account owner can request a new upload key. For instructions, see the Request an upload key reset section of "Use Play App Signing."
- App signing key: If you have security concerns about using the same app signing key before and after the transfer, the target account owner can request a new signing key through a key upgrade for new installs. Google Play then uses the new key to sign new installs and app updates. Review key considerations before requesting an upgrade. For instructions, see the Upgrade your app signing key for new installs section of "Use Play App Signing."
If you transfer paid apps or apps with in-app products, your target account must have an active payments profile.
If the target account uses a different default currency, Google Play automatically applies default currency updates:
- In-app purchases only: After the transfer completes, Google Play unpublishes the app until you publish it again. Verify the updated prices on your target account, then publish the app again.
- Paid apps: Google Play automatically applies default currency updates to app prices.
Tip: If you're only transferring free apps and have completed the previous steps, proceed to the next section.
If your app uses integrated services, such as Google Analytics, Firebase, or Google Play Game Services, update your account settings and apps:
- Google Analytics: Add permissions for your target account in your Google Analytics account.
- Google Cloud Console projects: Add your target account as an Owner for your Google Cloud Console projects. These projects can include Google Play Game Services and other Google APIs.
- Firebase projects: Unlink Firebase projects from the original Play Console account and link them to the target account.
- Ad SDK integrations (including AdMob): After transferring your apps, update all ad SDK integrations in your APK files to make sure ad traffic attributes correctly to the target account.
- APK translations: Complete any in-progress translation projects using Google Play translation services before transferring your app.
- Managed Google Play: To transfer a private app, make sure the target developer account associates with your organization. Before completing the transfer, temporarily unpublish your app and remove organization restrictions. Support works with you to minimize app downtime. Existing users can continue using and reinstalling the app during the transfer process.
Note: You cannot transfer private apps created with the managed Google Play iFrame to a different developer account.
Tip: If you need help transferring a Game Services project, contact support.
Data and settings transferred with your app
When you transfer an app, Google Play transfers or retains data according to these rules:
- Google Play transfers all users, statistics, data, comments, ratings, subscriptions, and related app information to the target account.
- Orders created before the app transfer remain in the original account. To refund these orders, access the original account or use the Google Play Developer API.
- Bulk export reports, estimated sales reports, and earnings reports do not transfer to the target account.
- Promotions do not transfer to the target account, but previously issued promo codes continue to work.
- Test groups (open, closed, internal test, and internal sharing) do not transfer between accounts. Recreate any closed testing groups in the target account. Testers may need to opt in to the test again.
- Permissions and linkage settings for integrated services do not transfer automatically. Update your account settings and apps manually.
- Google Play transfers any documentation and information you previously submitted to the new developer account, including policy declaration submissions provided on the App content page (Monitor and improve > Policy and programs > App content).
Submit your transfer request
After completing all prerequisite steps, submit your transfer request. The target developer account owner receives the request to review and approve. After approval, support reviews and responds to transfer requests within two business days.
Related content
- Learn more about managing your developer account in the Academy for App Success.