How to Move from WhatsApp Business App to the API (2026 Guide)

Migrating from the WhatsApp Business App to the WhatsApp Business API gives you a multi-agent inbox, CRM integration, template messaging, and AI automation. Your phone number stays the same. With Meta's Coexistence feature (available since 2025), you can now run both the App and the API on the same number simultaneously, making migration smoother than ever.

Not sure if you need the API yet? Read our WhatsApp Business App vs API comparison first.

The WhatsApp Business App got you started. But if you have more than one person replying to customers, or you want to connect WhatsApp to your CRM, or you want an AI assistant handling enquiries, you need the API.

Here's everything you need to know before making the switch.

Why upgrade to the API?

The free WhatsApp Business App is fine for a one-person shop. Once you grow past that, you hit walls. And you probably already know exactly which walls we are talking about.

Picture this. You have three staff handling customer enquiries, but only one phone with WhatsApp Business on it. Someone is always waiting for the phone. Or worse, you link it to WhatsApp Web on four laptops, but everyone can see every conversation, nobody knows who is handling what, and someone accidentally replies to a customer that another colleague was already dealing with. It is chaos, and your customers can tell.

The app also has no scheduling. You cannot queue up appointment reminders to go out tomorrow morning. You cannot send a follow-up message three days after a quote. You have to remember to do it manually, and things slip through the cracks. On the broadcast side, you can send to 256 contacts at a time, but you cannot see who actually read your message. No read receipts for broadcasts. You are basically sending messages into the void and hoping for the best.

What the API gives you:

• Multiple team members in one inbox (no more sharing one phone)
• Every message tagged to a specific person. Accountability.
• CRM integration. Customer history in one place.
• Template messages. Send appointment reminders, follow-ups, and promotions at scale.
• Scheduled and automated messages that go out without you lifting a finger
• AI assistants like chatavocado that reply 24/7

Faster replies directly correlate with more bookings. Here's the data on why speed matters.

What you can't do with just the app:

• Let three staff reply from the same number without passing a phone around
• Track who said what to which customer
• Send bulk messages without getting banned
• See read receipts or delivery reports for broadcast messages
• Schedule messages to go out at a specific time
• Automate anything beyond basic quick replies
• Connect your WhatsApp to a CRM, booking system, or any other tool

If you have hit even two of these limitations, you have outgrown the app.

What happens to your number and chats

This is the part most business owners worry about, so let us be very clear about what stays and what goes.

What follows your number to the API:

• Your phone number stays the same. Your customers do not need to save a new contact or do anything at all.
• Your display name and profile picture carry over.
• Your verified green tick (if you have one) transfers to the API. You do not need to reapply.

From your customers' perspective, nothing changes. They message the same number, they see the same name and profile picture, and everything feels exactly the same. The only difference is that you now have a proper system behind the scenes.

What you lose:

• Pre-existing chat history does not carry over automatically. Your old conversations will not appear in the new system unless you export them first. With coexistence, new messages sync across both platforms going forward.
• Update (March 2026): You can now use both the App and the API on the same number at the same time, thanks to Meta's Coexistence feature. This means you no longer have to choose one or the other. You can transition gradually.
• Group chats do not sync between App and API. The API's group support is limited (requires Official Business Account status and 100K daily conversations, max 8 participants). If you rely on group chats with customers, keep using the App for those while handling 1:1 conversations through the API.

This is why you need to export your chats before migrating. Do not skip this step.

How to export your chats before you migrate

Update (March 2026): If you use Meta's Coexistence feature, you can run both the App and API simultaneously, so your App chat history stays accessible on your phone. However, pre-existing chats do not sync to the API platform, so exporting important conversations is still a good idea.

If you are doing a full migration (not using coexistence), do this BEFORE you start. Once you switch to the API without coexistence, your chat history in the app is gone. There is no undo button.

Prioritise your most valuable chats first. You probably do not need to export every single conversation. Start with your top customers, any ongoing deals or quotes, and any chats that have important details you might need to reference later (like agreed prices, special requests, or delivery instructions). Work your way down from there.

From your phone (manual):

