Skip to content
Meta Business PartnerGlossary term

Number Migration

Number migration is the process of moving a phone number registered on the WhatsApp Business Platform — along with its display name, verified green tick, quality rating, and messaging limit tier — from one Business Solution Provider (BSP) or platform to another, without applying for a brand-new number. For Indian businesses that outgrow their first provider or want better pricing and support, a clean migration means keeping the number customers already know while switching the infrastructure behind it. Whether it goes smoothly comes down to one thing: who actually owns the underlying Meta assets, and whether you control your BSUID and WhatsApp Business Account (WABA).

A live WhatsApp number and its Meta assets to a new provider
What it moves
Ownership of your WABA and BSUID
Key requirement
Display name, green tick, quality rating, messaging tier
Preserved
Under an hour, plus template review time
Typical cutover
Per delivered message by category — no per-conversation penalty
Billing during move

In one line

Number migration moves a live WhatsApp Business number — with its display name, green tick, and quality rating — to a new provider. It's only clean when you own your WABA and BSUID, so plan the cutover, keep templates ready, and expect a short verification step rather than lost history.

What number migration actually means

A WhatsApp Business number is not a standalone SIM you simply plug into a new tool. It lives inside a WhatsApp Business Account (WABA), which sits under a Meta Business Manager, and it is connected to your business through a Business-Scoped User ID (BSUID) — the identifier Meta uses to tie a number to a specific business entity. Number migration is the coordinated act of detaching that number from its current BSP's WABA and re-registering it under a new provider's setup, while preserving the assets that took weeks to earn. It is different from creating a fresh number (you lose everything and start onboarding again) and different from simply changing chat software (which does nothing at the Meta layer). Done properly, your customers never notice: the same number keeps receiving and sending messages.

  • Display name and any verified green tick (official business account badge)
  • Quality rating (High / Medium / Low) that governs deliverability
  • Messaging limit tier (250 / 2K / 10K / 100K / unlimited unique customers per day)
  • Opt-in history and, where supported, existing approved template libraries

Why it matters for Indian businesses

The number printed on your packaging, invoices, storefront, and ad creatives is a hard asset. Re-training customers to message a different number is expensive and lossy. Migration lets you switch providers — for transparent pricing, better support, or features like flows and native automations — without touching the number itself. It also protects the reputation you have built inside Meta's system: a High quality rating and a 100K-tier messaging limit are earned over time and directly affect how many people you can reach each day. The catch is that a migration is only as safe as your ownership position. If your current provider registered the WABA under their own Business Manager and never gave you admin control of the BSUID, you are effectively renting your own number, and moving it becomes a negotiation rather than a technical task.

How a migration works, step by step

A well-run migration is sequenced so the number is never orphaned. First, confirm you have admin access to the Meta Business Manager and WABA that hold the number, and that your BSUID is correctly associated with your business. Next, the receiving provider (InfiQ) prepares the destination WABA and completes any business verification. You then initiate the disconnect from the old provider and register the number under the new one, which triggers a short re-verification (usually an OTP to the number). Templates are re-submitted or, where the platform allows, carried across, and webhooks and API credentials are re-pointed to the new provider. The final step is a live send test on a low-volume utility or authentication message before you switch production traffic. Throughout, billing follows Meta's current model — you are charged per delivered message by category (marketing, utility, authentication), so a brief migration window has no per-conversation penalty.

  • Verify ownership: Business Manager admin, WABA control, correct BSUID
  • Provision the destination WABA and finish business verification
  • Disconnect from the old provider and re-register the number (OTP verification)
  • Rebuild templates, webhooks, and API keys against the new endpoint
  • Run a live test send, then cut production traffic over

Common mistakes that break migrations

Most failed or painful migrations trace back to ownership and sequencing, not technology. The single biggest trap is discovering, mid-move, that a previous provider holds the WABA under their own Business Manager and controls the BSUID — leaving you unable to detach the number without their cooperation. Others delete or deactivate the number to 'start clean,' which wipes the quality rating and messaging tier and forces onboarding from scratch. Some teams migrate during a peak campaign window, so any short verification gap collides with high volume. And many forget that approved templates are tied to the source WABA — if they are not re-submitted early, marketing and utility sends stall on the destination side while awaiting Meta review.

  • Assuming you own the WABA when the old provider actually does
  • Deleting the number instead of migrating it, losing rating and limits
  • Migrating during a high-volume campaign instead of a quiet window
  • Not re-submitting templates early, so sends stall after cutover
  • Confusing this with the 2026 BSUID username change — that is a Meta-wide identifier update, not a provider move

See InfiQ pricing

Talk to InfiQ

See how this works on InfiQ

Tell us your use-case — we’ll show it running in a sandbox, usually within a working day.

Step 1 of 2
WhatsApp

Protected by invisible spam checks · replies within 1 working day

Frequently asked questions

Will I lose my green tick and quality rating when I migrate?+
Not if the migration is done correctly. The green tick (official business account status), quality rating, and messaging limit tier are attributes of the number inside Meta's system. When the number is migrated rather than recreated, these carry over. You only lose them if the number is deleted or deactivated and re-onboarded as new.
Do my customers need to save a new number after migration?+
No. The whole point of number migration is that the phone number stays the same. Customers keep messaging the number they already have. Only the infrastructure and provider behind it change, which is invisible to them.
What is a BSUID and why does it decide whether I can migrate?+
BSUID stands for Business-Scoped User ID — Meta's identifier linking a WhatsApp number to a specific business entity. If your BSUID and WABA are controlled by your own Meta Business Manager, you can move to any provider freely. If a previous provider controls them, you may need their cooperation to release the number.
How long does a WhatsApp number migration take?+
The technical cutover — disconnecting, re-registering with an OTP, and re-pointing webhooks — often takes under an hour. The longer part is preparation: confirming ownership, completing business verification on the destination side, and re-submitting templates for review, which can take a few days depending on Meta's queue.
Is there downtime during migration?+
There is a brief verification window when the number re-registers under the new provider. Planned carefully — outside peak hours, with templates already submitted and a test send ready — the practical interruption to live traffic is minimal. Migrating during a major campaign is what causes noticeable disruption.
Does migration change how I'm billed for messages?+
Billing follows Meta's current model regardless of provider: you pay per delivered message by category — marketing, utility, or authentication. InfiQ applies transparent rupee pricing (ex-GST). A short migration window does not create any extra per-conversation charge.
Can I migrate if my current provider set everything up under their own account?+
Sometimes, but it may require their cooperation to release the number and transfer WABA control. This is exactly why owning your Meta Business Manager, WABA, and BSUID from day one matters. InfiQ sets you up with full BSUID ownership so future moves are always your decision, not a negotiation.
Do my approved message templates transfer automatically?+
Templates are tied to the source WABA, so they generally need to be re-submitted on the destination side, where they go through Meta's standard review. Preparing and submitting them before cutover is the best way to avoid a gap in marketing and utility sends.

Migrate your WhatsApp number without losing what you've built

Talk to an InfiQ onboarding specialist for a zero-drama migration plan that keeps your green tick, quality rating, and messaging tier — with full BSUID ownership so the number is always yours.