The Good News and the Catch
Your WhatsApp number is not owned by your provider. It is registered to your WhatsApp Business Account (WABA), which belongs to your Meta Business Manager — which belongs to you. Providers connect to your WABA; they do not hold it hostage. Migration is a supported Meta process.
The catch is one specific scenario: if your provider created the WABA under their Business Manager rather than yours, you do not control it, and migration becomes their cooperation problem rather than your administrative task. Check this first, because it determines whether the rest of this guide applies to you.
To check: open Meta Business Manager, go to Business Settings, then Accounts, then WhatsApp Accounts. If your WABA is listed under your business, you are fine.
What Transfers and What Does Not
Transfers with the number:
- The phone number itself and its display name
- Your business verification status
- Your quality rating and messaging limit tier
- The green tick, if you have it
Does not transfer:
- Approved message templates. Resubmit on the new provider and wait for approval. This is the single biggest scheduling constraint.
- Automation flows and chatbots. Not portable between platforms. Rebuild.
- Conversation history. Export from the old provider before you leave — after cutover you may lose access.
- Contacts and custom fields. Export as CSV. Usually straightforward, but verify the export actually contains custom fields and tags.
- Team accounts, canned replies, tags, saved views. Recreate.
Note that quality rating and messaging tier do follow the number. Migration does not reset a bad reputation, and it does not cost you a good one.
The Migration Sequence
Step 1 — Confirm WABA ownership (before anything else)
As above. If the provider owns it, open that conversation with them now — it is the long pole. Some providers will transfer ownership on request; some make it difficult.
Step 2 — Export everything you will miss
Contacts with custom fields and tags, conversation history, template bodies (copy the exact text and variable structure), and a written description of every automation flow you will rebuild. Do this while you still have full access.
Step 3 — Set up the new provider in parallel
Create your account, connect it to your existing Meta Business Manager, and get as far as you can without registering the number. Import contacts, invite your team, rebuild flows, configure assignment rules.
Step 4 — Submit templates on the new provider and wait
Do this before cutover. Template review typically takes minutes to a few hours but can take longer, and cutting over with no approved templates means you cannot start conversations. Our template approval guide covers getting them through first time.
Step 5 — Pick a low-traffic window
There is a genuine gap between deregistering from the old provider and completing registration on the new one. It is usually minutes, occasionally longer. Choose your quietest hours and tell your team.
Step 6 — Deregister, then register
Remove the number from the old provider, then immediately register it on the new one. You will need access to the number for the verification code, so have whoever controls it standing by.
Do not skip the deregistration step and expect the new provider to take over. A number can only be active on one platform at a time, and attempting to register while still active fails.
Step 7 — Verify before you announce
Send a test inbound and outbound message. Confirm a template sends. Confirm webhooks are firing. Confirm agent assignment works. Then tell your team it is live.
Mistakes That Cause Real Outages
- Cutting over before templates are approved. You lose the ability to initiate conversations entirely until they clear. This is the most common self-inflicted outage.
- Cancelling the old subscription first. Keep it active until migration is verified. Losing access mid-migration removes your rollback path and your export access.
- Migrating during a campaign. Never during a broadcast, a sale, or your peak hours.
- No access to the phone number for the verification code at the moment you need it.
- Not exporting first. Conversation history is frequently unrecoverable once you leave.
- Assuming flows transfer. They never do. Budget rebuild time honestly.
Realistic Timeline
- Ownership check and export: a day, longer if the provider holds your WABA
- Parallel setup and flow rebuild: two days to two weeks, depending on automation complexity
- Template approval: hours to a couple of days
- The cutover itself: usually under thirty minutes
The cutover is the easy part. Everything before it is the work.
Frequently Asked Questions
Will I lose messages during migration?
Messages sent during the deregistration gap may not be delivered to either platform. Keep the window short and quiet. Customers who message during it will typically resend.
Do I lose my green tick?
No. Official Business Account status is attached to your WABA, not your provider. See the green tick guide.
Does my quality rating reset?
No — it follows the number. Migration is not an escape route from a low rating. If that is your motivation, read the quality rating recovery guide instead.
Can I test the new provider before migrating?
Yes — register a different number on the new platform and run it in parallel. This is the safest way to evaluate, and worth the small extra Meta cost.
What if my provider refuses to release my WABA?
Escalate through Meta Business Support. Ownership of a verified business's WABA should rest with the business. This is also the strongest argument for checking ownership at signup rather than at exit.
Check Ownership Today, Even If You Are Not Moving
The worst time to discover your provider owns your WhatsApp Business Account is when you want to leave. Spend five minutes in Business Manager confirming it is yours. If you are evaluating where to move, the provider comparison covers the field, and Tenreply connects to your existing WABA so your number and verification stay yours.