1. Open WhatsApp Business
2. Go to a chat you want to save
3. Tap the contact name at the top
4. Scroll down to "Export Chat"
5. Choose "Include Media" or "Without Media"
6. Save to Google Drive, email, or your files

You'll get a .txt file with all messages and timestamps. If you included media, you'll also get the photos and documents.

The catch: You have to do this one chat at a time. Each export takes about 2 minutes, including the time to select the chat, choose your export options, and wait for the file to upload. If you have 50 important customer chats, budget about two hours. If you have 200, set aside a morning for it.

Tip: Choose "Without Media" for most chats unless you specifically need the photos and documents. Media exports take longer and create much larger files. You can always export a few key chats with media and do the rest as text only.

Advanced method: Third-party tools can bulk-export chats. But be careful with data privacy. Make sure any tool you use is compliant with PDPA if you're handling Singapore customer data, or PDPA Malaysia if you are based there.

Understanding template messages

Once you're on the API, you can't just message customers whenever you want. WhatsApp has rules, and understanding them early saves you money and frustration.

The 24-hour window: When a customer messages you, you have 24 hours to reply freely. You can send anything you want during this window, no templates needed. After 24 hours, you need to use a pre-approved template to re-open the conversation.

Template categories:

• Utility: Order confirmations, appointment reminders, shipping updates. Lowest cost.
• Authentication: OTP codes and verification. Also low cost.
• Marketing: Promotions, offers, re-engagement. Highest cost.

Real-world template examples by industry:

For a dental clinic or GP: "Hi {{name}}, this is a reminder that your appointment is on {{date}} at {{time}}. Reply YES to confirm or CHANGE to reschedule." This is a utility template and costs the least.

For a tuition centre or enrichment class: "Hi {{name}}, just a reminder that {{child_name}}'s class is tomorrow at {{time}}. Please let us know if your child will not be attending." Also utility.

For a cleaning or home services company: "Hi {{name}}, your cleaning session is confirmed for {{date}}. Our team will arrive between {{time}}. Please make sure someone is home to let us in." Utility again.

For a retail shop or F&B business running a promotion: "Hi {{name}}, we have a special this week: 20% off all items in store until Sunday. Show this message at checkout to redeem. Reply STOP to opt out." This is a marketing template and costs more.

Tips for getting templates approved:

• Be specific. "Hi {{name}}, your appointment is on {{date}} at {{time}}" works. Vague messages get rejected.
• Don't try to sneak marketing into utility templates. WhatsApp will reclassify them and charge you more.
• Include an opt-out option in marketing templates. Something like "Reply STOP to unsubscribe" at the end.
• Keep templates short and clear. WhatsApp reviewers check them manually, and overly long or confusing messages get rejected more often.

New billing from July 2025

WhatsApp changed how they charge for API messages in July 2025. This has already happened, so if you are migrating now, this is the pricing model you will be on from day one.

The old model charged per conversation, where a 24-hour window counted as one conversation regardless of how many messages were exchanged. The new model charges per template message sent. Messages within the 24-hour customer-initiated window remain free.

What this means for you in practice:

• Utility messages (appointment reminders, order confirmations) are cheaper than before
• Marketing messages (promotions, offers) cost more per message
• You pay for each template message sent, not per conversation
• Messages within the 24-hour customer-initiated window remain free, so responding to incoming enquiries costs nothing

Practical cost examples for Singapore: If you are a clinic sending 500 appointment reminders per month, that is roughly SGD $25 to $40 in utility template costs. If you are a retail business sending 500 marketing messages per month, expect SGD $75 to $100. A typical SME that sends a mix of reminders and the occasional promotion usually lands between SGD $50 and $150 per month for messaging costs alone. That is on top of whatever your platform or BSP charges.

The good news is that most customer-initiated conversations are free. If a customer messages you to ask a question and you reply within 24 hours, you pay nothing. This means businesses that get a lot of inbound enquiries often spend less than they expect.

Three ways to migrate

Option 1: DIY through Meta

Apply for API access through Meta Business Suite. Set up a Business Manager account, verify your business, and configure everything yourself.

Cost: Free for the setup. You only pay WhatsApp's per-message fees.

