Template migration | Developer Documentation
Prepare WhatsApp templates before an account change with ChatArchitect
If you plan to change a WhatsApp Business account, provider connection or sending integration, first ask ChatArchitect support which process applies. Confirm whether the Meta messaging account itself will change. A new CRM connection and a transfer between Meta accounts can require different checks.
Confirm the scope before making changes
- Identify the current and intended account, connected business number, account owner and sending tool. Provide account identifiers through the support channel when requested.
- Explain the proposed change and ask which steps ChatArchitect supports. Confirm whether templates need to be copied, recreated, submitted again or simply made available in another connected tool.
- Agree who performs each step, when sending selections can switch and what evidence will show that the destination is ready.
- Ask how pending attempts will be handled and what recovery options remain if a required template is unavailable. Do not assume the original account will remain usable after a number or provider change.
Record the templates and sending dependencies
Use the campaign template register to list every required version. Check the current entries in wtargeted.com and record:
| Item | What to preserve for checking |
|---|---|
| Template identity | Exact name, language, category, approved text and current status/quality. |
| Content | Variable order and source values, meaningful samples, configured buttons and their destinations. |
| Sending dependency | The sender, CRM, help desk or automation that selects the version, and the person responsible for its mapping. |
| Timing and history | Any confirmed delivery validity setting, pending attempt references and the period to which earlier campaign reports belong. |
| Destination result | The corresponding template and language in the intended account, their status and the result of a permitted test. |
This is a preparation record. It does not move an account or create destination templates. Keep language versions and failures separate so that an incomplete change is visible.
What Meta's template migration means
Meta's migration reference describes an API operation that recreates templates in a destination messaging account. For that operation, both accounts must belong to the same Meta business, and the source templates must be approved with an eligible quality score. Its response can contain both successful and failed templates.
Those API rules do not establish that ChatArchitect provides a customer migration button, supports every account change, or copies all templates automatically. Ask support to confirm the route for your case and explain any failures. Customer workflows use ChatArchitect App key and Secret; obtaining a Meta access token is not a step in this preparation guide.
Check the destination before switching sends
- Follow the process agreed with support. Review the outcome for each required template and language; completion of one version does not establish readiness of the others.
- Check the destination account and sender, current template text, language, category and approval. If recreation or a new submission was needed, use the review guide for a missing or rejected version.
- Check the selection and variable mapping in the connected sending tool. Test the received text and available button actions using the template test checklist.
- After the destination is verified and support confirms that switching is appropriate, update the agreed sending references and record the effective time. Keep earlier attempt and report references associated with their original account.
If a required version is missing or a test fails, keep affected workflows paused while support reviews the result. Preserve the source records and agree on recovery before deleting templates or removing a connection. If an old template must be deleted, follow the management guide after the dependent sends have been checked.
No comments to display
No comments to display