> 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/moving-numbers-between-business-portfolios.md).

# Moving numbers between Business Portfolios

Learn how to migrate a phone number from one Meta business portfolio to another Meta business portfolio

{% hint style="warning" %}
Coex numbers cannot be migrated between Business Portfolios using this method.
{% endhint %}

## Prerequisites

* [x] Source & Destination Business Portfolio must be verified
* [x] Display name must be approved
* [x] 2FA must be disabled.
* [x] Access to the phone number to receive OTP via SMS or voice call.
* [x] The destination WABA can’t be in use by another Client
* [x] The number cannot be registered using Coexistence
* [x] You have admin access to both Business Portfolios

## How to migrate a number

Follow the process described [here](/docs/hub/migrations/migrate-a-phone-number-to-a-new-waba.md). 

{% hint style="info" %}
**Select destination Portfolio**

During the migration, make sure the destination Business Portfolio is chosen
{% endhint %}

<div align="left"><figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FcYBGK7OQ5V7WhzOEQknw%2Fimage.png?alt=media&amp;token=859a02e9-4cf4-46ff-b685-c5fde54d6d21" alt=""><figcaption></figcaption></figure></div>


---

# 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/moving-numbers-between-business-portfolios.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.