Timeline: 1 to 3 weeks, sometimes longer. The business verification step with Meta can be unpredictable. Some businesses get verified in 2 days. Others wait 3 weeks and get asked for additional documents.

Pros: No monthly platform fee. Full control over your setup.

Cons: You need a developer or someone very technical. There is no inbox included, so you still need to build or buy one. No AI, no CRM, no automation out of the box. If something breaks, you are on your own.

This option only makes sense if you have a tech team and want to build a fully custom integration.

Option 2: Use a BSP (Business Solution Provider)

Companies like Twilio, 360dialog, or MessageBird handle the technical setup and give you API access through their platform.

Cost: Typically SGD $50 to $200 per month for the platform, plus WhatsApp's per-message fees.

Timeline: 3 to 7 days on average. BSPs have established relationships with Meta, so verification tends to go faster.

Pros: Handles the technical complexity for you. Usually comes with an inbox or integrates with popular CRM tools.

Cons: You still need to configure the inbox, set up templates, train your staff, and manage the system yourself. Most BSPs do not include AI or automation. You are paying for infrastructure, not a complete setup.

This option is good if you have a tech team that can manage the integration and you want flexibility to customise.

Option 3: Let chatavocado handle it

Other BSPs give you API access and walk away. We migrate you AND build the AI that answers your customers from day one.

We do the migration for you. We set up your API access, configure your number, build your AI assistant, and get you live in days. The AI handles enquiries, bookings, and follow-ups from day one. Here's exactly what the AI does. No technical work on your end.

Cost: Starts from SGD $199 per month, which includes the platform, AI assistant, and shared inbox. WhatsApp's per-message fees are separate.

Timeline: 2 to 5 days from start to live.

Pros: Everything handled for you. AI assistant from day one. Multi-agent inbox included. Your staff can start using it immediately with minimal training.

Cons: Less customisation than a fully DIY setup. You are using our platform rather than building your own.

This is what most of our Singapore and Malaysia clients choose because they would rather focus on their business than wrestle with API configurations.

Migrating multiple locations or branches

You started with one number. Now you have three outlets, maybe five. Each branch has its own phone with WhatsApp Business on it. Customers WhatsApp you about bookings, but they message whichever number they saved, and sometimes that is not the branch they actually want. Staff at one outlet cannot see what the other outlet promised. You are outgrowing the WhatsApp Business App, and adding more phones is making it worse, not better.

This is the most common pattern we see with Singapore businesses that have multiple branches. A cleaning company with teams in the east and west. A tuition centre with three locations across the island. A clinic group with outlets in Tampines and Jurong. It always starts the same way: one number worked fine, then they expanded, and now nobody has the full picture.

Before you migrate, you need to make one big decision.

One number with routing, or one number per branch?

One number for the whole business: Every customer messages the same number. Your team (or your AI employee) figures out which branch they need and routes them accordingly. Customers only need to save one contact. Simpler for them.

• Works well if your branches offer the same services and customers do not strongly identify with one location
• Easier for marketing. One number on all your flyers, your website, your Google listings
• Requires good routing logic so messages reach the right team. Without it, you get confusion

One number per branch: Each outlet gets its own WhatsApp number on the API, all under one WhatsApp Business Account. Customers message the branch they want directly. Staff see only their branch's messages.

• Works well if each branch is different. Different menus, different services, different staff
• Customers already have a relationship with a specific outlet. Changing to one central number confuses them
• More numbers to manage, but each inbox stays focused

Most Singapore businesses with 3 to 5 branches choose one number per branch. Their customers already have the branch number saved. Forcing everyone onto one number creates unnecessary friction. See how a bar group runs 3 branches from one inbox with separate numbers per location.

Migration sequence: start with the quietest branch

Do not migrate all branches at once. And do not start with your busiest outlet. Start with the branch that gets the fewest messages. This gives your team time to learn the new system without the pressure of 50 customers waiting for replies.

A good sequence looks like this:

1. Migrate your quietest branch first. Get staff comfortable with the new inbox. Work out any issues.
2. Run it for one to two weeks. Note what your staff finds confusing or what needs adjusting.
3. Migrate the second branch. Apply what you learned from the first.
4. Migrate the busiest branch last, when your team already knows the system.

