How to Migrate from the WhatsApp Business App to the API
Short answer
To migrate from the WhatsApp Business app to the API, back up your chats and contacts, choose a platform, register your number with the API (which usually stops it working in the app), rebuild your quick replies as templates and saved replies, then announce the change and cut over during a quiet period.
Teams outgrow the WhatsApp Business app when more than one person needs to answer, or when they want automation and reporting. The move is straightforward, but it is a cutover, not a toggle. Plan it so customers never notice.
What changes when you move
| WhatsApp Business app | WhatsApp Business API | |
|---|---|---|
| Team access | Limited linked devices on one phone account | Any number of agents through a platform |
| Interface | The app itself | The platform you choose |
| Outbound messages | Broadcast lists and manual sends | Approved templates and campaigns |
| Automation | Basic away and greeting messages | Routing, workflows, AI agents |
| Chat history on the phone | Stored in the app | Does not automatically carry over |
For the full comparison see WhatsApp Business API vs app.
Before you cut over
- Back up chats. Export important conversations from the app. Message history generally does not transfer to the API, so keep an archive of anything you may need to refer back to.
- Export contacts to a spreadsheet, and note which have opted in to marketing messages.
- Save your quick replies and labels. You will recreate them in the new platform.
- Check your Meta business account and start business verification if you have not.
- Choose your platform. Use our buyer’s checklist.
- Decide on the number. Moving your published number keeps continuity, but it usually stops working in the regular app afterwards. Meta has been introducing options for some numbers to be used in both, so check current documentation for your region.
The cutover
- Pick a quiet period, such as an evening or a weekend morning.
- Warn customers in advance if you can: a status message or a note on your website is enough.
- Connect the number to your new platform following how to connect the WhatsApp Business API.
- Import contacts and apply labels.
- Recreate quick replies and submit message templates for approval. Do this before cutover so they are ready.
- Send a test message from another phone and reply from the new inbox.
- Have two team members watch the inbox closely for the first day.
After migration
- Set up assignment and routing so multiple agents do not collide.
- Add an out-of-hours message and working hours.
- Review response times daily for two weeks.
- Layer in automation gradually, starting with the questions you get most.
Common mistakes
- Migrating during peak hours.
- Forgetting that outbound messages after the 24-hour window need approved templates. See the 24-hour window.
- Not archiving old chats before the move.
- Messaging contacts who never opted in to marketing.
Frequently asked questions
Will I lose my WhatsApp chat history when I move to the API?
Chat history from the app generally does not carry over automatically, so export and archive anything you need first.
Can I keep using the WhatsApp Business app after migrating?
Traditionally the number stops working in the app once it is on the API. Meta has been adding options for some numbers to use both, so check current availability.
How long does migration take?
The technical steps can take under an hour. Allow extra time for business verification and template approval, and plan the cutover for a quiet period.
See it working on your own conversations
Resolvenyx puts WhatsApp, email, Instagram, Facebook and web chat in one inbox, with tickets and AI agents built in. 7-day free trial, no credit card required.
Written by the Resolvenyx team
We build a WhatsApp and omnichannel customer support platform, and write these guides from what we see support teams run into. Product details are checked against the current app. About Resolvenyx