Moving Your WhatsApp Number From the Business App to the Cloud API
Short answer: You can keep the same phone number when moving from the WhatsApp Business app to the Cloud API, but plan it like any system change. Prepare a verified Meta business portfolio, an approved display name and a payment method, then decide between coexistence, where Meta's onboarding lets the number keep working in the Business app while it is also connected to the API, and a full migration, where the number leaves the app and only the API is used. Chat history behaves differently in each case, so back it up first. Pick an inbox tool or provider before switching, test everything on a second number, and switch at a quiet time with customers informed.
Why businesses make the move
The app has served you well, but now three people answer the same phone, you want booking confirmations sent automatically, and the conversations need to live in your CRM. Those are API territory. Keeping the existing number matters because it is printed on vans, flyers and your Google listing, and customers already have it saved.
Pre-move checklist
Work through this list before touching the number.
- Meta business portfolio (formerly Business Manager): create or locate it, and make sure at least two trusted people from your business are admins.
- Business verification: complete it with your legal company details. Unverified businesses face lower limits and some features are restricted.
- Display name: the name shown to customers must follow Meta's display name rules and relate clearly to your business. It is reviewed, so submit it early.
- Payment method: add one to the WhatsApp account, since template messages outside free windows are charged.
- Access to the number: you must be able to receive a verification code by SMS or voice call on that number during setup.
- Two-step verification: if the number has a PIN set in the app, you will need it, or you must turn it off before migrating.
- Templates drafted: prepare the first message templates (appointment reminder, order update) so they can be submitted as soon as the account exists.
- Website and links: list everywhere your WhatsApp link appears, in case anything changes.
Coexistence or full migration?
Meta has introduced onboarding that lets eligible Business app numbers connect to the Cloud API while staying active in the app. Availability, supported features and regions change, so check Meta's current developer documentation and your provider's guidance.
| Coexistence | Full migration | |
|---|---|---|
| Business app on the phone | Keeps working | Stops working for that number |
| API automation | Available | Available |
| Chat history | Recent history may be synced to the connected platform, depending on provider support | Stays on the old phone only, not transferred to the API |
| Best for | Owners who want to keep chatting from the phone while adding automation | Teams moving entirely to a shared inbox |
| Watch out for | Feature differences between app and API, two places to answer | Losing the convenience of the phone app |
If you choose full migration, delete the number from the Business app or follow the provider's migration flow so the number is free to register on the API. The number cannot be active on both through ordinary registration.
Chat history
This is the part people worry about most.
- Back up first: in the Business app, make a chat backup to Google Drive or iCloud before any change. It preserves your records even if you never restore them.
- Export key chats: for important customers or ongoing jobs, export chats to a file and store them with the customer record.
- Expect a clean start in full migration: API platforms do not import old app conversations in that case. Your inbox starts empty, and customers' next messages begin new threads.
- Coexistence: some history may be synced into the connected platform for a limited period. Check what your provider supports before relying on it.
Choosing an inbox tool or provider
The Cloud API itself has no chat screen. You either build one or, more commonly, use a provider or inbox tool connected through Meta's embedded signup. Compare options on:
- Shared inbox with assignment and internal notes.
- Template management and broadcast to opted-in lists.
- Integrations with your CRM, booking system or shop.
- Support for coexistence, if you want it.
- Where data is stored and whether a data processing agreement is available.
- How pricing works: platform fees on top of Meta's message charges.
Ask for a trial and test the specific workflows you need, not just the demo.
Test with a second number
Before moving your main number, register a spare number with the same provider and run through the real flows:
- Customer sends a message from a personal phone; does it arrive in the inbox and route to the right person?
- Agent replies within the customer service window; does the customer see the business name correctly?
- Send each template; are variables filled in correctly?
- Trigger an automation from your booking system or shop.
- Test opt-out handling.
- Check what happens outside office hours.
Fix problems here, where a mistake costs nothing.
Switch day plan
- Pick a quiet day and time, for example a weekday morning outside your busiest season.
- Tell regular customers a day ahead that replies may be slightly slower during a short window.
- Make the final backup in the app.
- Run the migration or coexistence onboarding with the provider, entering the verification code when it arrives.
- Send a test message from a staff member's personal phone straight away.
- Watch the inbox closely for the first few hours.
- Keep phone and email visible on your website as a fallback for the first week.
After the move
- Train staff on the new inbox: assigning chats, using notes, closing conversations.
- Submit remaining templates and track approval.
- Set up opt-in capture on forms so you can message customers properly.
- Review quality rating and messaging limits weekly during the first month.
FAQ
Will customers notice the change?
With the same number and display name, most will not. They may notice faster replies, structured messages or buttons in templates.
Can we go back to the app later?
You can usually remove the number from the API and register it in the app again, but history from the API platform will not appear in the app. Treat it as a deliberate decision.
Do we need a developer?
Not necessarily. Many providers handle onboarding with guided signup. A developer helps when you want custom automations connected to your own systems.
What happens to our catalogue and labels?
They belong to the Business app. Plan to recreate equivalents in your new inbox tool or shop integration.
Moving a busy number is easier with a checklist and someone who has done it before, so let us know your setup and we can plan the switch together.