Use Meta's Coexistence feature during this process. Each branch can run both the App and the API on the same number simultaneously, so you are never fully cutting over until you are ready.

What stays the same across branches. What differs.

Keep consistent across all branches:

• General business policies: cancellation terms, deposit requirements, refund rules
• Pricing (if the same across outlets)
• Brand tone and messaging style
• AI knowledge base for company-wide FAQs

Customise per branch:

• Operating hours and address
• Staff names and roles
• Services or menu items specific to that outlet
• Google Maps link and directions
• Branch-specific promotions

If you are setting this up yourself, you need to configure each branch's details separately in whatever inbox or CRM you are using. For businesses with 3 or more locations, this is where the setup time adds up fast.

We have set up multi-branch WhatsApp for 57 businesses across Singapore and Malaysia.

On our Enterprise plan, we handle the entire multi-location setup for you. One onboarding, all branches configured, AI trained on each outlet's specific details. Talk to us about your branches.

Already on the API? Switching from another provider

You already made the move to the WhatsApp Business API. You set it up through a BSP. It worked. For a while.

Now it does not. Maybe you are paying monthly for a system you still have to manage yourself. Maybe your support tickets take three days to get a reply. Maybe the setup worked fine for one location, but you have added two more branches and the whole thing is falling apart. Whatever the reason, you are looking for something better.

Switching providers is not the same as migrating from the App. The process is different, and there are things that can go wrong if you do not plan for them.

What actually happens when you switch BSPs

Number porting. Your WhatsApp number moves from your current provider to the new one. This is a standard process through Meta's systems. The actual transfer typically takes a few hours, not days. During those hours, your number is in limbo. Messages sent to you during the switch may not come through.

Template re-submission. Your approved message templates do not transfer automatically. You need to re-submit them with your new provider. Most templates that were approved before will get approved again, but it is not guaranteed. Meta reviews each submission fresh. Budget 24 to 48 hours for approvals, sometimes longer for marketing templates.

Conversation history. Here is the part nobody likes to hear. Your chat history with your current provider does not come with you. Those conversations live in your current provider's system. You can export them if your provider allows it, but they will not appear natively in your new inbox. This is the same limitation as migrating from the App. Export anything important before you switch.

Webhook reconfiguration. If you have integrations (CRM, booking system, payment notifications), those webhook endpoints need to point to your new provider. This is the most technical part of the switch and where most things break if you rush it.

What goes wrong during a provider switch

The gap. There is a brief period during number porting where messages may not come through. It usually lasts a few hours. But if a customer messages you during that window, you might miss it. They will not get an error. Their message will just disappear.

Template rejections. A template that was approved with your old provider might get rejected on resubmission. This happens more with marketing templates. If your appointment reminders or booking confirmations are rejected, you cannot send them until you fix and resubmit. That can leave you without automated messages for a day or two.

Customers messaging during the switch. Your regular customers do not know you are changing providers. They will message you at their usual times. If you switch at 2pm on a Tuesday, you will miss messages from your busiest hours.

How to minimise downtime

1. Schedule the switch during your quietest hours. For most Singapore service businesses, that is late night or early morning. If your enquiries slow down after 10pm, start the porting process then.
2. Have your new provider fully set up before you port. Inbox configured. Templates submitted (they can be submitted before the number is ported). Staff trained. AI assistant ready. The moment the number lands, you should be live.
3. Re-submit your templates early. Submit your most critical templates to the new provider days before the switch. Get them approved first. Do not wait until porting day to find out your booking confirmation was rejected.
4. Export your conversation history. Do this before you disconnect from your current provider. Once you leave, access to those conversations depends entirely on your old provider's export policies.
5. Tell your team. Everyone who handles customer messages needs to know when the switch is happening, where the new inbox is, and what to do if something looks wrong.

On the Enterprise plan, we coordinate the entire switch. We handle the number porting, template resubmission, webhook setup, and inbox configuration. You keep running your business. The transition happens in the background, and we aim for the shortest possible gap. Talk to us about switching.

Common mistakes during migration

We have helped enough businesses migrate to know the most common pitfalls. Avoid these and your transition will be much smoother.

