How to transfer an iOS app after acquisition
A clean iOS app handoff depends on App Store Connect eligibility, documented revenue, source and release access, backend ownership, privacy responsibilities, and an agreed sequence for buyer and seller actions.
Transfer planning should happen before closing.
Buyers and sellers should agree on what moves through Apple, what moves through separate service transfers, what requires credential rotation, and what support the seller will provide after control changes.
iOS transfer readiness areas
Use these categories to prepare a listing, review an acquisition target, and reduce avoidable handoff surprises.
App Store Connect readiness
Confirm the app, bundle ID, in-app purchases, subscriptions, associated domains, capabilities, agreements, and team roles against Apple's current transfer requirements.
Revenue and payout context
Separate App Store proceeds, subscriptions, ad revenue, refunds, chargebacks, taxes, and any off-platform income so the buyer understands what does and does not transfer.
Source and release handoff
Prepare repository access, build instructions, signing notes, certificates, provisioning context, third-party SDK keys, backend dependencies, and release procedures.
Ownership and privacy review
Document IP ownership, contractor assignments, privacy disclosures, data handling responsibilities, support obligations, and unresolved App Review or policy issues.
Practical transfer sequence
- Review Apple's current app transfer requirements before signing a purchase agreement or promising a closing date.
- List every asset that must move outside App Store Connect, including code, backend services, domains, analytics, support tools, push notification services, and documentation.
- Agree on the exact sequence for payment, App Store transfer initiation, source access, operating access, and post-close seller support.
- Keep sensitive credentials out of broad diligence materials and transfer them only through an agreed secure handoff process.
- Retest the app, subscriptions, push notifications, sign-in providers, analytics, and core backend paths after the buyer receives control.
What buyers and sellers should document
A useful transfer plan explains both the assets and the open questions before money and access start moving.
What may need buyer and seller coordination
- App Store transfer initiation and acceptance, account team roles, banking or tax changes, subscription continuity checks, and app capability review.
- Source repository handoff, CI/CD access, signing material rotation, third-party service ownership, domain transfer, and support inbox transition.
Risks to resolve before close
- Apps with unclear ownership, missing source code, unresolved policy issues, fragile backend dependencies, or undocumented manual operations can be harder to transfer cleanly.
- Subscription, in-app purchase, entitlement, Game Center, Sign in with Apple, associated domain, and push notification behavior should be checked against the app's actual configuration.
Artifacts that support diligence
- App Store Connect screenshots or exports, payout history, analytics, crash reports, privacy notes, support volume, source access, build notes, and infrastructure inventory.
- A written transfer plan that names owners, timing, close conditions, remaining dependencies, and any post-close support the seller will provide.
iOS app transfer questions
Can every iOS app be transferred through App Store Connect?
No. Transfer eligibility depends on Apple's current requirements and the app's configuration. Buyers and sellers should review App Store Connect status, capabilities, subscriptions, agreements, and account requirements before relying on a transfer plan.
What should transfer besides the App Store listing?
Most acquisitions also require source code, build notes, backend services, domains, analytics, support tools, documentation, third-party service ownership, and a secure credential rotation plan.
How should sellers prepare an iOS app before listing it?
Sellers should organize revenue proof, App Store Connect context, source repositories, release instructions, infrastructure notes, privacy obligations, known risks, and a clear post-close support plan.
Does AppsVerified guarantee that an iOS app transfer will complete?
No. AppsVerified can help present listing details, proof artifacts, confidentiality controls, and transfer guidance, but Apple eligibility, buyer diligence, seller cooperation, and transaction outcomes remain the responsibility of the parties.