Can your existing WhatsApp number move to the API?
This is the worry we hear most: "My customers know this number — will I lose it?" Short answer: the number can move. The longer answer depends on a few conditions, and the move involves a short interruption. Both are below.
Yes, your existing number can move to the API and customers keep seeing the same number. Three conditions apply: two-step verification must be off, the number's app account must be closed, and you must be able to receive the verification code at that moment. Chat history from the app does not move; Chatinbox runs the migration, Meta decides whether to accept the number.
What you provide
- A number that can receive an SMS or a call
- Confirmation that the number is yours
- A suitable time window for the move
What Chatinbox handles
- Checking the number's eligibility beforehand
- Running the migration steps for you
- Setting up team and flows afterwards
- The conditions to meet before migrating
- What carries over and what does not
- What interruption to expect
Three conditions before you move
Two-step verification is turned off
If the number has two-step verification (a PIN) enabled, the migration will not start. It is disabled in the app settings and set up again on the business account side afterwards.
The number's current use is resolved
If the number is currently used in the WhatsApp app or the WhatsApp Business app, that account has to be closed. This step cannot be undone: the chat history in the app does not move to the API.
Cannot be undoneThe number is verified
Meta sends a code to the number, by SMS or voice call. You need access to the number at that moment.
What carries over, what does not
Carries over
- The number itself
- The business name customers see
- Previously approved message templates
- The number's quality rating
Does not carry over
- Old chat history from the app
- Quick replies and labels from the app
- Product catalogue settings from the app
How long is the interruption?
There is a short gap between the old account closing and the number going live on the API. Messages sent during that gap do not reach you. That is why we schedule migrations outside busy hours. We do not promise a number of minutes, because the pace is set by Meta's processing — we plan around that instead.
If you want to keep the number active in the app as well, Meta offers a separate path for that. We work out which route fits you during the call.
Let's look at your number
In a 15 minute call we check its status and plan the migration.
Meta's migration flow can change. The conditions on this page were checked on 17 August 2026.
