Use this guide when your team can execute an eligible transfer itself. If signing continuity, Firebase, billing, OAuth, ads, subscriptions, or account coordination need one accountable owner, the managed App Migration service covers those dependencies in a written scope.
When Would You Transfer an App?
Common scenarios for app transfers between Google Play accounts:
- Business acquisition — Buying or selling an app or company
- Personal to Organization — Moving from personal account to a company account
- Developer transition — Moving an app built by a contractor to your own account
- Company restructuring — Consolidating apps under a parent company account
- Portfolio reallocation — Moving eligible apps between verified, owner-controlled accounts
Key Point
An eligible app transfer keeps the package and public listing with the app, including install history, ratings, and reviews. Continuity for existing installations, subscriptions, billing, APIs, Firebase, AdMob, and other linked systems depends on the app's configuration and must be verified before and after the move.
Eligibility Requirements
Both the source (sending) and destination (receiving) accounts must meet these criteria:
Source Account
- Account in good standing (no active policy violations)
- App must be published or unpublished (not suspended or removed)
- All in-app purchase issues resolved
- No pending app updates under review
Destination Account
- Verified and in good standing
- Identity verification completed
- Payment profile set up (if app has monetization)
- Must accept the app transfer request
Restriction
Do not use a transfer as a workaround for enforcement. Check the current eligibility guidance and the exact Policy status on both accounts before requesting a move; a suspended or removed app, terminated account, unresolved policy issue, or another dependency can block or delay the request.
What Transfers (and What Does Not)
Transfers With the App
- App listing (title, description, screenshots, feature graphic)
- Install count and download history
- User ratings and reviews
- Active subscriptions and in-app purchases
- Store listing URL and package name
- Version history
Does NOT Transfer
- Statistics history — Analytics data stays with the original account
- Financial reports — Revenue data remains in the source account
- Firebase project — Must be transferred separately through Firebase console
- Play App Signing key — Managed by Google, transitions automatically
- Custom store listing experiments — A/B tests do not transfer
- Managed publishing queue — Pending changes are lost
Step-by-Step Transfer Process
- Source account: Open Google Play Console → Select the app → Setup → Advanced settings
- Find "Transfer app" section and click "Transfer"
- Enter destination account's developer ID (found in the destination account's Settings → Developer account → Developer ID)
- Confirm transfer request — Review the terms and submit
- Destination account: Log into Play Console → Check "Transfer requests" notification
- Accept the transfer — Review app details and confirm
- Track processing — Google controls the transfer review time; preserve the request, account details, and any follow-up
Timeline & Status Tracking
- Transfer request — Preserve the submitted request and verify that the destination account can see it
- Acceptance — Follow the deadline and instructions shown in the destination account
- Processing — Google controls completion and may request additional information
- Closeout — Verify the app, payments, signing, releases, users, and every linked service before declaring the transfer complete
An eligible transfer is designed to preserve the public app, but do not promise zero disruption. Monitor availability, purchases, subscriptions, APIs, authentication, messaging, analytics, ads, and release access throughout the change.
Common Pitfalls
- Firebase not transferred — Remember to transfer the Firebase project separately, or the new account will not have access to crash reports, analytics, or push notifications
- API keys and secrets — Update any API credentials tied to the original account
- Ad account configuration — AdMob accounts need to be updated to the new developer account
- Subscriptions — Ensure the new account's payment profile is configured to receive subscription revenue
- Pending updates — Cancel any pending updates before initiating transfer
Preserve account-level evidence
Export the reports and experiment records you may need later. Transfer behavior differs by product and dataset, so verify what follows the app, what remains account-level, and what requires a separate ownership change.
After Transfer Checklist
- Verify app appears correctly in new account's Play Console
- Confirm all in-app purchases work correctly
- Transfer Firebase project to new owner
- Update API keys and third-party service configurations
- Verify push notifications still work
- Check that ad revenue is flowing to the correct account
- Update your developer name if it changed
- Publish a minor update from the new account to confirm full access
Migration Service
Our App Migration service starts at $149 for a scoped basic transfer. Firebase, Analytics, AdMob, billing, API reconfiguration, and extended verification belong to a separately quoted migration scope. Contact us.
Evidence standard
Primary references
These first-party sources support the changeable platform requirements in this guide. Your current Play Console notice remains authoritative for account-specific steps.
Review your next Play Console step
Tell us what the account shows, where the release is blocked, and what has already been submitted. We will scope the work around the evidence in your case.
Discuss Your Release