> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/hub/partner-change-with-360dialog.md).
# Partner change (with 360Dialog)
This document explains how to migrate a WABA to a new integration partner within 360dialog.
## Background
For security and billing reasons, a WABA can be associated with only one integration partner on the 360dialog platform at a time. You can view your current integration partner in **Client Settings**.\
\
**Before you start**
* The steps below must be completed by a client user.
* Have the **Partner ID** of the destination partner ready before beginning.
## How to change partners
The following actions must be completed by a client user.
{% stepper %}
{% step %}
Log in to the 360dialog Hub, then select **Channels** → **Change Partner**.
{% endstep %}
{% step %}
Select the **WABAs** to migrate
Partner changes apply **per WABA**. You can select one or more WABAs.
To migrate a single number, first move it to its own WABA, then migrate that WABA to the new partner.
{% endstep %}
{% step %}
Enter the **Partner ID** of the destination Partner.
If needed, create a new destination **client** account. If this option is selected, a new Client account will be created to receive the WABA.
{% endstep %}
{% step %}
Select the pricing plan and enter the payment method.
Note: The option to enter a payment method will only be presented if the Destination Partner is using Direct Billing.
Example plans only. Actual plan prices may vary by partner.
{% endstep %}
{% step %}
Continue and complete the registration.
The destination partner may have to approve the incoming request depending on their configuration.
{% endstep %}
{% endstepper %}
---
# 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.360dialog.com/docs/hub/partner-change-with-360dialog.md?ask=&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.
