Skip to content
TAA

Guide: App ownership

How to transfer your app and its code into your own accounts

An app is only yours when the store listing, the developer account and the source code sit with your company. Apple and Google both have a transfer process for this, but the current owner has to start it. Here is what each platform asks for, what moves with the app, and what you should get besides the listing.

Many companies find out late that their app is listed under the developer's or the agency's account. Everything works until that person leaves, stops answering or sends a final invoice. Then a routine update needs someone else's password.

Platform rules checked against Apple's and Google's help pages on 8 October 2026.

What "owning your app" means in practice

Four things have to sit with your company, not with a person:

  • The store listing: the app in App Store Connect and in the Google Play Console.
  • The developer accounts: Apple Developer Program and Google Play Console, registered to your company.
  • The source code: a repository in your company's account, with its full history.
  • The keys and services behind it: signing keys, server, database, domain, payment and email accounts.

Apple: transferring an app in App Store Connect

An app moves between Apple developer accounts through an app transfer. The Account Holder of the current account starts it in App Store Connect, under App Information, and enters the Apple Account and Team ID of the receiving Account Holder. Your Account Holder accepts it. Until then the request stays open for up to 60 days.

Apple lists the conditions in its app transfer criteria. The ones that most often hold things up:

  • Both accounts have accepted the latest paid and free apps agreements.
  • At least one version of the app was released to the App Store.
  • No version is waiting for review, in review or pending release.
  • The app's in-app purchase product IDs do not already exist in your account.

The app stays available for download during the transfer, keeps its reviews and ratings, and users keep receiving updates. Some parts need work afterwards, as Apple's overview of app transfer explains: subscriptions need an app-specific shared secret, TestFlight builds and Xcode Cloud data must be removed first, push notification keys, Apple Pay merchant IDs and Sign in with Apple need preparation, and with keychain sharing users have to sign in once more after the next update.

If the developer account already belongs to your company but the Account Holder is a former employee, you do not need an app transfer. The Account Holder role can be transferred to another person on the team who has the legal authority to sign agreements for your company.

Google Play: moving an app to your Play Console

Google calls it an app transfer request. Both Play Console accounts must be registered and active. The current owner submits the request with the registration transaction ID of your account, you approve it, and according to Google its support team replies within two business days. A new Play Console account costs a one-time registration fee of US$25.

Per Google's transfer instructions:

  • Moves with the app: users, statistics, ratings, reviews, subscriptions and the information submitted under App content.
  • Stays behind: earnings and payout reports, test groups and the links to services such as Firebase or Google Analytics, which have to be set up again.
  • Needs a decision: whether to keep the upload key and app signing key, or request new ones.

How to get the source code from your developer

Ask for the repository, not a ZIP file. The cleanest way is a transfer of the repository to a GitHub, GitLab or Bitbucket account that your company owns, with the complete history. Ask in writing for:

  • the repository with all branches and its history
  • the signing keys: the Android keystore or upload key, and the Apple certificates and profiles, or the access to recreate them
  • access to the server, the database and their backups
  • the API keys and accounts of services the app uses, such as payments, email or maps
  • a short note on how the app is built and released

Whether a developer has to hand the code over depends on your contract. Read it first, and if they refuse, the enforcement is a matter for your lawyer. What I do is check that what comes back is complete and that the app can actually be built and released from it.

Where I come in

The App Check at $2,000 lists every account, who owns it and who can log in, and checks whether the app builds from the code you have. The App Takeover from $10,500 then moves the accounts into your name, removes the previous developer's access and submits a store update from your own accounts. If an Android update is due anyway, the Google Play target API level deadlines tell you how much time you have.

The code sits in your repository from day one; with each paid milestone, the rights to everything delivered up to that point pass to you.

Confidential from the first call: we are happy to sign an NDA before we talk.

Professional liability insurance in place, proof on request.

Common questions

How do I transfer an app to my own App Store account?

The Account Holder of the account the app sits in starts the transfer in App Store Connect, under App Information, with the Apple Account and Team ID of your Account Holder. Your Account Holder then accepts it. The app has to meet Apple's transfer criteria, for example at least one version released to the App Store and no version waiting for or in review. Until it is accepted, the request stays open for up to 60 days.

How do I transfer an app to another Google Play developer account?

Both Play Console accounts must be registered and active. The current owner submits a transfer request with the registration transaction ID of the target account, the target account approves it, and Google's support team reviews it and replies within two business days, according to Google.

Do users lose the app, its reviews or their purchases?

Not with a proper transfer. On Apple, the app stays available for download, keeps its reviews and ratings, and users keep receiving updates. On Google Play, users, statistics, ratings, reviews and subscriptions move with the app. Some technical parts have to be redone afterwards, such as push notification keys or Sign in with Apple.

How do I get my app's source code from my developer?

Ask for the repository itself, transferred to an account your company owns, not a ZIP file: with its full history, the signing keys and the build instructions. Whether the developer has to hand it over depends on your contract, so read it first. If they refuse, enforcing it is a matter for your lawyer.

My developer will not start the transfer. What are my options?

In the standard process, neither Apple nor Google moves an app without the current owner: Apple needs the current Account Holder to start the transfer, Google needs the current owner to submit the request. Without that, the legal route goes through your lawyer, and the practical fallback is a new listing in your own account, which starts without the old ratings and reviews.

Who owns the code if you work on the app?

You do. The code sits in your repository from day one; with each paid milestone, the rights to everything delivered up to that point pass to you. Store, server and domain accounts are registered to your company.

Find out what you actually own.

30 minutes, free: you tell me where the app, the accounts and the code are today; you leave knowing what has to move into your name and in which order.

Free 30-minute call, no obligation

You talk to Marcel directly, the architect who is accountable for the work. No sales rep, no pitch.

The calendar is served by Cal.com. It loads only after you click (data goes to Cal.com, US). Privacy policy

Prefer to write first? Describe your situation, with a link to your app, repository or questionnaire. You get an answer within one business day.