1. Forgetting to export chats before switching. This is the number one mistake. Once you activate the API on your number, your WhatsApp Business App chat history is gone. We have seen business owners realise this a week after migration, and by then it is too late. Export your important chats first. Do it before you even start the migration process.

2. Not training staff on the new inbox. The API does not come with the WhatsApp Business App. Your staff will use a different inbox, whether that is chatavocado, a BSP platform, or something custom. If you switch on a Monday without showing your team how the new system works, you will have confused staff and slow replies all week. Spend 30 minutes walking everyone through it before you go live.

3. Sending marketing templates without opt-in. WhatsApp takes spam seriously. If you blast marketing messages to contacts who did not opt in, your number's quality rating drops, your sending limits get reduced, and in the worst case your number gets banned. Always make sure customers have agreed to receive marketing messages from you. Utility messages (like appointment reminders) are generally fine if the customer has an existing relationship with you.

4. Not having AI or automation ready from day one. The whole point of moving to the API is to upgrade your customer communication. If you migrate but then just have your staff manually replying the same way they did before, you have gone through all the effort for very little benefit. Set up at least basic automation, like auto-replies outside business hours and an AI assistant for common questions, before you go live.

5. Trying to do it during your busiest period. Migration itself only takes a few days, but there is always a short adjustment period as your team gets used to the new system. Do not schedule your migration the week before Chinese New Year or during your peak sales period. Pick a quieter week so you have breathing room.

Don't want to deal with any of this? Message us on WhatsApp and we handle the entire migration. Your number, your templates, your AI employee. Live in days.

What changes for your customers?

Here is the good news. For your customers, almost nothing changes.

They message the same number. They see the same business name and profile picture. They do not need to re-save your contact or do anything differently. Most customers will never know you switched to the API at all.

The only thing they will notice is that your service gets better. Replies come faster because multiple staff can handle messages at the same time. Questions get answered at 2am because your AI assistant is always on. Appointment reminders arrive automatically so they do not forget. Follow-ups happen consistently instead of falling through the cracks.

If you have a verified green tick, that transfers too. Your customers will still see the same trusted badge next to your business name.

In short, you are upgrading your backend without disrupting your customers' experience. Everything feels the same to them, except better.

Frequently asked questions

Do I lose my WhatsApp chats when migrating to the API?

Yes. Chat history from the WhatsApp Business App does not transfer to the API. You need to export your chats manually before migrating. Once you switch, the old conversations will not appear in your new system.

How long does WhatsApp Business API migration take in Singapore?

With chatavocado, the typical migration takes a few days from start to finish. DIY migration through Meta can take 1 to 3 weeks depending on how quickly Meta verifies your business.

What is a BSP and do I need one?

A BSP (Business Solution Provider) is a company authorised by Meta to help businesses set up the WhatsApp Business API. You can go direct through Meta, but a BSP handles the technical setup for you. chatavocado acts as your BSP and also builds your AI assistant.

How much does the WhatsApp Business API cost in Singapore?

Since July 2025, WhatsApp charges per message. Utility messages (reminders, confirmations) cost less than marketing messages (promotions). Messages within the 24-hour customer-initiated window remain free. The exact cost depends on your volume, but most Singapore SMEs spend SGD $50 to $200 per month on API messaging.

Can I use the WhatsApp app and API at the same time?

Update (March 2026): Yes. Meta's Coexistence feature, available since 2025, lets you run both the WhatsApp Business App and the API on the same phone number simultaneously. New messages sync across both platforms in real time. This is now the recommended way to migrate, as you can test the API while keeping the App as a fallback. For a full comparison, see our WhatsApp Business App vs API guide.

How do I migrate multiple branches or locations to the WhatsApp Business API?

Migrate one branch at a time, starting with your quietest location. Each branch can have its own WhatsApp number under one WhatsApp Business Account. Use Meta's Coexistence feature to run both the App and API simultaneously during the transition, so you never lose messages.

Can I switch from another WhatsApp API provider to chatavocado?

Yes. Your WhatsApp number ports to us in a few hours. We re-submit your templates, configure your inbox, and set up your AI employee before the number arrives. Chat history from your old provider does not transfer, so export important conversations first.