Changing your WhatsApp provider can feel like changing a shop’s front door. A provider change does not automatically require a new public number. This is not universal number portability. Under Meta’s current account model, the safer route is often to keep the number inside the WhatsApp account that owns it and change provider access. Prove ownership before accepting any migration promise.
The number and the provider are different things
Your customers know a phone number. Meta, however, also tracks the WhatsApp account that owns that number and the businesses or solution providers allowed to manage it. Those are separate layers.
- Identify the ownerFind the business portfolio and WhatsApp account that own the number.
- Confirm the access pathAsk how the new provider will receive supported access.
- Protect operating dataExport or rebuild conversations, contacts and rules that live elsewhere.
- Prove the cutoverTest inbound and outbound messages before removing old access.
Meta’s current phone number migration guidance says phone number migration is not supported for accounts on the new WhatsApp account model. It also says a destination account cannot claim a number it does not already own. Disconnecting the number does not make it freely movable.
That does not mean every business is trapped. Meta points to sharing the account that owns the number with the new provider. The familiar number stays attached while access changes. Older or exceptional setups may have another documented path, so the provider must inspect the actual account.
Start by proving what your business owns
Before signing, ask an administrator to open Meta Business settings and record the business portfolio, WhatsApp account and phone number identifiers. Confirm that the business controls administrator access, recovery email and billing.
Use the ownership questions in our WhatsApp API support guide and request evidence on screen. See where the number lives and who can grant partner access.
The official WhatsApp partner guidance explains that account sharing lets clients work with more than one provider or partner. That makes a controlled overlap possible in some setups. It is access sharing, not proof that the phone number moved to another account.
Choose sharing before assuming migration
Ask each provider to describe the handover in account terms. Will the current WhatsApp account be shared with the new provider? Which permissions will be granted? When will the old provider lose access? Who will remain the business administrator?
Run those questions during a provider onboarding test, before a busy campaign. A responsible provider should show the account relationship and name any step Meta must approve. If the plan creates a fresh account and pulls the same number into it, require current Meta documentation supporting that setup.
Plan for the things that may not follow
Keeping the number does not preserve every operational record. Conversations, contact notes, automations, templates, routing rules, media, analytics and invoices may live with the old provider. Decide what must be exported, rebuilt, archived or deleted.
Our guide to moving conversations without losing context separates history from channel access. If staff use the WhatsApp Business app, confirm how the provider works with the app and platform together. Do not assume the phone experience remains unchanged.
| Checkpoint | Evidence to collect | Safe decision |
|---|---|---|
| Account ownership | Business portfolio, WhatsApp account and admin view | Continue only when the business controls access |
| Provider handover | Written sharing path and permission list | Prefer supported account sharing where applicable |
| Operating data | Export list for conversations, contacts and rules | Rebuild or archive before old access ends |
| Customer continuity | Test messages and replies on the public number | Cut over only after both directions work |
Test one real conversation before the cutover
Choose a quiet hour. Stop nonessential campaigns, nominate one decision owner and send a test message from a phone that is not in the business team. Confirm the message reaches the intended shared inbox, a named person can reply, the customer receives that reply and the conversation retains the required context.
Test media and an approved template only if your operation uses them. Record evidence without customer data. Keep the old provider available until acceptance checks pass, then remove and verify its access.
Know when not to switch yet
Delay if no one can prove ownership, explain the sharing route, export required records or offer a rollback window. A discount is not worth risking the number customers trust.
For a neutral account review, talk to DripTell before changing permissions. Aim for a controlled access change that customers barely notice.
Frequently asked questions
Can I keep my WhatsApp number when changing providers
Often, yes, when the business retains the owning WhatsApp account and gives the new provider supported access. The route still depends on account model, ownership and provider setup.
Should the old provider release the number first
Do not disconnect anything merely on verbal advice. Current Meta guidance says disconnecting a number does not make it available to another account. Confirm the documented handover and recovery plan before removing old access.
Will my chat history move with the number
Not automatically. The channel number, provider inbox and business records are different things. Export or archive the conversations, contacts, notes and routing information your team must retain before the previous service ends.
How long should both providers overlap
Use the shortest controlled overlap that verifies access, messages, templates and team ownership. Define acceptance checks instead of choosing an arbitrary number of days.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
