WhatsApp Business Platform

Migrate customers via Embedded Signup - WhatsApp

Updated: Aug 12, 2026
Copy for LLM
If you are a Tech Provider, you can use the API and Embedded Signup to migrate a client’s Messaging account from one Multi-Partner Solution (the “source solution”) to another (the “destination solution”).
As part of this process, a new Messaging account will be created for the client, templates within the source Messaging account will be duplicated in the destination Messaging account, and access to the Messaging account and its assets will be granted to the destination solution’s Solution Partner.

Requirements

Your app (or apps, if you are using separate apps) used to create or accept the source and destination Multi-Partner Solutions must be associated with the same business portfolio. The destination solution must also be in an Active state.

Templates

Templates are not duplicated automatically in this flow. You must duplicate them yourself using the Template Migration API, as described in Step 3 below. Duplicated templates are 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 Messaging account cannot accommodate all of the new templates, we will duplicate as many as we can until the destination Messaging account’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 Messaging account.
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: Instruct the customer to unshare their Messaging account and WhatsApp account

Instruct the customer to use the Meta Business Suite to unshare their Messaging account and WhatsApp account with your app. Ask them to:
  1. Access Meta Business Suite’s Business settings panel at https://business.facebook.com/settings/⁠.
  2. Navigate to Messaging Accounts.
  3. Unshare the Tech Provider app from the Messaging account intended for migration.
  4. Navigate to WhatsApp Accounts.
  5. Unshare the Tech Provider app from the WhatsApp account associated with the phone number.

Step 2: Instruct the customer to complete Embedded Signup

Instruct the customer to complete the Solution Partner’s implementation of Embedded Signup.
Make sure that you are directing the customer to the Embedded Signup implementation correctly configured with the destination Multi-Partner Solution ID, otherwise the customer could be onboarded via the wrong solution.
You can provide the customer with these instructions:
  1. Enter your existing business portfolio name in the business portfolio screen.
  2. Enter your existing business phone number in the phone number addition screen.
  3. Enter the existing WhatsApp account in the WhatsApp account selection screen.
  4. Complete the Embedded Signup flow.

Step 3: Use the Template Migration API to migrate templates to the newly created Messaging account

After the customer completes Embedded Signup and a new destination Messaging account has been created, migrate templates from the source Messaging account to the newly created destination Messaging account using the Template Migration API.
Before calling the API, make sure you have:
  • The source Messaging account ID, which is the account being migrated from.
  • The destination Messaging account ID, which is the account created by Embedded Signup.
  • A valid access token with the permissions required by the Template Migration API.
Call the API to duplicate the templates from the source Messaging account in the destination Messaging account.

Solution Partner steps

Provide the Tech Provider with a link to your implementation of Embedded Signup configured with the Multi-Partner Solution ID. Whenever a client completes your implementation’s flow successfully, onboard the client as you normally would, with one exception: do not register the phone number again.