Migrating a WABA from one Multi-Partner Solution to another via Meta Business Suite

Updated: Nov 14, 2025 You can use the API and the Meta Business Suite’s Business settings panel to migrate a business customer’s WhatsApp Business Account (WABA) from one Multi-Partner Solution (the “source solution”) to another (the “destination solution”). As part of this process, a new WhatsApp Business Account (WABA) will be created for the business customer, templates within the source WABA will be duplicated in the destination WABA, and access to the WABA and its assets will be granted to the destination solution’s Solution Partner. Note that both you and the destination solution’s Solution Partner must perform one or more API requests to complete the process.

Requirements

Your app (or apps, if you are using separate apps) used to create or accept each solution must be associated with the same business portfolio, and the destination solution must be in an active state.

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 our 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 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.

Tech Provider steps

Step 1: Tag the customer’s WABA for migration

Use the POST /<WHATSAPP_BUSINESS_ACCOUNT>/set_solution_migration_intent endpoint to tag the business customer’s WABA for migration. This generates a migration intent, which indicates your intent to migrate the WABA.

Request

curl 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;WABA_ID&gt;/set_solution_migration_intent' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer &lt;BUSINESS_TOKEN&gt;' \
-d '
\{
  "solution_id": "<DESTINATION_MULTI-PARTNER_SOLUTION_ID>"
}'

Response

Upon success:

\{
  "id": "&lt;MIGRATION_INTENT_ID&gt;"
}

Capture the migration intent ID.

Step 2: Send the migration intent ID and phone number to be migrated to your Solution Partner

Send the migration intent ID you just captured to the Solution Partner of your destination solution. They will need this ID to determine if the customer has accepted the migration request. In addition to this, share the phone number on the old WABA that you want migrated to the new WABA. This will be used in step 5 of the solution partner steps below.

Step 3: Disable two-step verification on the business phone number

If you have access to the business customer’s WABA in WhatsApp Manager, disable two-step verification on the business phone number associated with their WABA. Alternatively, instruct the business customer to do this on their own. You can provide them with these instructions: Access WhatsApp Manager at https://business.facebook.com/latest/whatsapp_manager/. Navigate to Account tools > Phone numbers, and click the phone number’s settings (gear) icon. If you don’t see your business phone number, click Overview in the menu on the left, then locate the number and click it. Click the Two-step verification tab. Click the Turn off two-step verification button and complete the flow.

Step 4: Instruct the customer to accept the request

Instruct the customer to use the Meta Business Suite to review and accept the request. You can provide them with these instructions: Access Meta Business Suite’s Business settings panel at https://business.facebook.com/settings/. Navigate to Requests > Received. Locate the request and click the Review button. Complete the flow.

When the customer completes this step, an account_update webhook indicating that a customer has been onboarded will be triggered and sent to both you and the destination solution’s Solution Partner. Note that an email from WhatsApp for Business ([email protected]) will also be sent to anyone who has admin access on the WABA, requesting review and acceptance of the request. The button in the email just loads the Business settings panel in a new window, so any WABA admin can review and accept the request.

Solution Partner steps

Step 1: Get the customer’s business token

Use the GET /<SOLUTION_ID>/access_token endpoint and request the business_id parameter to get an onboarded business customer’s business token.

Request

curl 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;SOLUTION_ID&gt;/access_token?business_id=&lt;CUSTOMER_BUSINESS_PORTFOLIO_ID&gt;' \
-H 'Authorization: Bearer &lt;SYSTEM_TOKEN&gt;'

The customer’s business portfolio ID is included in the account_update webhook triggered when the customer accepts the migration intent.

Response

Upon success:

\{
  "data": [\
    {\
      "access_token": "&lt;CUSTOMER_BUSINESS_TOKEN&gt;"\
    }\
  ]
}

Step 2: Get the status of the migration intent

Use the GET /<SOLUTION_MIGRATION_INTENT_ID> endpoint to get the status of the migration intent that the Tech Provider created. Your Tech Provider should provide you with this ID.

Request

curl 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;MIGRATION_INTENT_ID&gt;' \
-H 'Authorization: Bearer &lt;BUSINESS_TOKEN&gt;'

Response

Upon success:

\{
  "solution": {
    "name": "&lt;DESTINATION_SOLUTION_NAME&gt;",
    "status": "&lt;DESTINATION_SOLUTION_STATUS&gt;",
    "status_for_pending_request": "&lt;DESTINATION_SOLUTION_PENDING_REQUEST_STATUS&gt;",
    "id": "&lt;DESTINATION_SOLUTION_ID&gt;"
  },
  "status": "&lt;MIGRATION_INTENT_STATUS&gt;",
  "destination_waba": {
    "id": "&lt;BUSINESS_CUSTOMER_WABA_ID&gt;",
    "name": "&lt;BUSINESS_CUSTOMER_WABA_NAME&gt;",
    "currency": "&lt;BUSINESS_CUSTOMER_WABA_CURRENCY&gt;",
    "timezone_id": "&lt;BUSINESS_CUSTOMER_WABA_TIMEZONE&gt;",
    "business_type": "ent",
    "message_template_namespace": "&lt;BUSINESS_CUSTOMER_WABA_TEMPLATE_NAMESPACE&gt;"
  },
  "id": "&lt;MIGRATION_INTENT_ID&gt;"
}

If <MIGRATION_INTENT_STATUS> is ACCEPTED, it means the customer has reviewed and accepted the migration intent and you can proceed to the next step. If it’s any other value, do not proceed. Note that when a customer accepts the migration intent in the Meta Business Suite, an account_update webhook is triggered with status set to PARTNER_ADDED. Although the webhook won’t tell if the customer onboarded via the Meta Business Suite, you may wish to perform this query when you get one of these webhooks. Use the POST /<WABA_ID>/subscribed_apps endpoint to subscribe your app to webhooks on the business customer’s WABA. If you want the customer’s webhooks to be sent to a different callback URL than the one set on your app, you have multiple webhook override options. Note that <WABA_ID> should be the customer’s destination WABA ID.

