> 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/migrations/migrate-a-phone-number-to-a-new-waba.md).
# Migrate a phone number to a new WABA
This document explains how to migrate a phone number from one WABA (source WABA) to another (destination WABA) with 360Dialog.
## **How to migrate a phone number to a new WABA**
{% stepper %}
{% step %}
### Disable 2FA
Disable [2FA](https://docs.360dialog.com/docs/resources/phone-numbers/2fa)
{% endstep %}
{% step %}
### Select the channel (phone number)
[Log in](https://app.360dialog.com/) to the 360Dialog hub. In the **channel section**, choose the particular channel you want to update.
{% endstep %}
{% step %}
### Start Migration
The navigation bar at the top of the page has a **"Detail"** section. Scroll down to the **Meta Business Settings**. Click the “Migrate number” button and start the migration
{% endstep %}
{% step %}
### Start Embedded Signup
Click the Embedded Signup button. It wil trigger the registration flow.
{% endstep %}
{% step %}
### Go through the Embedded Signup flow & Finish
Follow [these steps](/docs/hub/embedded-signup.md#select-business-assets) to finish the migration.
{% hint style="info" %}
**Create new WABA**
Use clear and distinct WABA names to minimize errors. Note the existing WABA ID and name before creating a new one to ensure easy differentiation during the migration process.
{% endhint %}
After the migration is complete, verify the transfer by checking the number’s status in its source WABA within WhatsApp Manager. If the status shows as “**transferred**,” the migration was successful.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
**Limitation**
COEX numbers can´t be migrated between WABAs
{% 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.360dialog.com/docs/hub/migrations/migrate-a-phone-number-to-a-new-waba.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.
