> 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.md).
# Migrations
## What is Migration?
In the context of the WhatsApp Business Platform, **migration** refers to the process of transferring a phone number from one WhatsApp Business account to another, without losing its messaging history, display name, or quality rating.
This process is typically used when:
* A business switches from one Business Solution Provider (BSP) to another
* A business wants to move a number from one WhatsApp Business Account (WABA) to another
* A business wants to change the currency of a WABA
Migration is only required if a phone number is already registered for the **WhatsApp Business API.**
The WABA currently hosting the number is called the **source WABA**, while the WABA receiving the number is called the **destination WABA**.
If the number is being used on the **WhatsApp Business App,** one of the following actions must be taken:
1. Onboard the number using [WhatsApp Coexistence](/docs/hub/embedded-signup/coexistence-onboarding.md), or
2. Delete the WhatsApp Business App account before proceeding to register the number for the WhatsApp Business API.
If the number is being used on the **consumer WhatsApp app**, there is no API migration process; instead, delete the WhatsApp consumer App account before proceeding to register the number for the WhatsApp Business API.
## Migration Scenarios
The scenarios below outline when a phone number registered for the WhatsApp Business API may need to be migrated or reassigned. Migrations involve moving the number between BSPs or WABAs. Internal configuration changes happen within the 360Dialog platform.
It is important to determine the correct migration path before starting the process.
| Scenario | Description |
| --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Migrate a number to 360Dialog](/docs/hub/migrations/migrate-a-number-to-360dialog.md) | Transfer a number from another BSP to 360Dialog while retaining its API registration on Meta. |
| [Migrate a number to a new WABA (with 360Dialog)](/docs/hub/migrations/migrate-a-phone-number-to-a-new-waba.md) | Transfer a number from one WhatsApp Business Account to another with 360Dialog. |
| [Migrate a number to an alternate BSP](/docs/hub/migrations/migrate-to-alternate-bsp.md) | Transfer a number from 360Dialog to a different BSP. |
| [Migrate a client to a new Partner (with 360Dialog)](/docs/hub/migrations/migrate-all-numbers-to-a-new-partner-with-360dialog.md) |
Transfer all numbers to another 360Dialog integration Partner. (Partner Change)
ie: Move 1 client account and all contained assets, WABAs and numbers, from 1 Partner to another.
|
| [Migrate a WABA to a new Partner (with 360Dialog)](/docs/hub/migrations/migrate-a-waba-to-a-new-partner-with-360dialog.md) | Transferring 1 WABA and all contained numbers to another 360Dialog Partner. |
| [Migrate numbers between Business Managers](/docs/hub/migrations/moving-numbers-between-business-portfolios.md) | Migrate a number from one Meta business portfolio to another. |
{% hint style="warning" %}
Each migration scenario has different conditions. Please review the checklist provided in each section.
{% endhint %}
## Impact on Assets
Asset
Migration
Configuration Changes
Display Name
✅ Yes
✅ No loss
Quality Rating
✅ Yes
✅ No loss
Messaging Limits
✅ Yes
✅No loss
Official Business Account Status
✅ Yes
✅No loss
Uploaded Media
✅ Yes
✅No loss
Approved High-Quality Message Templates
✅ Yes
✅No loss
Low-Quality, Rejected, or Pending Message Templates
❌ No
✅ No loss
Catalogs
❌ No
✅ No loss
Message and Chat History
❌ No
✅ No loss
## Templates
Templates are automatically duplicated in the destination WABA and initially granted the same status as their source counterparts.
After duplication however, templates are re-checked to ensure they are correctly categorized according to Meta [guidelines](https://developers.facebook.com/docs/whatsapp/updates-to-pricing/new-template-guidelines). This may result in some duplicated templates having their `status` set to `REJECTED`.
Only templates with both a `status` of `APPROVED` and `quality_score` of `GREEN` are eligible for duplication. If the destination WABA cannot accommodate all of the new templates, we will duplicate as many as we can until the destination WABA's template limit has been reached. Unduplicated templates must be re-created and submitted for approval if they are to be used by the destination WABA.
Note that **template quality ratings are not duplicated**. All duplicated templates will start with an `UNKNOWN` rating. This rating will remain for the first 24 hours, after which a new rating will be generated if sufficient data is available.
## Billing
Messages delivered before the migration is complete are charged to the old Solution Partner. Undelivered messages sent before migration is complete will be charged to the old Solution Partner if they are delivered after migration is complete. Messages delivered after migration is complete are charged to the business customer.
## Limitations
* Test business phone numbers issued by WhatsApp cannot be migrated.
* Business phone numbers must have an approved display name (`name_status` is `APPROVED`).
* Business phone numbers cannot have any associated pending display name change requests.
* Quality ratings of templates will **NOT** be migrated. All migrated templates will start with an `UNKNOWN` rating. This rating will remain for the **first 24 hours**, after which a new rating will be generated if sufficient data is available.
### Requirements aren´t met during the onboarding flow
During the onboarding flow, we check if the number meets the requirements for migration: If the **Meta Business Portfolio is verified**, **2FA is disabled**, and if the **display name is approved**. All three conditions must be met. If not, the following flow is triggered, and the number can be deleted, or another number can be chosen.
**Is your Meta Business Portfolio verified?**
**Is your 2FA disabled on your Meta Business Manager account?**
**Is your display name verified?**
If the answer to one of those questions is **No / Not sure** this screen will be visible
Once the customer clicks to re-onboard the phone number, a screen with the instructions will be presented.
Two options are available: delete the number or ask the previous BSP to take action.
Once it is done, please confirm so the onboarding flow will continue.
---
# 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.md?ask=&goal=
```
`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.