WhatsApp API

WhatsApp BSP Migration: What Moves, What Does Not, and How Long It Takes

A WhatsApp BSP migration moves an API number from one solution provider to another, carrying its verification and tier but not its chat history. A practical guide to migrating a WhatsApp Business API number between providers: what transfers, what you rebuild.

Arjun Mehta Published 2 Aug 2026 6 min read

Switching WhatsApp BSP: green cover card with the WhatsApp API label, two chat bubbles and a 6 min read tag

WhatsApp BSP migration in brief

A WhatsApp BSP migration moves an API number from one provider to another, and WappBlaster sets out before the switch exactly what will be rebuilt, because the number and its standing belong to the business's WhatsApp Business Account rather than to any provider. The number, business verification, quality rating, messaging tier and Meta Business Manager assets, green tick included, all move, so the account does not drop back to 1,000 unique customers a day. Approved templates usually come across too. What gets rebuilt is the real work: chatbot flows, automations, team roles and department routing, and integrations to the store, CRM or sheets, while chat history stays with the old platform. The timeline is short: audit and export on Day 0, parallel rebuilding into Day 1, then release and re-registration in one maintenance window on Day 1, with a gap measured in minutes, followed by a week of watching quality and delivery. The step that matters most comes first: confirm the business, not the provider, owns its Meta Business Manager.

What moves when you switch WhatsApp BSP?

The number, business verification, quality rating and messaging tier move with you, approved templates usually transfer, and chat history, chatbot flows and automations normally have to be rebuilt.

WappBlaster explains up front what will be rebuilt, because the number and its standing sit with your WhatsApp Business Account rather than with any provider.

  • The number is the part that moves most cleanly.
  • Budget time for rebuilding flows, not for moving the number.
  • Expect a short, planned gap rather than a long outage.

WhatsApp BSP migration benefits

  • Messaging tier kept

    The number's limit and quality rating carry over, so sending volume does not restart from scratch.

  • Green tick preserved

    Business Manager assets belong to you and travel with the number.

  • A gap of minutes

    Release and re-registration fit inside one off-peak maintenance window.

  • Realistic planning

    Knowing that flows and integrations need rebuilding puts the effort where it belongs.

  • No ownership surprises

    Checking Business Manager ownership first stops a one-day job becoming a two-week one.

  • Records saved before cutover

    Exporting contacts with custom fields and any history you need protects what stays behind.

Most of the fear about switching providers is about the number. The number is the part that moves most cleanly.

Quick answer: Migrating a WhatsApp API number between providers keeps the number, your business verification and your quality rating and messaging tier, because those belong to your WhatsApp Business Account rather than to the provider. Approved templates generally come across. Chat history, chatbot flows and automations usually have to be rebuilt on the new platform.

What moves with you in a WhatsApp BSP migration

The important one is the messaging tier. You do not start again at 1,000 unique customers a day, which is the fear that keeps most businesses on a provider they have outgrown.

  • The phone number itself
  • Business verification for your legal entity
  • Quality rating and current messaging limit tier
  • Approved message templates, in most cases
  • Your Meta Business Manager assets, including any green tick

What has to be rebuilt after a BSP migration

This is the real work of a migration, and it is why a plan matters more than the technical cutover. The cutover itself is short.

  • Chatbot flows, because every platform has its own builder
  • Automations and workflow logic
  • Chat history, which stays with the old platform
  • Team accounts, roles and department routing
  • Integrations to your store, CRM or sheets

A realistic WhatsApp BSP migration timeline

  1. Day 0: audit what exists on the old platform. Export contacts, list templates, screenshot bot flows.
  2. Day 0-1: rebuild templates, flows and automations on the new platform in parallel, while the old one still runs.
  3. Day 1: the number is released from the old provider and registered on the new one, usually inside a single maintenance window.
  4. Day 1: verify sending and receiving on the new platform before announcing anything.
  5. Day 2 onward: monitor quality rating and delivery closely for the first week.

