> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/the-podplay-system/overview-of-tiers/further-details-of-tiers/apple-developer-account/transferring-your-ios-app-to-your-apple-developer-account.md).

# Transferring Your iOS App to Your Apple Developer Account

### Overview

When moving your Club's iOS App to your [Apple `Developer` account](https://docs.podplay.app/owners-playbook/the-podplay-system/overview-of-tiers/further-details-of-tiers/apple-developer-account), the App is transferred from PodPlay's App Store Connect to yours. Apple requires two things:

1. PodPlay starts the transfer
2. Your `Account Holder` accepts it

The `Account Holder` is the person who signed up for your Apple `Developer` account and holds the authority to accept legal agreements for your organization. **Only that person can accept an App transfer**, so plan for them to be available for this step.

To start the transfer, send the Customer Success (CS) team two things:

1. **Your Team ID**
2. **The email address** of your `Account Holder`

#### Finding Your Team ID

1. Sign in to your Apple `Developer` account at [developer.apple.com/account](https://developer.apple.com/account)
2. Click "Membership details"
3. Copy the Team ID shown on that page

Once we has your Team ID and `Account Holder` email, we will initiate the transfer.&#x20;

Apple then places a transfer notice in your App Store Connect account for your `Account Holder` to accept.

{% hint style="warning" %}
**Only the `Account Holder` can accept the transfer.** An Apple Developer account has one `Account Holder` at a time. Because that role also carries authority to accept legal agreements for your organization, PodPlay does not ask you to hand it over. Your `Account Holder` completes the acceptance directly.
{% endhint %}

### Accepting the Transfer

These are the steps your `Account Holder` takes in [App Store Connect](https://appstoreconnect.apple.com) after we start the transfer (Apple's full reference is [Accept an app transfer](https://developer.apple.com/help/app-store-connect/transfer-an-app/accept-an-app-transfer)).

1. Sign in to [App Store Connect](https://appstoreconnect.apple.com)
   1. A notice indicates that an App is ready to be transferred
2. Go to the "Business" section of App Store Connect
   1. An App transfer alert appears in the Agreements section
3. Click "Review" under App Transfers on the right
4. Enter the new metadata:
   * Support URL
   * Marketing URL (required if the App previously had a marketing URL)
   * Privacy policy URL (required if the App previously had a privacy policy URL)
   * App Review contact information
   * App Store contact information
5. Choose to give all users on your App Store Connect team access to the App in the User Access section
   1. After the transfer completes, you can limit access to specific people
6. Review **and do not change** the privacy details in the [App privacy section](https://developer.apple.com/help/app-store-connect/manage-app-information/manage-app-privacy) that we set in place previously by clicking View Existing Details
   1. If you delete the existing responses you'll need to complete the [App privacy section](https://developer.apple.com/help/app-store-connect/manage-app-information/manage-app-privacy) before you submit a new App version
7. Read the terms
8. Select "I have read and agree to the agreement presented above"
9. Click Accept

### Metadata Values

Step 4 asks for the values that appear on your App's App Store listing and in App Store Connect. We will sends you the current values to enter so your listing stays consistent after the transfer.

The Support URL, Marketing URL, and Privacy policy URL are specific to your Club. The CS team pulls your Club's current values and provides them. The App Review and App Store contact information is the same across all PodPlay Clubs, and the CS team provides those values as well.

{% hint style="info" %}
If you are unsure what to enter in any metadata field, leave it and ask the CS team before you accept. Entering a value that does not match your Club's live listing can change what Customers see in the App Store.
{% endhint %}

### After the Transfer

Once your Account Holder accepts, the App moves into your Apple Developer account. Notify the CS team that the transfer is complete. The CS team then confirms the App is live under your account and coordinates any remaining access changes.

{% hint style="info" %}
At this point, if you don't already have a developer account with Apple, you may be asked to purchase one. The cost is $99 + tax (\~$107) /year.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/owners-playbook/the-podplay-system/overview-of-tiers/further-details-of-tiers/apple-developer-account/transferring-your-ios-app-to-your-apple-developer-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
