Selling an Apple Developer Account With an Existing App: Account Handover vs App Transfer, and What to Verify

First decide: are you buying the account or the app inside it

An aged account with an app can change hands in two very different ways. In a full account handover, the app stays where it is and you take over the account itself. In an App Transfer, the app moves from the seller's account into a developer account you already hold. The first puts the risk on account ownership and login control. The second puts it on transfer prerequisites and on whether the app's capabilities survive the move. If you already have an eligible account and only want the app, a transfer is usually cleaner. If you need the account's age, entity type or country, a full handover is the only route that delivers it.

Check app status inside App Store Connect, not in a description

Sit through a live walkthrough or get screenshots straight from the console. Verify the app's state (live, removed, in review), the Bundle ID, the current version, territories, any in-app purchases or auto-renewable subscriptions, and the review history for rejections or warnings. Then list the capabilities in use: push notifications, Sign in with Apple, iCloud, associated domains, App Groups. These tie to identifiers and certificates and often need reconfiguring after a move, and some capabilities carry transfer restrictions. Apple's current documentation governs the exact conditions, so read it rather than relying on memory. If an app has been delisted or left idle, find out whether that was the owner's choice or a policy action.

A listing is not a license to the source code

The developer account proves who published the app. It says nothing about who owns the code. Settle three things before paying: whether source code and build scripts are delivered, and in what form; whether third-party SDKs, fonts, audio and icons are licensed to transfer with the app; and who owns the backend, API domain, cloud accounts, analytics and crash reporting. A common failure is an app that stays online but can never be updated, because the buyer received the account without a buildable project or the backend remained under the seller's name. Without source, treat the app as a listing record, not a product you can maintain, and price it that way.

Credentials and entity details: who controls the Apple ID and who is the Account Holder

In a full handover, confirm that the Account Holder's Apple ID, its email, phone number and two-factor devices can be changed and end up solely with you. For individual accounts, the holder's identity should match the registration country. For organizations, check that the legal entity name, D-U-N-S number, website and contacts are still valid. Changes to the Account Holder or entity details should go through Apple's official support process with whatever documents Apple requires at the time. Do not accept arrangements that rely on someone else's identity documents, altered files, or a seller who keeps control of two-factor verification. Accounts set up that way tend to fail the next time they are reviewed.

A workable handover order with a check at each step

A safer sequence: record app status and capabilities in the console; transfer source, assets and backend ownership; change login and contact details so only you can pass two-factor; release the final payment last. For an App Transfer, the seller initiates it, your account accepts, and you then recheck the Bundle ID, in-app purchases, certificates and provisioning profiles, followed by a test build through your own submission flow. Every check should be something you perform yourself: log in, create a build, edit store metadata. A verbal assurance from the seller is not a check.

When to pause the deal

Stop and reassess if the seller cannot show live app status, or offers only static screenshots; if rejections or removals have no explanation; if code, backend and asset ownership is unclear; if the two-factor device never moves to you; if the entity details do not match the sales or payout region; or if the app depends on capabilities that break on transfer with no substitute. These rarely resolve after payment. Account standing, membership validity and review outcomes change with platform policy, so rely on what the console shows on the day of handover.