> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/publishing-and-distribution/transfer-android-app.md).

# Transfer Android app

### Can you transfer your Android app from one developer account to another?

Yes, you can transfer your Android app from one Google Play Developer account to another without removing it from the Google Play Store. Follow the steps below to initiate an app transfer.

#### **Step 1: Gather Required Information**

Before submitting a transfer request to Google, ensure you have the following details:

* App package name – You can find this in your Google Play Console or AppMySite account under the Download App module.

{% embed url="<https://scribehow.com/shared/How_To_Download_and_Rebuild_Your_App__8h8Gx8BoTIqg8W0j2Kp3UA>" %}

* Transaction ID of your current developer account – This is the $25 payment transaction ID used to create your Play Console account.
* Transaction ID of the recipient’s developer account – The recipient must also provide their Google Play Developer account transaction ID.

#### **Step 2: Retrieve transaction IDs**

**Find your transaction ID:**

{% embed url="<https://scribehow.com/shared/Retrieve_Google_Play_transaction_ID__ZGmpRPjpRsy94X9uWQ34mg>" %}

* Log in to [**Google Payments** ](https://payments.google.com/)using the email ID associated with your Play Console account.
* Click on Activity tab from the header menu.
* Look for the $25 payment transaction titled "Google Play Developer" from when you created your Play Console account.
* Click on the Google Play Developer account activity.&#x20;
* From the right side menu, scroll down to find and note your transaction ID.

**Find the recipient’s transaction ID:**

* The recipient should log in to Google Payments using the email ID associated with their Play Console account.
* Repeat the steps above to find and note their transaction ID.

#### **Step 3: Submit a transfer tequest**

* Log in to your Google Play Console.
* Select the app you wish to transfer.
* Navigate to App Dashboard, where you’ll find the app name and package name.
* Fill out Google’s app transfer request form with the required details.
* Submit the request.

{% hint style="warning" %}
Transfer your Android app without removing it from the Play Store by submitting a **Google app transfer request** with your **package name and transaction ID**. The process is usually completed within **48 hours**.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/frequently-asked-questions/publishing-and-distribution/transfer-android-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.