> 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/agency-white-label/migrate-app-to-agency.md).

# Migrate app to agency

### How to migrate a live app to my white-label agency account?

If you have an app created outside your agency account, you can move it into your white-labeled platform using the in-app move function. This helps consolidate management without disrupting the app's configuration.

#### Step 1: Go to the app dashboard

* Log in to your AppMySite account
* Navigate to the app you want to migrate

#### Step 2: Open the settings

* From the app dashboard, click on Settings

#### Step 3: Locate the Move button

* In the header area, click the **Move** button
* A pop-up will appear to confirm the migration destination

#### Step 4: Select your agency or workspace

* From the list, select the **agency** you want to move the app to

#### Step 5: Confirm the move

* A second confirmation pop-up will appear
* Click **Move** to complete the migration

{% hint style="success" %}
This action moves the app into your agency account without changing its live status or setup.
{% 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/agency-white-label/migrate-app-to-agency.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.
