If you are a Tech Provider, you can use the API and Embedded Signup to migrate a business customer's 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.
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 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.
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 to a destination solution.
curl 'https://graph.facebook.com/<API_VERSION>/<WABA_ID>/set_solution_migration_intent' \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer <BUSINESS_TOKEN>' \ -d ' { "solution_id": "<DESTINATION_MULTI-PARTNER_SOLUTION_ID>" }'
Upon success:
{ "id": "<MIGRATION_INTENT_ID>" }
Capture the migration intent ID.
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, you can instruct the business customer to do this on their own. You can provide them with these instructions:
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:
Provide the Tech Provider with a link to your implementation of Embedded Signup configured with the Multi-Partner Solution ID. Whenever a business customer completes your implementation's flow successfully, onboard the business customer as you normally would.