How to Transfer a Google Play App to Another Account (Step-by-Step Guide)

Moving an app between Google Play Console accounts — after an acquisition, a rebrand, or an agency handoff — is an approval workflow with a few sharp edges. This guide covers the official transfer process, the common failure points, and how to verify everything landed safely. Done right, you keep your install base, ratings, reviews, and statistics. Done wrong, you start from zero.

In short: you transfer a Google Play app by submitting Google's app-transfer request with the package name, both accounts' registered developer names and owner emails, and both accounts' $25 registration transaction IDs. The target owner accepts, Google support replies within two business days, and the app moves with its installs, ratings, reviews, store listing, and history intact. Never unpublish and re-upload instead — that creates a brand-new listing with zero history.

Why do transfers happen — and why do people mess them up?

The most common reasons for a transfer:

• Personal account → organization account as a startup matures
• Agency hands a client app over after development
• Business acquisition or asset sale

The biggest mistake developers make is uploading the app fresh to the new account and unpublishing the old listing. That creates a new listing with zero install base, zero reviews, and no update path for existing users. The official transfer preserves everything. Always use it.

What do you need before you start?

Before starting, confirm the following on both accounts:

1. Both accounts are active and in good standing. Google won't transfer from an account that is suspended or terminated — that's a different (and much harder) problem.
2. The app meets transfer eligibility: it must be published (not draft), have no unresolved policy issues, and not be part of certain restricted programs.
3. The target account is registered, active, and able to accept the app, with no header message in Play Console saying it cannot publish.
4. You know your signing configuration. If the original account uses Google Play App Signing (mandatory for new apps), the transfer is straightforward. Your upload key stays with you — the app signing key moves with the app automatically.

How do you check your signing setup?

Verify whether the app uses Play App Signing and which upload key you're holding:

# Check the certificate fingerprint of your upload keystore
keytool -list -v -keystore upload-keystore.jks -alias upload -storepass:env KEYSTORE_PASS | grep -A1 "SHA256"

# Compare against the upload certificate shown in Play Console:
# Setup → App integrity → Upload key certificate

If the original account managed signing entirely with Play App Signing and you don't have a local upload key, the new account can request an upload key reset after the transfer — it doesn't need the old key to do that.

How does the transfer work, step by step?

Google's transfer is a support request, not a button inside Play Console. You submit it through the official app-transfer form, the target owner accepts, and Google support reviews it.

Step 1: Gather the details for both accounts

You'll need:

• The app's package name (e.g., com.yourcompany.yourapp)
• Both accounts' registered developer names (exactly as shown in their account details)
• Both accounts' owner email addresses
• Both accounts' developer registration transaction IDs — the $25 fee receipt. Find each one by searching the owner's inbox for "developer registration fee", or in Google Payments under Activity. Google instructs you to drop the leading part of the order ID (for example, paste only the digits from 0.G.123456789012345).

Step 2: Submit the transfer request

The current owner submits the transfer request through Google Play Developer Support's app-transfer form with the details above. The app's status becomes "Pending App Transfer" and the app stays live and fully functional while the request is open.

Step 3: The target account accepts

The receiving owner reviews and accepts the request in Play Console. Nothing moves until they do. The request expires if nobody accepts within 60 days.

Step 4: Google reviews and completes the transfer

Google support replies to transfer requests within two business days of the receiving owner's acceptance. Once approved, the app moves over with:

• All install history, ratings, and reviews
• Store listing content and graphics
• Release history and track configuration
• Statistics history

What does not transfer: any separate upload key remains the original owner's responsibility — reset it if you don't have it. Firebase projects linked to the app must be moved separately in the Firebase console. AdMob and Google Play Billing / merchant accounts are not transferred — reconfigure monetization in the new account.

What should you check right after the transfer?

Run through this immediately after acceptance:

