BSP migration: phone number stuck in old backend

zoecreative

Anyone else hitting this wall? we're trying to migrate to a new BSP, but our phone number is still locked to the old provider. Can't connect anywhere else - it's just stuck.

Two suggestions came through: first, ask the old BSP to remove the credit line. Second, try disabling 2FA from the old WABA.

Has anyone actually managed to break free? Feels like a classic platform lock-in, except now your business messaging is hostage. would love to hear if either of those worked - or if there's a cleaner fix

datanerd

Ask your old BSP to remove the credit line from that number. If they don't, the new provider's backend can't take ownership - the system sees it as still tied to an active account with outstanding obligations. I've seen this stall migrations for weeks. You might need to confirm with them exactly which credit line (sometimes it's a billing credit reserve, other times a service-level limit). A quick API call from their side usually sorts it, but expect pushback if they've already terminated your contract. Worth escalating to their Ops team if support drags their feet.

adcraft

Disabling 2FA from the old WABA worked for me, but that's just putting a plaster on a badly designed migration.

coopplayer

Turning off 2FA from the WABA linked to the BSP was the first thing I tried - that whole backend tangle is such a headache. Keeping the display name identical during the migration from the old provider to the new one is crucial, otherwise Meta just rejects it silently.

If that still doesn't shake the number loose, you'll probably need to go back to your previous BSP and ask them to raise a support ticket with Meta to officially release your WABA. That's the only way I've seen the stuck numbers actually get freed up.

ctrjunkie

Oh, I've been through this exact mess. Removing the credit line is step one, but loads of people forget to check who actually owns the WABA first.

Hop straight into Meta Business Manager and see if your phone number's still linked to the old BSP's system user or their business portfolio. If it is, they either need to transfer the WABA back to you or open a Meta support ticket to release it.

Disabling 2FA only matters once the WABA is under your control - doing it earlier won't change a thing. The support ticket route takes three to seven business days. Annoyingly slow, but it does the job.

Is your WABA currently inside your own Business Manager or still sitting with the old BSP?

zoecreative

Had the exact same head-scratcher after a BSP migration last month. Meta's support is genuinely useless for anything beyond the obvious, so i ended up figuring this one out the hard way.

the fix that worked for the client: forced the number back to regular WhatsApp, left it for about 2-4 hours, then flipped it back to WhatsApp Business API. once that processed, reconnected it to Business Manager and suddenly it was visible and assignable to the new BSP.

this was with coexistence enabled, so can't speak for direct API-linked numbers. My assumption is the backend has some kind of state lock that needs a full reset cycle. feels like flushing a cache in a system that shouldn't need one

ctrjunkie

Ugh, been there - it's a proper headache. The Meta AI connection and your BSP's credit line are two separate blockers, but they love hitting you at the same time.

The automatic events side lives in your Meta Business Manager, not the BSP. Head into Business Manager, find the WhatsApp account under Accounts, and check which System Users or apps have permissions on it. Strip out anything tied to the old BSP or old IA setup.

Then, like someone else pointed out, you need to ask your old BSP to release the credit line. Both steps have to happen - fixing only one leaves you stuck.

Have you checked the System Users section in Business Manager yet?

adcraft

screenshot isn't going to fix anything. the BSP migration is notorious for breaking phone number fields - usually it's a mapping issue with the new call extension format. have you checked whether the old number is a tracking number or a static one? That makes a difference. also, try pulling the ad group level report instead of campaign level - sometimes the migration tool pushes numbers into hidden ad group extensions that don't surface in the UI. a screenshot will just show me what you already know: it's stuck. The real fix is in the Google Ads Editor or a direct API call to purge the legacy extension.

ctrjunkie

Oh man, I feel this pain. If Meta support already told you it's still linked, turning off 2FA won't do a thing. You've gotta go through Business Manager-not WhatsApp Manager-and raise a proper Business Support ticket. Head to business.facebook.com, click Help, then pick the WhatsApp account issues category. The magic phrase is: "I want the number released from BSP X so I can migrate." Don't just say "migration" in general-that specific wording gets it to the team who actually handles this nonsense. Took us about three to five business days that way. Did they give you a ticket ID when you spoke to them?