Switching WhatsApp Business API providers (also called a BSP or Meta Business Partner) is a known, common process: your phone number belongs to you, not to the provider, so you don't lose it when you migrate. What does change is where the technical connection with Meta lives and which platform for multi-agent support, CRM for WhatsApp, and automation your team uses going forward. A typical migration takes anywhere from a few days to a couple of weeks, and with the right planning the cutover feels like switching a dashboard, not losing the channel.
Why businesses switch WhatsApp Business API providers
The most common reason isn't price: it's that the current provider stopped keeping up with the operation. Support that takes days to respond, number quality reports that don't exist, no way to add omnichannel support (Instagram, Messenger, email) without signing up for another separate tool, or a cost that climbs with every new feature the plan doesn't cover. If two or more of these sound like your current setup, this guide on how to choose a provider breaks down the criteria to compare before you decide to make the jump.
What transfers and what doesn't when you switch BSPs
| Item | Does it transfer? | Detail |
|---|---|---|
| Your WhatsApp number | Yes | The number is yours; it gets disconnected from the old provider and reconnected with the new one |
| Business verification with Meta | Yes, it's reused | An already-verified business doesn't go through the full process again from scratch |
| Conversation history | Not automatically | Depends on whether the previous provider allows exporting history; ask for it before closing the account |
| Approved message templates | Not automatically | They need to be recreated and resubmitted for approval on the new platform, even if the content is already proven |
| Number quality rating | Yes, it's Meta's | Quality is tied to the number with Meta, not to the provider running it, so it doesn't reset |
| CRM contacts and tags | No | These migrate manually or via export/import if both platforms support it |
This table is why a BSP migration deserves careful planning: the technical side (the number, verification, quality) isn't lost, but the operational side (templates, history, inbox setup) takes real handoff work.
How the process works, step by step
- Assessment and handoff plan: the new provider reviews your current setup (agents, active templates, integrations) to map out what needs to be recreated.
- Export what you can from the previous provider: conversation history, contacts, and approved templates, if the previous provider allows it.
- Disconnect the number from the previous provider: the number is released from the old platform, usually coordinated in a short window to minimize interruption.
- Reconnect with the new provider: the already-verified number gets linked to the new technical infrastructure.
- Recreate templates and flows: message templates and chatbot or qualification flows are set up again on the new platform.
- Test window: incoming and outgoing messages are validated before announcing the change to the whole team.
How long it actually takes
The typical range runs from a few days to two or three weeks, mostly depending on how many templates need to be recreated and approved, and how quickly the previous provider responds to the disconnection request. The technical part (reconnecting the number) is usually resolved in hours; what takes the most time is Meta's approval of new templates and reconfiguring automation flows.
How to avoid downtime during the switch
- Don't cancel the old contract until the reconnection is confirmed: keeping both platforms active for a couple of overlapping days lowers the risk of going without a channel.
- Recreate critical templates first: prioritize the ones you use for confirmations, reminders, or active campaigns, and get them approved before the cutover date.
- Tell your team the exact switch date: so they know which platform to answer from starting minute one.
- Request the exported history in advance: some providers take days to generate the file, so ask for it before starting the disconnection.
- Test the number on the new platform before announcing it: send and receive test messages to confirm the connection with Meta came through correctly.
What to check with the new provider before signing
If you're going through the effort of migrating, it's worth making sure the next provider doesn't leave you in the same spot a year from now. Confirm they're a certified Meta Business Partner, that the onboarding team actively owns the handoff (not just the technical part), that AI chatbots are included and not just a shared inbox, and that omnichannel support is available from day one if you'll need it.
How LiveConnect supports a BSP migration
LiveConnect, as a Meta Business Partner, manages the technical handoff of your number, guides the recreation of message templates, and sets up the multi-agent inbox, AI chatbots, and CRM for WhatsApp before the cutover date, so your team starts operating on the new platform without any dead days. If you also handle Instagram, Messenger, or email, the migration includes adding those channels to the same inbox. Plans start at USD $89/month; you can review them in the plans and pricing section of this page.
How to get started
- Gather your current setup: list of active templates, number of agents, and which additional channels you use today.
- Request your history and confirm the disconnection date with your current provider.
- Schedule the handoff with the new provider so critical templates are approved before the cutover.
Weighing whether to switch WhatsApp Business API providers? Message us on WhatsApp or check out our plans and pricing: a LiveConnect specialist will help you plan the handoff without missing a single day of support.