• [ ] Confirm the app appears in the new account with full history (ratings, reviews, stats)
• [ ] Reset the upload key if you didn't receive the original keystore
• [ ] Re-link the Firebase project (or transfer the Firebase project itself)
• [ ] Reconfigure Google Play Billing / merchant account in the new account
• [ ] Update any CI/CD pipelines with the new account's service account credentials
• [ ] Remove old API access keys from the original account
• [ ] Update the contact email in store listing settings

Updating CI/CD service accounts

If you publish via the Google Play Developer API (fastlane, Gradle Play Publisher, etc.), the new account needs a fresh service account with release permissions:

# After creating a service account in Google Cloud and granting it
# access in the NEW Play Console (Users and permissions → service account),
# update your CI secrets:

# fastlane example — point to the new account's key
supply(
  package_name: "com.yourcompany.yourapp",
  json_key: "new-account-play-key.json",
  track: "production"
)

Can you transfer an app out of a suspended account?

This is where it gets painful. Google does not allow transferring apps out of a suspended or terminated developer account through the normal flow. In practice:

• If the account was suspended with a warning (not terminated), resolve the policy violation first, get the suspension lifted, then transfer.
• If the account was terminated, the apps are effectively stranded. You'd need to republish from scratch under a new account with a new package name — and even that is risky if Google associates the new account with the terminated one.

This is exactly why account hygiene matters before trouble starts. If you're unsure whether your current account structure is transfer-safe — signing keys enrolled in Play App Signing, the right account type for verification — getting hands-on help with Play Console account setup from people who do this daily can save you from a painful dead end later.

What are the common pitfalls?

1. Unpublishing and re-uploading instead of transferring. You lose reviews, ranking history, and existing users get no update path.
2. Forgetting the upload key. Without it (or a reset), you cannot ship updates after the transfer.
3. Assuming Firebase moves with the app. It doesn't — move the Firebase project separately or re-link.
4. Mismatched developer names. The transfer form is strict about the target account's exact registered developer name. Copy it from the target account's details page.
5. Starting a transfer with unresolved policy warnings. Clear them first or the transfer stalls.
6. Using only one transaction ID. Google needs the registration transaction ID for both accounts, not just the target.

How long does a transfer take?

Phase	Typical duration
Preparing (signing check, Firebase plan, gathering IDs)	1–2 hours
Target owner reviews and accepts	Up to you and the other party; request expires after 60 days
Google support review after acceptance	Within 2 business days
Reconfiguration in the new account	Half a day

Plan for a week of calendar time even though the hands-on work is under a day. And once the dust settles, document your new signing setup somewhere durable — future-you will thank present-you.

FAQ

Can I transfer a Google Play app to another developer account?
Yes. Submit Google's app-transfer request with the package name, both accounts' developer names and owner emails, and both accounts' $25 registration transaction IDs. The target owner accepts and Google support replies within two business days.

What transfers with the app?
Install history, ratings, reviews, store listing content and graphics, release history, track configuration, and statistics. The app signing key moves with the app under Play App Signing.

What does not transfer?
Your upload key (reset it if you don't hold it), Firebase projects (move separately), and AdMob / Google Play Billing merchant accounts (reconfigure them in the new account).

How long does a Google Play app transfer take?
Gathering the details takes 1–2 hours, acceptance depends on both owners (the request expires after 60 days), and Google support replies within two business days of acceptance. Plan for about a week end to end.

Can I transfer an app out of a suspended account?
No. Google does not allow transfers out of suspended or terminated accounts through the normal flow. Resolve the suspension first; a terminated account's apps are effectively stranded.

Do I need the transaction ID for both accounts?
Yes. Google requires the developer registration transaction ID for both the original and the target account. Find each by searching the owner's inbox for "developer registration fee" or in Google Payments under Activity, and paste only the digits if the ID starts with a prefix like 0.G..

---

About the author: This guide was written by the team at Play Console Store — an independent marketplace for Google Play publishing services, not affiliated with or endorsed by Google LLC. We help Android developers with Play Console account setup, closed testing coordination, and policy compliance. Note that each developer must register their own Play Console account ($25 one-time fee).