WhatsApp Business Account - Migration Intent Details API | Developer Documentation

Check the outcome of an agreed number change

Use this acceptance checklist after support and the responsible teams have carried out an agreed number or provider change. Start with the change plan for the approved scope and recovery arrangements. A Meta migration-intent status is not by itself proof that your connected CRM or application works.

Compare the result with the agreed scope

• The business number, intended account and new connected tool/workspace.
• The route that should receive incoming chats and show outgoing results.
• The previous connection and scheduled workflows: which should remain, stop or be replaced.
• Any required WhatsApp Business app operation on the same number.
• The responsible people, acceptance time and supported next step if a check fails.

Use the routing inventory and labelled account references to compare the actual result with the agreed record. Keep uncertainty about ownership, history, templates and app synchronization explicit; a number continuing to exist does not establish their transfer.

Test the new route and the previous dependencies

1. With a permitted contact, send an incoming message to the intended business number. Check the actual destination conversation/receiver.
2. Send an appropriate reply through the agreed new tool. Verify the business sender seen by the contact and the result for that attempt.
3. Check the templates currently available for this connection using the template workflow; do not infer that the old collection or its status carried over.
4. Ask the owners of the former workflows to confirm the agreed state of their queues, jobs and receivers. Avoid two active workflows sending the same reply.
5. Check customer contact links and any required app operation in the changed setup, using the appropriate connection instructions.

Close or escalate the change with evidence

Record pass/fail for each agreed check, with the actual route and attempt references. A completed connection form, available account or provider status should be recorded as its own checkpoint, not as a substitute for messaging tests.

If a check fails, preserve the evidence and use the recovery/escalation route agreed with support. Do not initiate another migration or delete the previous account by guessing a reversal procedure. The connection-readiness guide helps describe an unfinished setup; the supported return route and guarantees need confirmation for the particular change.