When you move a WhatsApp Business API number to a new BSP or a new WABA, the number itself is the easy part — what breaks is everything hanging off it: the two-step verification PIN, your approved templates, the live 24-hour session windows, and any downtime you did not plan for. Done right, a handover is near-zero-downtime and your quality rating and messaging limit follow the number across; done wrong, you lock yourself out on the PIN, drop messages during the cutover, and rebuild templates from scratch. This applies to any business on the API, whatever your industry.
This 2026 guide is the operational mechanics of a number handover — separate from choosing a provider. It covers exactly what transfers versus what resets, the two-step PIN trap that strands most first-timers, how to make the downtime window near-zero, a pre-handover checklist, a cutover-day runbook, and what to verify after. Meta's platform behaviour shifts over time — treat the carry-over specifics below as directional and confirm the current rules in WhatsApp Manager before you cut over.
What transfers vs what resets on a handover
A "number handover" can mean two things: moving the same number to a different BSP, or moving it between WABAs. The mechanics overlap. The single most important thing to know is which assets ride along with the number and which start fresh:
| Asset | On handover | What to do |
|---|---|---|
| The phone number | Kept — same number, new host | Nothing; this is the point of the exercise |
| Quality rating | Generally follows the number (verify current Meta behaviour) | Do not assume a clean slate — a red rating travels with you |
| Messaging limit tier | Generally follows the number (verify current) | Confirm your tier post-move; do not plan a blast expecting a reset |
| Display name | May need re-submission/approval on the new setup | Have the approved name ready; expect a review step |
| Two-step verification PIN | Must be disabled/known to move the number — hard blocker if lost | Retrieve or reset it before handover day (see below) |
| Message templates | Re-created on the new BSP/WABA — do not carry automatically | Export names + bodies; re-submit early, approval takes time |
| Opt-in consent | Yours — it is your record, not the BSP's | Keep your consent log; it does not live with the provider |
| Open 24-hour session windows | Reset — in-flight service conversations drop | Cut over in a low-traffic window; expect to re-open with templates |
| Chat history | Does not transfer between BSPs | Export what you need from the old platform first |
The pattern: reputation is tied to the number, tooling is tied to the host. That is good news (a healthy rating and tier travel with you) and bad news (a red rating does too, and templates plus history do not). For the strategic side — whether to move at all, and how to pick the destination — see the WhatsApp BSP migration guide and the BSP contract red flags to check your exit terms before you start.
The two-step PIN trap
This is where most handovers stall. WhatsApp numbers carry an optional two-step verification PIN, and moving a number typically requires either disabling it or supplying it during the transfer. If the original setup was done by an agency or a departed employee and nobody recorded the PIN, you cannot simply guess it — and resetting it can involve a waiting period before the number can be moved.
Do this before you commit to a handover date: confirm you can log into the current setup, locate the two-step verification setting, and either turn it off for the move or write down the current PIN somewhere your team controls (not one person's inbox). If the number is held inside a partner's account and you do not have this access, that is a dependency to resolve weeks ahead, not on cutover day.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Ownership check before anything else
The number and its Meta assets should sit in a Business Manager / WABA you own, with the BSP added as a partner — not the other way round. If your provider owns the WABA, a handover becomes their decision, not yours. Verifying who holds the number is step zero; the Meta business verification guide covers getting your own verified business in place.
How to make the downtime near-zero
Some downtime is unavoidable — there is a moment where the number detaches from the old host and registers on the new one, and messages in that gap will not deliver. The goal is to make that gap minutes, not hours, and to schedule it where it costs least:
- Pick a genuine low-traffic window. Late night or a weekend for most Indian B2C; a public holiday for B2B. Never mid-campaign, never during a support peak.
- Have the new BSP fully staged first. Account connected, display name submitted, templates already approved, webhook and number pointing at the new endpoint — so the only live step is the number registration itself.
- Pause outbound campaigns before the window. Let open 24-hour sessions wind down; do not start conversations you cannot finish before cutover.
- Warm-lite after re-registration. The rating and tier follow the number, but ramp the first hour gently and watch quality before resuming full volume — see number warm-up for the ramp discipline.
Pre-handover checklist
- Confirm you own the WABA and have admin access to Business Manager — not just the BSP dashboard.
- Retrieve or reset the two-step PIN and store it where the team can reach it.
- Export templates (names, categories, bodies, variables) and any media headers; you will re-submit them on the new host.
- Export chat history and contact/opt-in records from the old platform — they do not migrate.
- Check the current quality rating and messaging tier so you know your starting point after the move.
- Read your current BSP's exit terms — notice period, data export, any lock-in — per the contract red-flags checklist.
- Stage the new BSP fully and get templates + display name approved before the cutover date.
Cutover-day runbook
| Step | Action | Why |
|---|---|---|
| 1 | Pause all outbound; announce a maintenance window internally | No new sessions you cannot close before cutover |
| 2 | Confirm new BSP staged: templates approved, display name set, endpoint ready | Only the registration step should be live work |
| 3 | Disable two-step PIN (or have it ready) and detach the number from the old host | The PIN is the usual blocker; clear it first |
| 4 | Register the number on the new BSP and re-enable two-step with a known PIN | The core cutover; keep this window tight |
| 5 | Send a controlled test to an internal number; confirm inbound + status webhooks fire | Prove both directions work before real traffic |
| 6 | Resume gently — utility first, watch quality for the first hour | Reputation follows the number; do not shock it |
After the handover: what to verify
Do not declare victory when the first test message sends. Confirm the full loop: outbound delivery and inbound receipt, delivery-status webhooks landing, templates showing approved on the new host, the display name correct in a real chat, and the messaging tier and quality rating reading what you expected. If the rating slipped or the number lands restricted, treat it like any quality incident — stop marketing, send only expected utility messages, and let the window recover; the red-rating recovery playbook applies unchanged. If sends are hard-blocked at the account level after the move, check the account-level send blocks guide.
How RichAutomate makes a handover boring
A handover should be a scheduled, reversible, low-drama event — not a leap of faith. RichAutomate onboards on a WABA you own, so the number is never hostage to the provider; templates are re-submitted and tracked in one place, webhooks are verified as part of setup, and there is no lock-in clause holding your number. Pricing is flat per-message — ₹0 platform fee, ₹0 setup, ₹0 monthly — so moving to us costs you the migration effort and nothing in subscription. See the full feature set, and if you are leaving another tool, the migration guide walks the strategic decision.
Bottom line
The number is the easy part of a WhatsApp handover; the two-step PIN, the templates, the session windows and the downtime are what actually bite. Own your WABA, clear the PIN weeks ahead, stage the new host fully so cutover is minutes not hours, export what does not travel, and warm the number gently on the far side. Do that and your customers never notice the number changed hands. Skip the prep and you spend the week after a "quick migration" locked out on a PIN and rebuilding templates you could have re-submitted in advance.