1. Your app remains on the store during the transfer

You don’t need to take your app out of the App Store to transfer it to another developer account. Your users can also keep on downloading your app, as well as sending notes and reviews. Of course, they will also be able to download further updates even after the app has been transferred.  

Besides, there is no limit to the number of apps you can transfer, the only requirement is to transfer them one by one.  

The app transfer must be initiated by the Team Agent owner of the app. Apple defines the Team Agent as the person legally in charge of the app and owning the access to the iTunes Connect account where the app is published.  


To allow the transfer request, the recipient Team Agent must provide his Apple ID and Team ID to the Team Agent who initiates of the transfer.  

2. Requirements to transfer your app

To transfer your app to another developer account, you must meet a few requirements.  

First, your Apple Developer Account must not be pending for validation or modification, neither must be the account where the app is going to be transferred.


The status of the app must allow the transfer. Basically, it is any status in the list bellow (provided the app was published at least once before the transfer):  

3. Precautions before starting the transfer

Apple recommends to take a few precautions before starting the transfer of your app.  

Save the information you will need after your app is transferred such as: the Catalog Report (available on the homepage of the iTunes Connect account where the app is published), the dates of release of the app on the store, and also information regarding the sales and downloads of the app.  

Once this is done, you can request the app transfer.  

4. Requesting the app transfer

Go to your iTunes Connect account and click on “Manage Your Apps”; then select the app to be transferred. Click on “Transfer App”.  

Verify that the app meets all the requirements stated hereabove, and if it does, click on “Continue”.  


Check all the information, the terms of agreement, and select “I have read and agree to the agreement presented above.”

Then you can click on “Request for transfer” and on “Done” to come back to the app presentation page.  

During the time of the transfer, the app status doesn’t change, but the mention “Pending transfer” is added. You also have the possibility to modify the price of your app on the store during this period.  

5. On the recipient’s side

The recipient of the app must accept the transfer request withing 60 days. When the Team Agent of the recipient account log in to their iTunes Connect account, a notification informs them that an app is in pending transfer.  

In the message displayed, they must click on “Contract, Tax and Banking”

In the section Transfert Agreement, subsection “Contract in Process”, select the app in pending transfer and click on “Review”.  

Then fill the information about your app like in a regular submission, accept the terms of agreement and validate.  

The transfer can take up to 2 business days, and during this time the app status is “Processing App Transfer”.  

The discussions in progress in the Resolution Center will be closed, as well as the possibility to modify the app metadata.

Once the transfer is over, the app belongs to the recipient. It no longer appears in the initial account.  

6. Pay attention to the Push Notification feature

It is very important that the recipient of the app is well informed of every additional features of the app, so they can be maintained after the app is updated on the store.  

The best example is the Push Notification feature.

As you may already know, the SSL Push Certicate is created using the App ID of your app.  

The App ID is automatically transferred to the recipient’s Member Center at the same time the app is transferred to their iTunes Connect account.

However, the SSL Push Certificate associated to the App ID isn’t transferred. This is the reason why, in order to maintain the push notifications in the app, the recipient will have to create a new push certificate. 

Did this answer your question?