Quick Answer: How Do You Transfer App Ownership to Your Own Developer Account?
To transfer app ownership from your developer or agency to your own business, you first open your own developer account on each store, then the current account owner sends a transfer request and you approve it. On Google Play, the developer submits the request from the original account, you approve it as owner of the target account, and Google support responds within two business days (Play Console Help: Transfer apps to a different developer account). On the App Store, the Account Holder of the current account clicks Transfer App in App Store Connect, you accept within 60 days, and the transfer can take up to two business days to complete (App Store Connect Help: Accept an app transfer). On both stores the app keeps its users, ratings and reviews.
Last updated: November 2026. This guide is for business owners whose app sits in a freelancer's or agency's developer account, and for owners about to hire an app developer. Every step, fee and time limit was checked against Google Play Console Help and Apple Developer documentation on November 17, 2026. Both transfers are done inside the official consoles by the two account owners. No middleman is needed, and nobody needs your password.
Key Takeaways
- You need your own accounts first: Google Play charges a US$25 one-time registration fee, and the Apple Developer Program costs 99 USD a year.
- The current owner starts it: on Google Play the request is submitted from the original account; on the App Store only the Account Holder of the current account can initiate a transfer.
- You approve it: the target account owner approves on Google Play, and the receiving Account Holder must accept on the App Store within 60 days.
- What stays with the app: users, ratings and reviews, on both stores.
- What does not move: the source code, past financial reports, test groups and links to services such as Firebase or Google Analytics.
Why Should the App Be in Your Own Developer Account?
When a freelancer or agency publishes your app under their own developer account, you depend on that person to push updates, answer the store and, eventually, hand the app over. The official documentation shows why the account matters.
- Seller name on the App Store: Apple lists the legal entity name of an organization account, or the personal legal name of an individual account, as the seller of the app.
- Legal agreements with Apple: the Account Holder is the only user who can sign legal agreements and renew the membership, and is the person responsible for entering into agreements with Apple.
- Payments on Google Play: the account owner is the only person who can link a payments profile to sell paid apps and the only one who can access the Payments profile page in Play Console.
These points come from Apple's enrollment requirements and role permissions pages pages and Google's Add developer account users and manage permissions article. If you are still planning the build, see our mobile app development cost breakdown.
What Do You Need Before You Start?
Both stores transfer an app only between two existing developer accounts, so the first job is opening yours. For Google Play, you need a Google Account, you must be at least 18, and you pay a US$25 one-time registration fee (Get started with Play Console). Google offers personal and organization accounts and says to choose an organization account when the account is for an organization or business. An organization account requires a D-U-N-S number (Choose a developer account type).
For the App Store, the Apple Developer Program annual fee is 99 USD, in local currency where available. To enroll as an organization, the business must be a legal entity. Apple does not accept DBAs, fictitious businesses, trade names or branches, and it asks for a D-U-N-S Number and a work email address on the organization's domain. A sole proprietor or single-person business enrolls as an individual, and the personal legal name then appears as the seller (Apple Developer Program enrollment).
The D-U-N-S Number is the step that takes longest. Apple says to allow up to 5 business days to receive the number from Dun & Bradstreet and up to 2 more business days for Apple to receive the information (Apple: D-U-N-S Number). Scam warning: Google states that applying for a D-U-N-S number through Dun & Bradstreet is completely free and warns about third-party services that try to charge high administrative fees for it. Request it yourself and do not pay anyone for it.
- For Google Play: the registration transaction ID of both the original and the target account. Search the account owner's inbox for "developer registration fee", or look under Activity in Google Payments.
- For the App Store: the Apple Account of your Account Holder and your Team ID, which the current owner has to enter.
- Payments: on Google Play, an active payments profile on your account if the app is paid or sells in-app products.
- Your new details: a support URL, privacy policy URL and contact information, which Apple asks you to enter when you accept.
How to Transfer App Ownership on Google Play - Step by Step
Google's process is a request form inside Play Console. The steps below follow Transfer apps to a different developer account.
- Step 1 - Check policy status: the original account and every app being transferred must comply with Google Play policy guidelines.
- Step 2 - Download reports: ask your developer to download bulk export, payout and earnings reports first, because these do not transfer with the app.
- Step 3 - Confirm both accounts are active: the developer can sign in to the original account, and your target account has completed registration. If your account shows the message "Why can't I publish", resolve the missing information first.
- Step 4 - Collect the transaction IDs: you need the registration transaction ID for both accounts. Google says to remove the prefix or order identifier (for example 0.G.) when entering it.
- Step 5 - Submit the request: the developer signs in to the original account and submits the official transfer request form.
- Step 6 - Approve it: as the target account owner, you receive the request to review and approve.
- Step 7 - Wait for Google: after approval, support reviews and responds to transfer requests within two business days.
The form is here: Play Console app transfer request (sign-in to a developer account is required). One point to check: personal accounts created after November 13, 2023 must run a closed test with at least 12 testers for 14 days before an app can be made available on Google Play (App testing requirements for new personal developer accounts). The transfer article does not say how this applies to an app that arrives by transfer, one more reason for a business to register an organization account.
How to Transfer App Ownership on the App Store - Step by Step
On the App Store the transfer is started and accepted in App Store Connect, and both sides need the Account Holder role. Start by checking the app transfer criteria: the app must have at least one version released to the App Store, it cannot be available for pre-order, and it cannot be in a status such as Waiting for Review or In Review. Both parties must also have accepted the latest version of their paid and free agreements.
- Step 1 - Back up: the app is removed from the current account after the transfer, so Apple advises keeping a record of metadata, pricing, availability dates and sales and download information.
- Step 2 - Turn off TestFlight: Apple says beta testing should be turned off before the transfer by removing all builds and testers and clearing the Test Information fields.
- Step 3 - Initiate: the current Account Holder opens the app in App Store Connect, clicks App information under General, scrolls to Additional Information and clicks Transfer App.
- Step 4 - Enter your details: they enter the Apple Account of your Account Holder and your Team ID, agree to the terms and click Request Transfer.
- Step 5 - Accept: you sign in to App Store Connect, go to Business, and under App Transfers click Review.
- Step 6 - Enter new metadata: the support URL, the marketing and privacy policy URLs if the app had them, and App Review and App Store contact information. Then review the App privacy details, agree to the terms and click Accept.
- Step 7 - Wait: the status shows Processing App Transfer, and it can take up to two business days to complete. Both Account Holders are notified when it is done.
The click paths are in Initiate an app transfer and Accept an app transfer. A request that is not accepted expires after 60 days, and either side can cancel while it is still waiting for the recipient. While it is pending, the current owner cannot edit some app information such as metadata, pricing and In-App Purchases, so agree on a week with no release planned.
What Transfers With the App and What Does Not?
The store listing and its audience move. Most of what surrounds the app does not. Use this as a checklist with your developer.
- Google Play, transfers: all users, statistics, ratings and reviews, subscriptions, content ratings, store listing information and policy declarations already submitted.
- Google Play, does not transfer: bulk export, estimated sales and earnings reports; promotions (issued promo codes keep working); internal, closed and open test groups, which must be recreated; permissions and links to integrated services.
- Google Play, older orders: orders created before the transfer remain in the original account, so refunds for them need access to that account or the Google Play Developer API.
- App Store, stays the same: availability on the App Store, reviews and ratings, updates for existing users, and the Bundle ID.
- App Store, changes hands: the App ID moves to your account, and you must create new provisioning profiles in your Apple Developer account after the transfer.
- App Store, needs follow-up: the merchant ID for Apple Pay is not transferred, push notification certificates must be regenerated once they expire, and apps with auto-renewable subscriptions need an app-specific shared secret exchanged before the transfer.
- Source code, both stores: Apple states that the transferor is responsible for exchanging the actual code set and building assets directly with the recipient. A store transfer does not hand you the code.
For Google services, the Play Console transfer article lists the manual work: add the target account as an Owner of the Google Cloud Console projects, unlink Firebase projects from the original Play Console account and link them to the target account, add permissions in Google Analytics, and update ad SDK integrations after the transfer. Apple's Overview of app transfer covers the equivalent cases, including Sign in with Apple, iCloud, Wallet and keychain sharing.
What Mistakes Delay or Block an App Transfer?
- Enrolling under a trade name: Apple does not accept DBAs or trade names for organization enrollment. Use the legal entity name.
- Starting during a review: an app that is Waiting for Review, In Review or Pending Developer Release cannot be transferred on the App Store.
- An unreleased iOS app: Apple requires at least one version released to the App Store. If the app has not launched yet, it is simpler to publish it from your own account from the start.
- Clashing product IDs: In-App Purchase product IDs on the app cannot match product IDs on any app already in the receiving Apple account.
- Different default currency: if the target Google Play account uses another default currency and the app sells in-app purchases, Google unpublishes the app after the transfer until you verify the prices and publish it again.
- Forgetting the code and keys: ask for the source code repository, build assets and, for Android apps using Play App Signing, a decision on the upload key. Google lets the target account owner request a new upload key if there are security concerns.
One honest limit: both stores require the current account owner to start the transfer. The help pages checked for this guide describe no route for the receiving business to pull an app out of another account by itself. If your developer is not responding, contact each store's developer support; this guide cannot promise the outcome. That is why the account question belongs in the contract before the build starts.
DIY, Freelancer or Agency: Who Should Handle the Transfer?
The store side of a transfer can only be done by the two account owners, so part of it is always yours. The official pages name the account fees (US$25 once for Google Play, 99 USD a year for Apple) and list no separate charge for the transfer request. What varies is the technical work after it.
- Do it yourself: realistic for a simple free app with no in-app purchases, no push notifications and no linked services.
- Freelancer: a good fit when the original developer is cooperative and still maintains the app. Ask them to ship one update from your account to prove the handover works.
- Agency: worth it when the app has subscriptions, Apple Pay, Sign in with Apple, Firebase or several environments, or when someone new has to take over the code as well as the listing.
After the transfer, you do not need to share your login to let a developer keep working. In Play Console, the account owner or an admin invites users under Users and permissions and chooses app-level or account-level permissions, and can set an access expiry date (Play Console Help). In App Store Connect, you add people under Users and Access with a role such as Developer or App Manager (Add and edit users). When you brief a new team, ask in writing which account the app will be published from and who holds the source code. ITSolutionNYC is based in Louisville, KY and works with clients remotely. If you want a team to take over the build or the handover, see our mobile app development service. For store listing assets after the move, our guide to Google Play Store screenshot sizes has the current dimensions.
Sources
- Play Console Help: Transfer apps to a different developer account: https://support.google.com/googleplay/android-developer/answer/6230247
- Play Console Help: Get started with Play Console: https://support.google.com/googleplay/android-developer/answer/6112435
- Play Console Help: Choose a developer account type: https://support.google.com/googleplay/android-developer/answer/13634885
- Play Console Help: App testing requirements: https://support.google.com/googleplay/android-developer/answer/14151465
- Play Console Help: Add developer account users and manage permissions: https://support.google.com/googleplay/android-developer/answer/9844686
- App Store Connect Help: Overview of app transfer: https://developer.apple.com/help/app-store-connect/transfer-an-app/overview-of-app-transfer/
- App Store Connect Help: App transfer criteria: https://developer.apple.com/help/app-store-connect/transfer-an-app/app-transfer-criteria/
- App Store Connect Help: Initiate an app transfer: https://developer.apple.com/help/app-store-connect/transfer-an-app/initiate-an-app-transfer/
- App Store Connect Help: Accept an app transfer: https://developer.apple.com/help/app-store-connect/transfer-an-app/accept-an-app-transfer/
- App Store Connect Help: Role permissions: https://developer.apple.com/help/app-store-connect/reference/role-permissions/
- App Store Connect Help: Add and edit users: https://developer.apple.com/help/app-store-connect/manage-your-team/add-and-edit-users/
- Apple: Enrollment: https://developer.apple.com/support/enrollment/
- Apple: D-U-N-S Number: https://developer.apple.com/support/D-U-N-S/
Conclusion
To transfer app ownership to your own developer account, open your own Google Play and Apple Developer Program accounts, have the current owner submit the transfer on each store, approve it, and then deal with what the stores do not move: source code, reports, test groups and linked services. The listing, users, ratings and reviews stay with the app. Nothing here guarantees a smooth handover, but requesting the D-U-N-S Number early and getting the code alongside the listing remove common causes of delay.
