In this guide 6 sections
Switch when the provider owns your account, bills opaquely, blocks exports or cannot support the order updates and staff handovers you need. The number and display name can move. Approved templates usually follow the account. Chat history and your opt-in register rarely move on their own, so export them first and cut over in a planned window.
Signs the provider has become the problem
Slow tickets annoy everyone but rarely justify a move, so look for structural trouble instead, starting with who owns the account.
The clearest sign is that you cannot name the admin of the Meta business portfolio holding your number or reach anyone at the provider who can. Another is a bill that mashes Meta’s charge and the provider’s margin into one line, so you cannot tell what each message really costs. A third is a missing export button.
Also count the workarounds: if staff copy replies into a spreadsheet because the console cannot filter by tag, the tool has stopped fitting the work, which is reason enough.
- Account sits in the provider’s Meta portfolio
- Invoice does not split Meta charges from fees
- No export of chats, contacts or templates
- Integrations promised and never delivered
- Repeated template rejections with no explanation
What travels with the number
The phone number itself can be re-registered on a new provider’s connection, and the verified display name is tied to the account, so it normally follows the account. Approved message templates belong to the WhatsApp Business Account, so they move when the account moves and need resubmission when it does not.
Quality rating and messaging limit are attached to the number and account, so moving a healthy number usually keeps its standing, though read Meta’s documentation before cutover day.
Plan for a short gap. While the number is deregistered from the old platform and registered on the new one, inbound messages may fail to arrive at either end.
What stays behind and must be saved
Chat history lives in the provider’s database rather than on the number, and it stays there for good unless you ask for an export in writing. Ask for a full dump. It should carry message text, timestamps, agent names, contact IDs and the direction of every message, or the history cannot be searched later.
Your opt-in register is the bigger asset, because it records who agreed to hear from you, when, and through which form or chat. Without it you cannot show consent for the next template broadcast, and you may have to ask every contact again before sending anything.
Also copy labels, saved replies, chatbot flow diagrams and contact tags, because they are easy to forget and slow to rebuild from memory. Staff will complain on the first morning.
- Opt-in log with date and source
- Contact list with tags and notes
- Template names, text and variable order
- Chatbot flow diagrams and keyword triggers
- Saved replies and assignment rules
Plan the cutover so no message is lost
Pick a quiet window, such as a Sunday night for a shop that trades by day, and announce a short pause on every channel you use. Add a phone fallback.
Prepare the new platform first. Connect the CRM, load templates, import contacts and test with a spare number, sending one message through each flow such as order update, appointment reminder and support reply.
On cutover day the order is export, deregister, register, verify and send one live test, with the old contract kept alive for a short overlap. Plan for the breakage.
A switch checklist you can run on a single page
Write the steps in order and give each an owner and a time, then include the rollback: who decides, and where inbound traffic goes if registration fails.
Watch the first two days. Check delivery status on outbound templates, agent reply times and any quality warning that appears in Meta Business Manager, and compare each against the week before.
Then close the old account properly. Ask the previous provider in writing to delete stored chats once your export is verified and a sample opened, then keep their confirmation with your records.
Provider switch cutover sheet
A single page split into parts. The export list comes first, with a tick box for opt-in log, contacts, chats, templates, flows and saved replies. Next is a timed cutover plan with step, owner, start time and rollback trigger. Last is a post-move log of test sends, delivery status and quality rating.
Open a blank worksheet to printQuestions owners ask
Will I lose my approved templates if I switch?
Not if the account travels with you. Templates belong to the WhatsApp Business Account, so if your number sits in the provider’s account you must recreate them and resubmit each one under the new account.
Can I move the number without downtime?
Usually there is a short gap while the number is released from the old platform and registered again on the new one. Schedule it in a quiet window. Give customers a phone fallback meanwhile.
Do I need fresh opt-ins after a switch?
No, if the records are yours. Opt-in belongs to your relationship with the customer rather than the provider, so keep the register, import it, and ask again only for contacts missing from it.
How do I get my chat history out?
Ask the provider for an export in writing, naming fields such as message text, time, direction and agent, and check that media files and contact notes are included. If the console has no export button, request a database dump before you give notice, because the provider has less reason to cooperate afterwards.