Back to all posts
Google Play7 min read·November 1, 2026

How to Transfer an App to Another Google Play Developer Account

TB
ThynkBlox Apps Team
App Engineering

To transfer an app to another Google Play developer account, prepare both accounts and submit a transfer request through Google Play’s official process. The receiving account owner must approve it before Google reviews it. Treat the move as a handover of the whole product: store ownership, subscriptions, signing, connected services and support responsibilities.

Use the official app transfer requirements alongside this checklist. Assign someone to each part of the handover before submitting the request.

What should you check before requesting the transfer?

Both developer accounts must be registered and active, and the transfer must meet Google Play’s policy requirements. Have both registration transaction IDs ready. For paid apps or in-app products, the receiving account needs an active payments profile. These requirements are set out in the official transfer guide.

Ask the receiving owner to confirm readiness from inside their account. Do not rely solely on an invitation email or a screenshot supplied earlier.

Prepare a handover record containing:

  • The app being transferred and the intended receiving account.
  • The people authorised to approve the move.
  • Open policy questions and who will resolve them.
  • Payment, subscription and refund responsibilities.
  • Connected services and the person responsible for each.
  • The checks required before removing the outgoing team’s access.

If ownership is still undecided, settle that first. Our guide to who should own the Google Play developer account covers that decision.

What moves with the app, and what needs separate work?

Google Play transfers the listing, users, statistics, ratings, reviews and subscriptions. Orders created before the transfer stay with the original account, and earnings and sales reports, promotions and testing groups do not transfer; download the reports you need first. Connected-service permissions and links need separate attention. See Google Play’s transfer details.

Use the following table to divide the work:

AreaHandover actionEvidence to collect
Store listingCompare the public listing before and afterListing details and screenshots
SubscriptionsCheck existing subscriber access and purchase handlingResults from controlled checks
Historical ordersAgree who handles earlier purchases and refundsA documented support route
Financial recordsDownload reports needed for reconciliationAccessible copies held by the right owner
SigningConfirm how the receiving team will sign uploadsA successful release preparation check
Connected servicesReview ownership, billing and permissions separatelyAccess confirmed by the receiving team
TestingPrepare the required tester access againTesters can reach the intended release

Keep this record practical. Each row should name a person and a completion check, rather than simply saying “transferred”.

How should you protect subscriptions and purchases?

Although subscriptions transfer, do not treat that as proof that every paid feature works. Historical-order refunds require access through the original account or the developer API, according to the transfer guide.

Plan separate checks for an existing subscriber and a new customer. Confirm that the app recognises an existing entitlement after sign-in and after reinstalling. Check restoration, purchase confirmation and cancellation handling where your product supports them.

Ask the person responsible for billing to trace a purchase through to the access it grants. A successful payment screen alone should not close this check.

Also compare default currencies. Google Play says that if the receiving account uses a different default currency, an app with in-app products is unpublished after the transfer until the owner checks the updated prices and republishes it. Paid-app prices are updated to the new default currency automatically. Review the currency conditions before scheduling the move.

Agree who will answer billing questions during the handover. Avoid asking subscribers to cancel and buy again as a substitute for checking continuity.

What must happen to signing keys?

First establish whether the app uses Play App Signing or a signing key managed by the developer.

With Play App Signing, the upload key signs the bundle you submit, while Google holds the key used to sign the app delivered to users. Google documents upload-key resets separately from signing-key upgrades in its signing guidance.

Ask the receiving team to confirm:

  • Who controls the upload key and its recovery arrangements.
  • Whether the outgoing team should retain any signing access.
  • Whether a reset or upgrade is needed for a specific security reason.
  • Which connected services rely on signing-certificate fingerprints.
  • How the next update will be prepared and checked.

For a developer-managed signing key, include secure custody and recovery in the handover. Do not leave essential access tied to someone’s personal device.

Google’s signing documentation explains certificate registration for connected APIs. Review those registrations when changing signing arrangements. Our guide to app signing key and upload key ownership explains the ownership questions in more detail.

How do you hand over backend access and analytics?

Create a service inventory separate from the store checklist. Include sign-in, databases, file storage, notifications, subscription processing, analytics, crash reporting, domains and customer support.

For each service, record who can administer it, who pays for it, how access is recovered and how the receiving team will prove it works. Prefer adding and verifying the new owner before removing the previous owner.

For Google Play Developer API access, grant the service account the permissions it needs in Play Console. An app's developer ID changes when it moves accounts, so where an API call uses the developer ID, the new account’s ID must be used after transfer. The official API setup guide explains these requirements.

Ask the technical team to test purchase validation and any automated publishing or order-management connections under the receiving account’s permissions.

For analytics, request access to the existing reporting history and check that fresh events arrive. Use a recognisable test journey: open the app, sign in and complete a key action. Compare what happened with what appeared in reporting.

Our guide to verifying mobile app analytics events provides a useful check sequence. Avoid replacing a working analytics setup during the transfer unless there is a separate reason to do so.

How should you coordinate the transfer?

Choose a period when both owners and the people responsible for billing and connected services are available.

Before submitting:

  • Save the listing details and required reports.
  • Record the current app version and key user journeys.
  • Confirm receiving-team access to connected services.
  • Prepare signing and subscription checks.
  • Agree who handles problems and customer questions.

Submit through the official process after completing the prerequisites. Avoid combining the move with a redesign, backend migration or major pricing change. Keeping the scope narrow makes unexpected behaviour easier to investigate.

Do not promise customers an interruption-free transfer. Base any notice on the changes they will actually experience, such as a new support contact or an expected availability gap.

What should you verify after the transfer?

Check the public store page and the app itself. Console ownership is only one acceptance condition.

Use this completion checklist:

  • The intended owner can administer the app.
  • The listing, screenshots and support details are correct.
  • An existing installation opens and signs in.
  • A fresh installation completes onboarding.
  • Existing subscriber access is recognised.
  • Purchase handling and restoration work as intended.
  • Notifications and important links behave correctly.
  • Analytics events and crash reports reach the intended accounts.
  • The receiving team can prepare the next update.
  • Historical-order support remains available.

Use our Android release testing guide to choose representative journeys. Remove outgoing access only after the receiving team has demonstrated that it can operate and maintain the app.

Which common mistakes should you avoid?

Closing the original account too early. Resolve historical records and refund responsibilities first.

Assuming store ownership covers connected services. Require separate evidence for backend, analytics and billing access.

Changing keys without a clear reason. Review signing requirements and connected-service registrations before making changes.

Testing only new customers. Include someone who already has an account, saved data or a subscription.

Calling the handover complete before checking updates. Include the ability to maintain the app in your acceptance criteria.

What else do owners ask about app transfers?

Is sharing a login enough?

Use the formal transfer process when moving the app between developer accounts. Set up named access for the receiving team so responsibility is clear.

Should the app be rebuilt before moving it?

Keep rebuilding as a separate decision. First establish whether the existing app can be transferred, operated and updated safely. A change of owner alone is not a reason to redesign the product.

When is the transfer complete?

Close the handover when the store move is confirmed, connected services are accessible, customer journeys pass and the receiving team can publish future updates.

For help coordinating the account and product handover, contact us.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.