Request

curl -X POST 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;WABA_ID&gt;/subscribed_apps' \
-H 'Authorization: Bearer &lt;ACCESS_TOKEN&gt;'

Response

Upon success:

\{
  "success": true
}

We are currently testing new steps for sharing your credit line with onboarded business customers. These steps will eventually replace this step, so if you wish to implement these steps now, see Alternate method for sharing your credit line. Use the POST /<EXTENDED_CREDIT_LINE_ID>/whatsapp_credit_sharing_and_attach endpoint to share your credit line with an onboarded business customer.

Request

curl -X POST 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;EXTENDED_CREDIT_LINE_ID&gt;/whatsapp_credit_sharing_and_attach?waba_currency=&lt;CUSTOMER_BUSINESS_CURRENCY&gt;&waba_id=&lt;CUSTOMER_WABA_ID&gt;' \
-H 'Authorization: Bearer &lt;SYSTEM_TOKEN&gt;'

Note that <CUSTOMER_WABA_ID> should be the customer’s destination WABA ID.

Response

Upon success:

\{
  "allocation_config_id": "&lt;ALLOCATION_CONFIGURATION_ID&gt;",
  "waba_id": "&lt;CUSTOMER_WABA_ID&gt;"
}

Step 5: Migrate the customers phone number to their new WABA

Use the POST /<WABA_ID>/phone_numbers endpoint to migrate the customer’s business phone number to the destination WABA. You should have received this from the Tech Provider in Step 2 of the Tech Provider steps. Note that <WABA_ID> should be the customer’s destination WABA ID.

Request

curl 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;WABA_ID&gt;/phone_numbers' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer &lt;BUSINESS_TOKEN&gt;' \
-d '
\{
  "migrate_phone_number": true,
  "cc": "&lt;BUSINESS_PHONE_NUMBER_COUNTRY_CALLING_CODE&gt;",// e.g. "91"
  "phone_number": "&lt;BUSINESS_PHONE_NUMBER_WITHOUT_COUNTRY_CODE&gt;", e.g. "8888888888"
}'

Response

Upon success:

\{
  "id": "&lt;BUSINESS_PHONE_NUMBER_ID&gt;"
}

Step 6: Register the customer’s phone number for use with Cloud API

Use the POST /<BUSINESS_PHONE_NUMBER_ID>/register endpoint to register the customer’s business phone number for use with Cloud API.

Request

curl 'https://graph.facebook.com/&lt;API_VERSION&gt;/&lt;BUSINESS_PHONE_NUMBER_ID&gt;/register' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer &lt;BUSINESS_TOKEN&gt;' \
-d '
\{
  "messaging_product": "whatsapp",
  "pin": "&lt;DESIRED_PIN&gt;"
}'

Response

Upon success:

\{
  "success": true
}

Did you find this page helpful? Thumbs up icon

ON THIS PAGE Requirements Templates Billing Tech Provider steps Step 1: Tag the customer’s WABA for migration Request Response Step 2: Send the migration intent ID and phone number to be migrated to your Solution Partner Step 3: Disable two-step verification on the business phone number Step 4: Instruct the customer to accept the request Solution Partner steps Step 1: Get the customer’s business token Request Response Step 2: Get the status of the migration intent Request Response Step 3: Subscribe to webhooks on the customer’s WABA Request Response Step 4: Share your credit line with the customer Request Response Step 5: Migrate the customers phone number to their new WABA Request Response Step 6: Register the customer’s phone number for use with Cloud API Request Response

Overview

Getting started

Business setup

Messages

Templates

Embedded signup

Flows

Calling

Groups

Payments

Catalogs

Marketing messages

Click to WhatsApp ads

Solution providers

API reference

Pricing

Policies

Other

Support

​Migrating a WABA from one Multi-Partner Solution to another via Meta Business Suite

​Requirements

​Templates

​Billing

​Tech Provider steps

​Step 1: Tag the customer’s WABA for migration

​Request

​Response

​Step 2: Send the migration intent ID and phone number to be migrated to your Solution Partner

​Step 3: Disable two-step verification on the business phone number

​Step 4: Instruct the customer to accept the request

​Solution Partner steps

​Step 1: Get the customer’s business token

​Request

​Response

​Step 2: Get the status of the migration intent

​Request

​Response

​Step 3: Subscribe to webhooks on the customer’s WABA

​Request

​Response

​Step 4: Share your credit line with the customer

​Request

​Response

​Step 5: Migrate the customers phone number to their new WABA

​Request

​Response

​Step 6: Register the customer’s phone number for use with Cloud API

​Request

​Response

Migrating a WABA from one Multi-Partner Solution to another via Meta Business Suite

Requirements

Templates

Billing

Tech Provider steps

Step 1: Tag the customer’s WABA for migration

Request

Response

Step 2: Send the migration intent ID and phone number to be migrated to your Solution Partner

Step 3: Disable two-step verification on the business phone number

Step 4: Instruct the customer to accept the request

Solution Partner steps

Step 1: Get the customer’s business token

Request

Response

Step 2: Get the status of the migration intent

Request

Response

Step 3: Subscribe to webhooks on the customer’s WABA

Request

Response

Step 4: Share your credit line with the customer

Request

Response

Step 5: Migrate the customers phone number to their new WABA

Request

Response

Step 6: Register the customer’s phone number for use with Cloud API

Request

Response