Google Play Developer Account Transfer: What Actually Moves

Google Play has two transfer paths, and they are not interchangeable. The account owner switch moves an entire developer account to a different person. The app transfer moves individual apps between accounts. Since the Account Transfer policy introduced in Google's 15 April 2026 announcement, the owner switch is the only sanctioned way to change who owns an account, and it is closed to one large group: individual developers who monetise their apps. Those developers must use the app transfer route instead, which moves the app but not the test groups attached to it.

That single eligibility rule decides the rest of the process, including how long it takes, what survives, and whether the transfer can start at all. Below is what each route does, what Google moves and does not move, and the conditions that block a transfer after you have already begun.

Which of the two transfers do you actually need?

Ask two questions before you open Play Console. Is the account registered to an organisation or to an individual, and does it earn money? The account type already shapes other Play requirements, and the difference between organisation and personal accounts is worth settling before a transfer, because converting between the two is itself a change that blocks one. Google's help page answers the rest directly: "Developers with organization accounts or non-monetizing personal accounts may switch account owners, provided they submit all required information and successfully complete the necessary identity verifications."

The same page closes the door on everyone else with a sentence that most third-party guides skip: "Individual developers who monetize their apps are currently ineligible for this direct transfer process. Instead, you must create a new developer account and transfer your existing apps to it."

Account type	Owner switch	What to do instead
Organisation	Available. Same-entity transfers can reuse existing account information; a different entity selects its own Google payments profile for identity verification.	Nothing, if the payment profile admins grant the new owner admin access first.
Individual, no paid apps or in-app purchases	Available. The prospective owner creates or selects a payment profile, used for identity verification only.	Nothing. Follow the five steps in the next section.
Individual, monetising	Not available	Create a new developer account and transfer each app to it. Test groups have to be rebuilt.

The third row is the common case for a solo developer selling an app or handing it to a co-founder, and it is the row where expectations break. You are not switching owners; you are moving apps one at a time into a second account that you register and pay for yourself. The registration fee and verification timeline applies to that second account in full, including identity checks.

Route	What you do first	The wait	How it finishes
Owner switch Organisation, or personal without revenue	Payment profile admin access, then Make account owner	Seven-day security hold, cancellable by any user on the account	The new owner completes the setup wizard and identity checks
App transfer Personal with revenue, or a single app	Both accounts active and compliant, transaction IDs to hand	Target owner approves, then Google support reviews the request	Support responds within two business days

The owner switch, in the order Play Console asks for it

Only the account owner can start this. Team members with admin rights cannot initiate it on the owner's behalf, and the help page does not describe an exception.

1. Fix the payment profile access first. For an organisation transfer, the prospective owner must already have admin access to the payment profiles used for identity verification or merchant monetisation, granted in the Google Payments Center. Until that happens, Play Console will list the profiles and refuse to continue.
2. Open Users and permissions in Play Console, find the team member who will take over, select Manage, then Make account owner. The person must already be a user on the account; there is no way to invite an outsider inside this step.
3. Choose the relationship to the entity for organisation accounts, or create a payment profile for an individual account. This is where the transfer is priced in time rather than money: the new owner goes through the same identity checks as a new registrant.
4. Submit, then wait out the hold. The current owner and every admin with access to all apps receive a confirmation email, and all team members get a Play Console notification. The transfer sits for seven days.
5. Complete the invitation. After the hold, the prospective owner receives an email link to a setup wizard covering payment profile, organisation details, contact verification by one-time password, developer contact details, and identity documents if Google asks for them.

If the current owner is unreachable, the self-serve path is closed. Google states that developers who have lost owner access "are not able to complete the self-serve process at the current time" and must go through Play Console support or the online form.

The seven-day hold is a security control, not a queue

The hold exists because an ownership transfer is the highest-value action on a developer account. Google's own explanation is explicit: it protects against account hijacking by giving the legitimate owner a window to contact support. Two details follow from that design and matter operationally.

