How to migrate from another BSP to InfiQ on the WhatsApp Business API
Switching your WhatsApp Business API number from your current Business Solution Provider (BSP) to InfiQ is a well-defined process, not a rebuild. Your phone number, verified display name, green tick (official business account status) and message history on Meta's side all belong to your WhatsApp Business Account (WABA) — not to your old provider. This guide walks through exactly how to migrate, what carries over, what has to be recreated, and how to keep downtime down to a short, planned window instead of a scary outage.
What you'll do
Migrating from another BSP to InfiQ means moving your existing WABA and number under InfiQ's Meta partnership. Your number, display name and green tick stay; approved templates usually carry over or are quickly recloned. The critical steps are getting your current provider to release the number, completing the two-factor migration in Meta Business Manager, and repointing your webhook to InfiQ before you resume high-volume sends.Step 1 — Audit what you have and prepare to move
Before you touch any settings, take stock of your current setup so nothing gets lost in the handover. The most common cause of a painful migration is missing information you assumed the old BSP was storing for you. Gather everything below while your existing number is still live and sending, because some of it is much harder to retrieve after the number leaves your old provider.
- Confirm which phone number(s) and which WhatsApp Business Account (WABA) you are moving.
- Note your verified display name and whether you hold the green tick (official business account).
- Export or screenshot every approved message template — name, language, category and exact body/variables.
- Locate your two-step verification (2FA) PIN for the number; you will need it or you will need to reset it.
- List active integrations that point at the old webhook: CRM, e-commerce plugin, chatbot, ticketing, analytics.
Step 2 — Verify Business Manager access and start onboarding with InfiQ
A WhatsApp Business API migration is fundamentally a change of the BSP attached to your WABA, and that is controlled through Meta Business Manager. You must be an admin of the Business Manager portfolio that owns the WABA — not merely a user of the old provider's dashboard. Once access is confirmed, InfiQ, as an official Meta Business Partner, initiates the connection so your existing WABA can be claimed under InfiQ's platform. Share your WABA ID and the number being moved with your InfiQ onboarding contact so the request lands against the right asset.
- Sign in to business.facebook.com and confirm you are an admin of the correct Business portfolio.
- Provide InfiQ your WABA ID, the phone number, and the registered business name.
- InfiQ sends a partner request / Embedded Signup link so you can grant InfiQ access to the WABA.
- Keep your Meta business verification current — an unverified or lapsed business can stall the move.
Step 3 — Release the number from your current BSP
Your old BSP has to let go of the number before InfiQ can register it. On Meta's platform a number can only be actively hosted by one BSP at a time, so this release step is the true point of migration. Ask your current provider to disable two-step verification (or give you the current PIN) and to confirm they are not blocking the transfer. Time this deliberately: the short window between the old provider releasing the number and InfiQ re-registering it is when the number cannot send or receive on the API, so schedule it outside your busiest hours.
- Raise a migration/porting request with your current BSP in writing.
- Ask them to turn off two-step verification or hand over the active 6-digit PIN.
- Pause any scheduled campaigns and pause automations that fire on inbound messages.
- Agree a specific switchover time so both sides act in the same window.
Step 4 — Register the number under InfiQ and re-verify
With the number released, InfiQ registers it against your WABA on the InfiQ platform and completes the migration handshake in Meta Business Manager. This is where your two-step verification PIN is used — Meta uses it to confirm you genuinely control the number. If the PIN is unknown, it can be reset, though a reset may briefly affect the number. After registration completes, your same number is now live through InfiQ with the display name and green tick intact.
- InfiQ registers the number and submits the migration with your 2FA PIN.
- Meta confirms the WABA is now connected to InfiQ as the BSP.
- Set a fresh two-step verification PIN and store it somewhere durable.
- Verify the display name and official business account badge still show correctly.
Step 5 — Recreate templates, repoint your webhook, and reconnect integrations
Approved templates are attached to the WABA, so in most migrations they travel with it and remain usable. Occasionally a template needs to be re-submitted; if so, recreate it with the identical name, language and category to avoid confusion and to keep costs predictable. The bigger task is plumbing: every system that talked to your old provider's webhook now needs to talk to InfiQ instead. Repoint each integration to InfiQ's webhook and swap in your new InfiQ API credentials so inbound messages and delivery/read events flow to the right place.
- Confirm approved templates are present in InfiQ; re-submit any that did not carry over using the same category.
- Update the webhook (callback) URL in every connected app to InfiQ's endpoint.
- Replace old API keys/tokens with your InfiQ credentials in your CRM, chatbot and e-commerce tools.
- Map incoming events (delivered, read, replied) to your automations so nothing silently breaks.
Step 6 — Test end-to-end, then go live and monitor
Do not resume full campaign volume the moment the number is live. Send controlled tests first, ideally to your own phone and to a couple of teammates, covering a utility template, an inbound reply landing in your CRM, and a delivery/read receipt showing in InfiQ. Because a migrated number keeps its existing quality rating and messaging limit, you usually do not need to warm up from zero the way a brand-new number does — but you should still ramp thoughtfully and watch the numbers for the first day or two.
- Send a test template message to your own number and confirm delivery and read status in InfiQ.
- Reply from that number and confirm the inbound message reaches your connected tools.
- Check that opt-in handling and the correct template category are applied before mass sends.
- Watch quality rating, delivery failures and messaging limit closely for the first 24–48 hours.
Frequently asked questions
Do I have to change my WhatsApp number when I migrate BSPs?+
Will I lose my green tick or verified display name?+
Do my approved templates carry over?+
How much downtime should I expect?+
What is the migration PIN and where do I find it?+
Do I need to warm up the number again after migrating?+
Will my quality rating and messaging limit reset?+
How does billing change once I move to InfiQ?+
Ready to switch to InfiQ without losing your number?
Our India-based onboarding team runs the migration with you, coordinates the release from your old BSP and keeps your downtime to a short planned window — book a call and we'll map your move end to end.