Migrating Your Business Number to the WhatsApp Platform
Picture the phone number printed on your delivery vans, stitched into your email signature, and saved in thousands of customers' contacts under your company name. Now imagine moving that exact number onto a more powerful messaging system without anyone noticing a hiccup. That is the quiet challenge of a number migration: keep the familiar number, gain new capabilities, and let your customers feel none of the plumbing happening behind the wall.
This guide walks through what it really means to bring a business number onto the WhatsApp Platform, the version built for sending notifications, running chatbots, and handling messages at scale. We will keep the language plain, the steps practical, and the focus on avoiding the small mistakes that cause big headaches. By the end you will know what to prepare, what to expect, and how to switch over with confidence.
Why move a number at all?
Most businesses start out on the free app, tapping out replies by hand. That works beautifully until it does not. One day the messages outnumber the people answering them, you want automated order updates to go out the moment a parcel ships, or you need several teammates handling the same number at once. The free app simply was not designed for that volume. The platform was.
Think of it as the difference between a personal mobile and a switchboard. Both make calls, but only one was built for an entire team. If you are weighing the two, our breakdown of the app versus the business platform lays out exactly where the line falls, and the comparison of the business app versus a personal account covers the rung below that.
The number itself is the prize worth protecting. It carries years of recognition. Customers trust it because they already know it. Migration lets you keep that trust intact while everything behind it gets an upgrade.
What "migration" actually means
Migration is the process of detaching a phone number from one WhatsApp environment and attaching it to another. In practice there are two common journeys. The first is moving a number off the free Business app and onto the platform. The second is moving a number that already lives on the platform from one provider's setup to another. Both share the same core idea: the number is verified, ownership is confirmed, and the old connection is released so the new one can take over.
The most important thing to understand is that you do not keep both running at once. A number can only be active in one place. When the migration completes, the old app or setup stops receiving messages on that number, and the new platform takes the reins. That is why timing and preparation matter so much. There is a switch-over moment, and you want it to be brief and well-rehearsed.
The chat history question
Here is the part that surprises people. Your historical chats do not travel with the number. Conversations stored on a phone stay on that phone; the platform starts you with a clean slate. This is not a flaw, it is simply how the two systems store messages differently. The practical lesson is to export or screenshot anything you truly need before you switch, and to tell your team that past threads will live in the old app, not the new dashboard.
Before you begin: a readiness checklist
Good migrations are boring migrations. The drama all happens in the preparation, so that the actual switch is uneventful. Walk through these before you touch anything.
| What to confirm | Why it matters |
|---|---|
| You can receive a code on the number | Verification sends a one-time code by SMS or call; you must be able to receive it. |
| A clear display name | The name customers see should match your real, recognisable brand to avoid review delays. |
| Business details ready | Verification may ask for company information, so have it on hand before you start. |
| A quiet window | Pick a low-traffic hour so the brief switch-over disrupts as few conversations as possible. |
| Exported chats you care about | History does not migrate, so save anything important first. |
If you have not yet stood up the platform side, our walkthrough of the WhatsApp Business Platform setup covers the groundwork you will want in place before the number actually moves.
The migration, step by step
Every provider wraps the process in its own dashboard, but the underlying journey is the same everywhere. Here is the shape of it in plain terms.
1. Confirm where the number lives today
First, know your starting point. Is the number sitting in the free Business app on someone's phone, or is it already on the platform under another setup? The answer changes one early step: a number on the platform usually needs to be released from its current home before it can be claimed elsewhere. A number on the free app needs to be disconnected from that app during the move.
2. Begin the request on the new side
On your chosen platform setup, you start a request to add the number. You enter the number, pick how you want to receive the verification code, and kick off the process. This is the moment you are formally saying, this number is mine and I want it here.
3. Verify ownership
A one-time code arrives by text or phone call. You enter it to prove the number is genuinely under your control. This step is the security gate; it stops anyone from hijacking a number that is not theirs. Keep the phone close and the code handy, because these codes expire quickly.
4. The switch-over
Once verified, the number activates on the new platform and goes quiet on the old one. This is the short window where the old app stops working for that number. In practice it is fast, often a matter of minutes, but it is real, which is why you chose a quiet hour. From here on, messages flow into the new system.
5. Rebuild what does not carry over
Now you reassemble the pieces that live on the platform rather than on the number itself. That includes your greeting and away messages, your automated replies, your team's access, and any chatbot flows. If you run a verified profile, you may also need to reapply for the green tick verification on the new setup, since it does not automatically tag along.
The templates trap and how to avoid it
Here is a snag that catches teams off guard. On the platform, any message you send to a customer who has not written to you recently must use a pre-approved template. These are the structured messages used for order updates, reminders, and the like. Crucially, your approved templates are tied to the setup they were created in. After a migration to a brand new environment, you may find yourself needing to recreate and resubmit them.
The fix is simple foresight. Before migrating, list every template you rely on. Right after the switch, recreate and submit them so they are ready by the time you need them. Our guides to message templates and their rules and to getting templates approved will save you from a frustrating wait when you least want one.
What happens to your sending limits
The platform controls how many people you can message in a rolling window, and that allowance grows as you prove you send messages people welcome. A fresh setup often starts at a lower tier and climbs as your quality holds up. If your number was already warmed up elsewhere, do not assume the new environment inherits that standing automatically; in some cases you build it up again. It is worth understanding how messaging limits and quality tiers work so a temporary cap does not catch you by surprise on day one.
The same logic applies to cost. Pricing is built around conversation categories rather than per-message charges, and migrating does not change those mechanics. If you want the full picture, our pricing explainer breaks down where charges actually land.
Keeping customers in the loop
Because the number does not change, most customers will never know a migration happened, and that is the goal. But there is a brief window during the switch-over where a message might not reach you. A short, friendly heads-up to your most active contacts, or simply choosing a genuinely quiet time, smooths that over. After the move, an automated greeting that confirms they have reached the right place reassures anyone who messages in those first hours.
This is also a good moment to revisit how you collect permission to message people. The platform takes a firm line on consent, so making sure your automation stays within the rules and that you are actively reducing spam complaints protects the standing you are about to build.
Common mistakes that derail a smooth move
Most migration trouble traces back to a handful of avoidable slips. Starting the request without being able to receive the verification code is the classic one; the code arrives, nobody is by the phone, and it expires. Forgetting that history will not transfer is another, leading to a scramble for old conversations after the fact. And underestimating templates, then discovering on a busy afternoon that none of your order updates can go out, is the kind of surprise that turns a calm migration into a stressful one.
If you are still deciding which provider to migrate onto, it pays to choose carefully, because moving again later is extra work. Our guide to choosing a business solution provider covers what to look for. More broadly, if messaging is one piece of a larger automation push, the principles in choosing an automation platform apply just as well.
A calm path forward
A number migration sounds intimidating, but at heart it is an orderly handover: prove the number is yours, release it from the old home, claim it in the new one, and rebuild the few pieces that live on the platform rather than the number. Prepare well, pick a quiet hour, line up your templates, and the whole thing becomes a non-event for everyone except you. If you would rather have a steady hand guide the move, you can always get in touch to talk it through.
Frequently asked questions
Will I lose my phone number during migration?+
Do my old chat conversations move with the number?+
How long is the switch-over, and will customers notice?+
Do I need to recreate my message templates after moving?+
References
- WhatsApp. "WhatsApp Business Platform documentation." business.whatsapp.com.
- Meta for Developers. "Phone Numbers and Migration." developers.facebook.com.