BSP migration downtime, honestly

There is a short window during release and re-registration where the number cannot send or receive. Scheduled properly this is minutes, not hours, and it should be run outside your peak.

Anyone promising literally zero downtime is describing the customer experience rather than the technical reality. Aim to make the gap short and quiet rather than to pretend it does not exist.

Pre-flight checklist for a WhatsApp BSP migration

That last one matters more than anything else on the list. If your provider owns your Business Manager rather than having admin access to yours, sort that out before you plan anything else.

  • Export contacts with all custom fields, not just names and numbers
  • Document every active automation and what triggers it
  • Record which templates are actually in use, not the whole library
  • Check your contract notice period with the current provider
  • Confirm who owns the Meta Business Manager: it should be you, not the provider

Before you move, read the green tick verification guide, compare migration providers in India and see our AiSensy comparison.

WhatsApp BSP migration: what moves and what is rebuilt
Feature Status Why
Phone number Moves It belongs to your WhatsApp Business Account
Business verification Moves Tied to your legal entity
Quality rating and tier Moves No restart at 1,000 unique customers a day
Approved templates Usually moves Owned by the WhatsApp Business Account
Chatbot flows and automations Rebuilt Each platform has its own builder
Chat history Stays behind Export what you need before cutover
Team accounts and integrations Rebuilt Roles, routing, store, CRM and sheets are platform-specific

WhatsApp BSP Migration: questions

Will I lose my messaging limit tier if I switch providers?

No. Your quality rating and sending tier belong to the number and its WhatsApp Business Account rather than to whichever provider you use, so a number on the unlimited tier keeps it when it moves.

Link to this answer

Do approved templates transfer?

In most cases, because templates are owned by the WhatsApp Business Account. Even so, make a list of the templates you rely on before you start, and check each one appears on the new platform before you switch traffic over.

Link to this answer

How much downtime is involved?

A short window during release and re-registration, typically minutes when scheduled properly. Plan it outside peak hours and verify sending before you resume campaigns.

Link to this answer

Can I keep my chat history?

Not into the new platform. History stays with the old provider, so export anything you need for records before you cut over.

Link to this answer

What is the most common migration mistake?

Discovering at cutover that the outgoing provider owns your Meta Business Manager. Verify ownership at the start, because untangling it mid-migration is what turns a one-day job into a two-week one.

Link to this answer

Does the green tick survive a WhatsApp provider switch?

Yes. Your Meta Business Manager assets, including any green tick, belong to you and move with the number.

Link to this answer

What has to be rebuilt after a BSP migration?

Chatbot flows, automations, team accounts and routing, and integrations to your store, CRM or sheets. Every platform has its own builder, so these are recreated rather than copied.

Link to this answer

Who should own the Meta Business Manager?

You, not the provider. If the provider owns it rather than holding admin access to yours, fix that before planning anything else.

Link to this answer

Is zero downtime possible when switching WhatsApp providers?

Not technically. There is a short gap during release and re-registration, but scheduled outside peak hours it lasts minutes and customers rarely notice.

Link to this answer

What should I export before switching WhatsApp BSP?

Contacts with all custom fields, a record of every active automation and its trigger, the templates actually in use and screenshots of bot flows. Check your contract notice period too.

Link to this answer

Still not answered?

Ask a real person. We reply on WhatsApp, usually within the hour.

Ask on WhatsApp

Arjun Mehta

Head of WhatsApp Business API, WappBlaster

Arjun Mehta leads WappBlaster’s official Meta WhatsApp Business Platform practice, bulk campaigns, chatbot, shared inbox and BSP migrations for 1,000+ India, UAE, USA and UK brands.

Ready to automate post-call follow-up?

Join 3,500+ businesses on Auto WhatsApp After Call, ₹2499 ($22.99)/yr per user.

Start Free Trial View product