Transferring an App Between Apple and Google Developer Accounts
Short answer
Both Apple and Google let you transfer a published app to another developer account while keeping its users, ratings and store listing. The current owner starts the transfer, the receiving account accepts it, and the app keeps its bundle ID or package name. What does not move automatically – keys, linked services, team-scoped identifiers – causes most of the trouble.
Typical reasons for a transfer
Most transfers follow one of three patterns: an agency published the app in its own account and the client now wants ownership, a company sells a product or a business unit, or a group consolidates apps from several subsidiaries into one account. In all three cases a transfer is far better than publishing a new app, because users keep receiving updates and the listing keeps its reviews and ranking history.
Transferring an app on the Apple App Store
The Account Holder of the current team starts the transfer in App Store Connect, in the app's information section. You need the receiving team's Team ID and the Apple ID of its Account Holder. The receiving Account Holder then accepts the request. Before you start, check Apple's current transfer criteria; in practice the important points are:
- At least one version of the app has been approved and released.
- No version is currently waiting for or in review.
- Both teams have accepted the latest agreements, including the paid apps agreement if the app sells anything.
- Certain capabilities need extra steps or block the transfer; review the app's services such as iCloud, Apple Pay and Sign in with Apple in advance.
The app record, bundle ID, ratings, reviews and in-app purchases move to the new team. Historical sales and financial reports stay with the previous owner, and TestFlight testers should be expected to be set up again.
Transferring an app on Google Play
On Google Play, the current owner also initiates the transfer from the Play Console and needs the identifying details of the target developer account; the target account owner confirms. The app keeps its package name, installs, ratings and reviews. With Play App Signing, the app signing key moves with the app, so users can keep updating. Both accounts must be in good standing, and if the app sells digital goods, the target account needs its own payments profile in place.
What breaks if you do not prepare
The store record moves; the surrounding infrastructure often does not. Check this list before the transfer date:
- Push notifications: APNs keys and certificates belong to the old team. Create new ones in the receiving account and update your push provider before releasing the first build from the new team.
- Team ID changes on iOS: Universal links rely on the apple-app-site-association file, which contains the Team ID – update it. Keychain items stored under the old team prefix may become unreadable; test an update installed over the old version.
- Sign in with Apple: User identifiers are scoped to the team. Apple provides a migration process with a limited time window; plan it, or users may appear as new accounts.
- Linked Google services: Firebase, AdMob, Google Analytics, Play Games services and API access for CI need to be relinked or moved separately.
- CI/CD and signing: Distribution certificates, provisioning profiles, upload keys and API keys in your pipeline all reference the old account.
- Legal details: The seller name on the listing changes. Update the privacy policy, imprint and support contact, and inform users if the data controller changes.
Agencies: avoid the transfer in the first place
The cleanest setup is that the client owns the developer accounts from day one and the agency works inside them with role-based access – App Manager or Admin in App Store Connect, scoped permissions in the Play Console. That removes transfer risk, keeps billing and legal responsibility where they belong and makes it easy to change service providers later. Our guide to the Apple Developer account for companies explains roles and the D-U-N-S requirement.
How jocapps can help
appsubmitter.io combines AI-assisted checks with experienced App Specialists and always works in your own developer accounts. We can prepare a transfer, rebuild signing and CI/CD in the receiving account, recreate push keys and submit the first update under the new owner. See our App Store launch service for the full scope, or book a free 30-minute intro call via the meeting planner.
Frequently asked questions
Do users have to reinstall the app after a transfer?
No. The app keeps its bundle ID or package name, so existing users receive updates from the new owner as normal.
Do ratings and reviews move with the app?
Yes, on both stores ratings and reviews stay with the app. Historical financial reports generally remain with the previous account.
Can I transfer an app that was never published?
On the App Store, a transfer requires at least one released version. For unpublished apps it is usually simpler to create a new app record in the target account.
Do active subscriptions survive the transfer?
In-app purchases and subscriptions move with the app. Make sure the receiving account has its agreements, tax and banking or payments profile set up first, and test purchase flows after the first update.
Guides on this topic
Related solutions
- App Store and Google PlayApp Maintenance After Launch: OS Updates, SDKs, Certificates, Budget
- App Store and Google PlayApp Store and Google Play Screenshots, Videos and Metadata Done Right
- App Store and Google PlayRejected Under Apple Guideline 4.3 Spam? Causes, Replies and Fixes
- App Store and Google PlayFixing an Apple Guideline 5.1.1 Data Collection and Privacy Rejection
Talk to us about your project
Honest advice on your idea, prototype or app.
- 30 minutes
- Free
- No obligation