During the hold, any user on the account can cancel the request from the Users and permissions page, not only the owner. Once the prospective owner begins the final setup, nobody else can cancel it. So the practical rule is to tell the whole team before you click submit, because a colleague who assumes the request is fraudulent can stop it without asking you.

Google also lists the conditions that block a switch outright:

• Account non-compliance: outstanding verification requirements, or an account not in good standing. If the account is already in enforcement, the appeal route has to be resolved before any transfer can be considered.
• A concurrent account change: a pending change to the Google payments profile, a transition between account types such as individual to organisation, a pending upload key reset, or an app transfer already in progress.
• A conflict on the receiving side: the prospective owner already owns a separate Play Console account.

That second bullet is the one that catches teams mid-migration. If you have just requested an upload key reset, or you are converting a personal account to an organisation, the owner switch will not start until that change settles. Sequence the work instead of doing it all in one week.

The app transfer route: what moves and what does not

App transfers are a support-mediated process, not a self-serve switch. Both accounts must be registered, active and compliant with Play policy, and if the app is paid or sells in-app products the receiving account needs an active payments profile. You need the registration transaction ID for both accounts, and creating the target account costs the standard US$25 registration fee. Google says support reviews and responds to transfer requests within two business days after the target owner approves.

What survives the move is generous, which is why a transfer is worth doing properly rather than recreating the listing:

Moves with the app	Stays behind or is lost
Users and install base, download statistics	Test groups of every type: open, closed, internal and internal sharing
Ratings, reviews and comments	Orders placed before the transfer, which stay in the original account
Subscriptions, content ratings and store listing content	Bulk export, payout, estimated sales and earnings reports
Policy declaration submissions from the App content page	Promotions, although promo codes already issued keep working
App-level documentation submitted to Google	Permissions and linkage settings for integrated services

Google's wording on test groups is unambiguous: "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." For anyone with a test running, that is the single most expensive line in the documentation. A 14-day test does not carry across an account boundary, and the testers have to be recruited into the new group afterwards.

The four things that break in an app transfer

Testing state. Recreate the groups and re-invite testers. Nothing in the transfer process preserves an active test, and the target account starts with no tester lists at all.

Money. Revenue reports do not transfer, so download the payout, earnings and bulk export reports you need before you start. Orders from before the transfer stay with the original account, which means refunds for those orders have to be handled there or through the Play Developer API. There is also a service-fee wrinkle: if both accounts sit in the 15% tier but in different account groups, the transferred app's earnings for that calendar year count toward both groups' totals for the first US$1 million calculation.

Pricing and availability. If the receiving account uses a different default currency, Google applies currency updates automatically. For an app that sells in-app products, that currency change unpublishes the app after the transfer until you check the prices and publish it again. Paid apps get their prices updated instead.

Signing and integrations. Play App Signing lets the new owner request an upload key reset, or a signing key upgrade for new installs, if the old key's custody is in doubt. Outside the app itself, Firebase projects must be unlinked from the original account and relinked, Google Cloud projects need the target account added as an owner, and ad SDK integrations including AdMob need updating so traffic attributes to the new account.

Why Google made the official route mandatory

The Account Transfer policy arrived in the 15 April 2026 policy announcement, which framed it as a trust measure: "To ensure a safe and trusted ecosystem, we're introducing the Account Transfer policy to require developers to use the official 'Transfer ownership' workflow within the Play Console." The Q2 2026 Play roundup spelled out the enforcement consequence, stating that all ownership changes must now use this feature and that unofficial methods, such as sharing login credentials or using third-party marketplaces, are no longer permitted.

The reasoning is easy to reconstruct from the mechanics. A shared password leaves no audit trail, no identity check on the new owner, and no way for Google to tell a sale from a hijack. The seven-day hold and the identity verification are what a marketplace listing cannot provide, and they are also why these transfers now take longer than a forum post suggests.

What Google has not documented

Some questions come up whenever this topic is discussed, and Google's pages do not answer them. Treat the following as gaps in the documentation, not as rules:

