Yes, you can transfer an app from a personal Apple Developer account to a company account, using the app transfer feature in App Store Connect. The app keeps its bundle ID, its reviews and ratings, and its existing users, who continue to receive updates seamlessly, so a transfer is not a re-publish and does not reset your app. Both accounts must be enrolled and in good standing, both must have accepted the latest paid and free agreements, and the app must have at least one version already released on the App Store and not be on pre-order. The sending account's Account Holder starts the transfer, and the receiving Account Holder must accept it within 60 days.
Short answer
Transferring an app between accounts moves the whole app, not just the code, and keeps its identity intact. Per Apple's app transfer overview, a transferred app maintains its bundle ID, retains its reviews and ratings, and users keep receiving updates, so nothing resets for your customers. Per Apple's transfer criteria, both accounts must not be in a pending or changing state, both must have accepted the latest agreements, the app must have at least one released version, and it cannot be on pre-order. The Account Holder initiates, and the recipient Account Holder accepts within 60 days. So the answer is yes, with conditions to meet first.
Can you transfer from a personal to a company account?
Yes, and it is a common and supported move, because App Store Connect treats the transfer as sending an app from one enrolled developer account to another regardless of whether they are individual or organization accounts. So a solo developer who started on a personal account and later formed a company can move each app to the company account, one app at a time, without rebuilding or resubmitting it as a new listing.
One thing to be clear about is that this transfers apps, not the account itself. Apple does not convert an individual account into an organization account, so the path when you incorporate is to enroll the company as its own organization account and then transfer your apps into it. Each app is transferred individually, so you can move them on your own schedule. The result is that your apps live under the company account while the personal account remains a separate entity, which is exactly what most founders want when a side project becomes a business.
Does the bundle ID change?
No, the bundle ID does not change, and that is the single most important reason a transfer is safe for your users. A transferred app maintains its bundle ID, which cannot be changed once a build has been uploaded for the app, so the app keeps the same identity in the new account as it had in the old one. Because the identity is preserved, existing users receive the next version as an ordinary update rather than having to find and install a new app.
There is a consequence worth knowing. Since the bundle ID moves with the app and stays fixed, you cannot reuse that bundle ID for a different app after the transfer, and the recipient account cannot rename it. So the transfer is not a way to change your app's identifier; it is a way to change which account owns the app while the identifier stays constant. For continuity that is exactly the behavior you want, because it is what makes the handover invisible to the people using your app.
Do reviews and ratings transfer?
Yes, the app retains its reviews and ratings through the transfer, along with its version history, so you do not lose the social proof you have built up. This is a frequent worry, because ratings and reviews are hard-won, and the reassurance is that they stay attached to the app rather than to the account. During and after the transfer the app remains on the App Store, so it does not disappear from search or become unavailable to download while ownership changes.
Because the reviews, ratings, and bundle ID all carry over, the transfer is essentially invisible from the user's side. They keep the app installed, they keep seeing its accumulated ratings, and their next update arrives normally. What changes is behind the scenes: the app now sits under the company account, and future proceeds, agreements, and management happen there. So the parts of your app that represent its reputation and reach are preserved, which is what makes transferring far preferable to relaunching under a new listing.
Requirements before you transfer
Before a transfer can go through, both accounts and the app itself have to be in an eligible state, and missing one of these is the usual reason a transfer cannot start. Both the sending and receiving accounts must not be in a pending or changing state, and both parties must have accepted the latest version of their paid and free agreements, since an outstanding agreement blocks the transfer. The app must have at least one version that has been released to the App Store, and it cannot currently be available for pre-order in any country or region.
There are additional eligibility conditions on Apple's criteria page that can block specific apps, so it is worth checking them against your app before you begin. Certain capabilities and configurations, and unresolved issues on the app, can prevent a transfer until they are addressed. The safe approach is to confirm your app has a released version, is not on pre-order, and that both accounts have clean, up-to-date agreements, then review Apple's full criteria for anything specific to your app, so the transfer is not rejected partway through.
What transfers and what you set up again
Not everything moves with the app, so it helps to separate what carries over from what the recipient re-establishes. The app itself, its bundle ID, its released versions, its reviews and ratings, and its existing users all transfer, which is the core of what you care about. In-app purchases associated with the app move with it as well, so your products and their identifiers are preserved.
What the receiving account handles on its own side are the account-level pieces. The recipient uses their own signing certificates and provisioning, since those belong to their team, and their own agreements, banking, and tax information govern proceeds from the transfer date forward. App Store Connect users and roles are set up in the receiving account, and some historical analytics remain associated with the original account. So plan for the recipient to have their Paid Apps agreement, banking, and tax details in place before accepting, so payments continue without a gap once the app is theirs.
Transfer criteria versus common blockers
Matching the requirement to the thing that blocks it helps you prepare. The table below maps the common ones.
| Requirement | Common blocker | How to clear it |
|---|---|---|
| Accounts in a stable state | One account is mid-change | Wait until no changes are pending |
| Latest agreements accepted | An unsigned paid or free agreement | Accept the current agreements in both accounts |
| At least one released version | App never went live | Release a version before transferring |
| Not on pre-order | App is available for pre-order | Remove pre-order or wait until release |
| App-specific eligibility | A capability that blocks transfer | Check Apple's criteria and resolve it |
Read the first two rows first, since a pending account state or an unaccepted agreement is the most common reason a transfer cannot be initiated.
How to transfer, step by step
The mechanics are straightforward once the requirements are met. The sending account's Account Holder starts the transfer in App Store Connect from the app, using the option to transfer the app, and provides the recipient's information, their Team ID and the Apple Account email of their Account Holder, which you get from the receiving side. Initiating the transfer does not take the app down; it stays live throughout.
The receiving Account Holder then accepts the transfer within 60 days, and as part of accepting they confirm their agreements and provide the banking and tax details needed for a paid app. Once accepted, the app moves to the company account with its bundle ID, reviews, ratings, and users intact, and you continue managing it from there. If the recipient does not accept within 60 days, the transfer expires and you would need to initiate it again, so coordinate the timing so both sides are ready.
What to check before and after
Working through these steps makes the transfer smooth. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Confirm eligibility | Released version, not on pre-order | [ ] |
| Update agreements | Both accounts accepted the latest agreements | [ ] |
| Prepare the recipient | Banking and tax ready in the company account | [ ] |
| Exchange details | Get the recipient Team ID and Account Holder email | [ ] |
| Initiate and accept | Start the transfer; accept within 60 days | [ ] |
| Re-establish account items | Set up signing, users, and roles in the new account | [ ] |
The step teams skip most is preparing the recipient's banking and tax details, since proceeds after the transfer flow through the new account and need those in place.
Where a scan fits
Transferring an app is an account and ownership task, so a security tool has no role in the transfer itself, and it is worth being clear about that boundary.
A scanner like PTKD.com analyzes your app build for security issues such as exposed keys, over-broad permissions, and risky third-party code, mapped to OWASP MASVS. To be clear about the boundary: PTKD does not move your app between accounts or manage your agreements, which you do in App Store Connect. A move to a company account is a natural moment to review the app's security, and a scan gives you that check while the transfer itself stays an App Store Connect operation.
What to take away
- Yes, you can transfer an app from a personal to a company Apple Developer account using App Store Connect, one app at a time.
- The bundle ID does not change, so existing users receive updates seamlessly and the app keeps its identity.
- Reviews and ratings transfer with the app, and it stays available on the App Store throughout, so nothing resets for users.
- Both accounts must be in a stable state with the latest agreements accepted, and the app must have a released version and not be on pre-order.
- The Account Holder initiates and the recipient accepts within 60 days, after setting up their banking and tax; a tool like PTKD.com is for auditing the app, not the transfer.
