> 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

## **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.<br>
{% 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 three dots and start the migration.

<figure><img src="/files/gNP5qeQX1RXzrpGh6gPc" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Start Embedded Signup

Click the Embedded Signup button. It wil trigger the registration flow.&#x20;

<figure><img src="/files/CJ0gGlwyOxCrgDD8nApq" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Go through the Embedded Signup flow & Finish

Follow [these steps](/docs/hub/embedded-signup.md#select-business-assets) to finish the migration.&#x20;

{% 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 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.360dialog.com/docs/hub/migrations/migrate-a-phone-number-to-a-new-waba.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.