• Whether an owner switch preserves app-level history the same way an app transfer does. The app transfer page lists exactly what moves. The owner switch page describes account ownership and identity, not app data, so the two routes are documented at different levels of detail.
• Whether a release in review blocks a transfer. The blocker list names a pending upload key reset and an in-progress app transfer. It does not mention review status.
• Whether a monetising personal account ever becomes eligible. The help page says "currently ineligible", which leaves the door ajar without promising anything.
• Whether the seven-day hold can be shortened for urgent business transfers. No exception appears in the documentation, and the security rationale suggests there is not one.
• How long identity verification takes during the setup wizard. The page describes the checks and the document upload, not the turnaround.

A pre-transfer checklist

1. Confirm the account type and whether it monetises. That decides the route before anything else.
2. If monetising on a personal account, register the target account and budget the US$25 fee plus the app-by-app transfer time.
3. Export payout, earnings and bulk reports from the original account. They will not follow the app.
4. Tell every team member the transfer is happening, and who may cancel during the hold.
5. Clear any pending upload key reset, payments profile change or account-type conversion before you start.
6. Plan tester recruitment for after the transfer if a test is running, because the groups do not survive.

Frequently Asked Questions

Can I buy or sell a Google Play developer account?

Not by transferring credentials. Google requires ownership changes to use the official workflow in Play Console, and its Q2 2026 roundup states that sharing login credentials or using third-party marketplaces is no longer permitted. If the account is an organisation account or a non-monetising personal account, the owner switch is the documented route. A monetising personal account cannot be switched at all, so the apps have to be transferred individually.

Why is the Make account owner option unavailable?

Four documented reasons cover most cases. You are not the account owner, the person is not yet a user on the account, the account is a monetising personal account, or the prospective owner already owns a separate Play Console account. A pending upload key reset, an in-progress app transfer or a payments profile change will also block the switch.

Do installs, ratings and reviews survive an app transfer?

Yes for the app transfer route. Google states that the users, download statistics, ratings and reviews, content ratings, store listing information and subscriptions all move to the target account, along with policy declaration submissions. What does not move is the testing configuration and the pre-transfer financial reporting.

Does my app go offline during a transfer?

Google documents no downtime for the transfer itself. Two exceptions are worth planning for. A private app distributed through Managed Google Play has to be temporarily unpublished with organisation restrictions removed, and an app selling in-app products is unpublished after the transfer when the receiving account uses a different default currency, until you republish it.

Can I cancel a transfer after submitting it?

During the seven-day hold, yes: any user on the account can cancel from the Users and permissions page. Once the prospective owner starts the final setup steps, other users can no longer cancel, and the prospective owner can only abort from the transfer page before they begin.

What happens to an active closed test when the app changes accounts?

It does not continue. Closed, open, internal and internal sharing test groups do not transfer, so the groups have to be recreated in the target account and testers may need to opt in again. Plan the transfer for a point where a test is not mid-run, or expect to rebuild the tester set afterwards.

Do I need a new upload key for the new account?

Not automatically. The upload key and the app signing key can stay as they are. Google's guidance is to evaluate whether the old key's custody is still acceptable, and the new owner can request an upload key reset, or a signing key upgrade for new installs, if it is not.

Sources

Every Google page below was opened and read on 7 November 2026. Where a statement is our reading of the documentation rather than Google's own wording, the text says so at the point of the claim.

• Transferring ownership of a Play Console developer account, Play Console Help. Eligibility for the owner switch, the payment profile prerequisite, the seven-day hold, cancellation rules and blockers.
• Transfer apps to a different developer account, Play Console Help. Prerequisites, transaction IDs, what transfers, test groups, reports, promotion codes, signing and the two-business-day review.
• Policy announcement: April 15, 2026, Play Console Help. Introduction of the Account Transfer policy requiring the official Transfer ownership workflow.
• The Latest from Google Play: Q2 2026, Google Play. The 7-day security cool-down, and the statement that unofficial transfer methods are no longer permitted.
• Create a Google Play developer account, Play Console Help. The US$25 one-time registration fee that applies to a new target account.
• App testing requirements for new personal developer accounts, Play Console Help. Background on why a test group that does not transfer matters.