The iOS App Handover Process: Step-by-Step Guide
Learn how to successfully navigate the iOS app handover process, covering Apple Developer account transfers and App Store Connect management.
The iOS app handover process involves two key phases: transferring the app's source code and project files to the client, and transferring app ownership through Apple's App Store Connect. To complete an apple developer account transfer, both the current and receiving accounts must hold active Apple Developer Program memberships, the app must meet Apple's eligibility criteria, and both parties must accept the app transfer agreement. This guide walks through the full mobile app development transition—from Xcode project handover to final App Store submission under new ownership.
What Is the iOS App Handover Process?
The iOS app handover process is the structured transfer of an iOS application from a development team to a client or new owner. It encompasses both the technical delivery of source code and assets, and the administrative transfer of app ownership through Apple's ecosystem.
A complete handover ensures the receiving party can independently build, maintain, and publish the app without dependency on the original developer. This involves an ios app source code handover, provisioning profile and certificate transfer, documentation, and the formal app store connect transfer app procedure.
- Source code repository access (Git URL, branches, tags)
- Xcode project structure and build schemes
- App bundle identifier and associated App IDs
- Signing certificates and provisioning profiles
- Third-party SDK keys (Firebase, Stripe, analytics, etc.)
- Backend API documentation and endpoints
- App Store metadata: screenshots, descriptions, keywords
- Push notification certificates (.p8 or .p12)
- CI/CD pipeline configuration if applicable
Preparing the Technical Handover Document
Before initiating any account-level transfer, the developer must prepare a comprehensive technical handover document. This document serves as the single source of truth for the client developer handover and reduces future dependency on the original developer.
The technical handover document should cover architecture decisions, third-party dependencies, build configurations, and deployment procedures. It must also include credentials for any backend services, API keys, and push notification certificates.
Store all credentials in a secure password manager or encrypted vault—never in plain text or unencrypted email.
Xcode Project Handover Best Practices
The xcode project handover is the technical foundation of the ios app migration. The receiving developer must be able to clone the repository, install dependencies, and run the app on a simulator and device without errors.
Ensure the repository includes a clear README with setup instructions, dependency installation commands (e.g., CocoaPods, Swift Package Manager, Carthage), and minimum Xcode and iOS version requirements. Clean up unused schemes, debug-only configurations, and hardcoded test credentials before handover.
- 1Tag the final release commit in Git (e.g., v1.0.0-handover)
- 2Clean the project: remove DerivedData, .xcuserstate, and personal signing identities
- 3Verify the project builds cleanly from a fresh clone on a separate machine
- 4Document the app bundle identifier, team ID, and any App Groups or associated domains
- 5Export a full Xcode archive and provide the .xcarchive file as a backup
- 6Include instructions for generating new signing certificates under the client's Apple Developer Program account
Apple Developer Account Transfer Requirements
Transferring app ownership apple requires meeting specific eligibility criteria. Apple enforces these rules to prevent fraud and ensure continuity for app users. To transfer app to another account, both the transferring and receiving accounts must have active Apple Developer Program memberships in good standing.
The app must have at least one approved version available on the App Store, and it must not be currently in review, pending a legal action, or using entitlements that prevent transfer. If you need to transfer ios app ownership, verify all prerequisites before initiating the request.
| Requirement | Details |
|---|---|
| Active memberships | Both sender and recipient need valid Apple Developer Program accounts |
| Approved app version | At least one version must be live on the App Store |
| No pending legal action | The app must not be under legal review or DMCA claim |
| Agreement acceptance | Both parties must accept the app transfer agreement |
| Two-factor authentication | Account holders must have 2FA enabled |
| Same app platform | Both accounts must support the same platform (iOS) |
If the app uses Apple Pay, push notifications, or Game Center, verify that the receiving account has the necessary capabilities configured before initiating the transfer.
How to Transfer App Ownership in App Store Connect
Once the technical handover is complete and both accounts meet the eligibility requirements, you can proceed with the app store connect transfer app process. This is the administrative step that officially moves the app to the new owner's account.
The transfer is initiated by the current app owner and must be accepted by the recipient within 30 days. During this window, the app remains available on the App Store without interruption. Follow this app store connect guide carefully to avoid common transfer errors.
- 1Log in to App Store Connect as the Account Holder of the current developer account
- 2Navigate to 'Agreements, Tax, and Banking' and accept the latest App Transfer Agreement if prompted
- 3Go to 'My Apps' and select the app you want to transfer
- 4Open 'App Information' under the General section and scroll to the bottom
- 5Click 'Transfer App' and enter the Apple ID and Team ID of the recipient's Apple Developer Program account
- 6Review the transfer summary, including app metadata, reviews, and in-app purchases
- 7Confirm and initiate the transfer—the recipient receives an email notification
- 8The recipient logs into their App Store Connect, reviews the transfer request, and clicks 'Accept'
- 9Apple processes the transfer (typically within minutes to a few hours)
- 10Verify the app now appears under the recipient's App Store Connect dashboard
In-app purchases, subscription groups, and app reviews all transfer with the app. However, the original account's sales and trends data will no longer be accessible to the new owner.
Post-Transfer Checklist for iOS App Deployment
After the apple developer account transfer completes, the new owner must reconfigure several components to resume ios app deployment under their own infrastructure. The app bundle identifier remains unchanged, but signing certificates and provisioning profiles must be regenerated.
The receiving developer should create new distribution certificates, provisioning profiles, and push notification keys under the new account. Any CI/CD pipelines referencing the old team ID or credentials must be updated accordingly.
- Generate a new App Store distribution certificate in the Apple Developer Program portal
- Create new provisioning profiles linked to the app bundle identifier
- Regenerate push notification certificates or .p8 keys
- Update App Store Connect users and roles for the new team
- Reconfigure analytics, crash reporting, or backend services with new team credentials
- Test submitting a new build to App Store Connect to verify the full pipeline
- Update any external integrations referencing the old Apple Team ID
Common Pitfalls in the Client Developer Handover
Even with a solid app store connect guide, teams encounter recurring issues during the ios app handover process. Being aware of these pitfalls helps both parties avoid delays and post-transfer breakage.
The most common issue is incomplete credential transfer—developers forget to hand over push notification keys, API tokens, or third-party service credentials. Another frequent problem is failing to regenerate signing assets promptly, which delays the first post-transfer app store submission.
- Missing or expired push notification certificates blocking new builds
- Third-party SDK licenses tied to the old account's bundle ID
- App Groups or Keychain Sharing entitlements not reconfigured under new team
- CI/CD pipelines failing due to stale team IDs or expired certificates
- RevenueCat, Stripe, or other service accounts still pointing to old developer
- Lost access to historical crash analytics and download data
If you encounter transfer eligibility issues, contact apple developer support directly—they can resolve account-level blockers that are not visible in the App Store Connect UI.
Conclusion
The iOS app handover process is a critical milestone in any mobile app development transition. By separating the technical deliverables—source code, signing assets, and documentation—from the administrative app store connect transfer app procedure, both developers and clients can ensure a smooth ownership transfer without disrupting live users. Whether you're a developer preparing to hand off a project or a business receiving an app, following this structured approach minimizes risk and preserves continuity. Need help executing a flawless ios app migration? TheDevs can guide you through the full handover—from Xcode project handover to App Store submission under your own account. Get in touch with our team today.
Frequently asked questions
How long does the iOS app handover process take?
The actual App Store Connect transfer usually takes up to two business days for Apple to process. However, the complete iOS app handover process, including sharing source code, provisioning profiles, and setting up new signing certificates, can take a few days to a week depending on the developer's responsiveness and the app's complexity.
What files are needed for a complete iOS app handover process?
Beyond transferring ownership in App Store Connect, the developer must provide the complete Xcode project source code, assets, and database structures. Crucially, the iOS app handover process also requires sharing signing certificates, private keys, and provisioning profiles so the new owner can compile and update the app independently.
Do app reviews and ratings transfer during the iOS app handover process?
Yes, when you use Apple's official App Store Connect transfer feature, the app retains its entire history. This means all current user reviews, ratings, and download statistics move seamlessly to the new account. This ensures the hard-earned reputation of the app remains intact throughout the iOS app handover process.
What happens to push notifications after an iOS app handover process?
Push notification certificates are tied to the original Apple Developer account. During the iOS app handover process, the receiving developer must generate new push notification certificates and update the app's server to use the new .p8 key or .pem files. Failing to do this will cause push notifications to stop working.
Is there a fee for the Apple Developer account transfer?
Apple does not charge a specific fee to transfer an app between accounts in App Store Connect. However, the receiving party must have their own active Apple Developer Program membership, which costs $99 per year. This membership is a mandatory requirement to accept the app during the iOS app handover process.
Can you transfer an app to a personal Apple Developer account?
Apple restricts app transfers based on account types. You cannot transfer an app from an organization account to a personal Apple Developer account. The receiving account must match the entity type or be an organization. Ensuring your account type is compatible is a critical step in the iOS app handover process to avoid rejection.
Related resources
Build it with TheDevs
Post what you want built and TheDevs starts your project — any tech work, one team.