Migrate a WhatsApp Number to Cloodot
Move a WhatsApp Business number from another provider (BSP) to Cloodot with no messaging downtime, keeping your display name, quality rating, and approved templates.
Already running WhatsApp Business with another provider? You can move your number to Cloodot without losing your history of approval. Meta's migration flow keeps your number live the whole time — there's no porting a SIM, no new number, and no downtime for your customers.
This guide walks through migrating a number that's currently connected to another Business Solution Provider (BSP). If you're connecting a brand-new number or one that's only ever been on the WhatsApp Business app, use Connect WhatsApp instead.
What "migration" means here
Every WhatsApp Business API number lives inside a WhatsApp Business Account (WABA) and is managed through a BSP — the platform that connects your number to Meta's API. Cloodot is a BSP. So is your current provider.
Migrating means telling Meta to move your phone number from your old provider's WABA to a WABA that Cloodot manages. Your underlying WhatsApp number never changes — only the provider behind it does.
This is a BSP-to-BSP migration through Meta's official Embedded Signup flow. It is not the same as deleting and re-registering a number, and it does not require deleting your account.
What you keep after migrating
Meta's partner-to-partner migration is designed to be non-destructive. According to Meta's documentation, a migrated number retains:
- Its display name
- Its quality rating (green / yellow / red)
- Its messaging limits (your current messaging tier)
- Its Official Business Account (OBA) status, if you have the blue checkmark
- Its previously approved high-quality message templates, which are copied to the destination WABA and can be sent immediately without going through review again
Most importantly, the migration does not cause any messaging downtime — your number keeps sending and receiving throughout the process. (Meta — Migrate phone numbers among Solution Partners)
Only high-quality templates are carried over automatically. Templates with a low quality score, in a paused/disabled state, or still pending review may not migrate — recreate those in Cloodot after the move. See WhatsApp Templates.
Before you start
You'll need:
- A number currently registered on the WhatsApp Business API with another BSP
- Admin access to the Meta Business portfolio (Business Manager) that owns the WABA — or a way to reach whoever does
- A payment method ready to add in Meta Business Suite (the API uses conversation-based pricing)
- The number's current two-step verification PIN disabled (covered below)
- A new 6-digit PIN chosen for re-registration after the move
The single most common reason a migration fails is two-step verification still being enabled on the number. WhatsApp will not migrate a number from one Solution Provider to another while two-step verification (2FA) is on. Disable it first. (Meta — Two-step verification)
Step 1 — Disable two-step verification on the old provider
Two-step verification must be turned off on the number before Cloodot can claim it.
If you own the WABA
If your own Meta Business portfolio owns the WABA, you can disable it yourself:
- Open WhatsApp Manager in Meta Business Suite
- Go to Account tools → Phone numbers
- Select the number you're migrating, then open Settings
- Find Two-step verification and turn it off
If your current BSP owns the WABA
Many providers register your number inside a WABA that they own. In that case you can't reach the two-step verification setting yourself — ask your current provider's support team to disable two-step verification on the number for you.
This is a normal, expected request during a migration; reputable BSPs will action it.
You don't need to (and shouldn't) deregister or delete the number from the old BSP yourself before migrating. Meta moves the number as part of the Embedded Signup flow — premature deletion can cause downtime, which migration is specifically meant to avoid.
Step 2 — Start the migration in Cloodot
The migration runs through Meta's Embedded Signup window, the same wizard used to connect a new number — Cloodot detects that the number already exists on the API and routes you into the migration path automatically.
Open the Channel Connection Wizard
- Go to Settings → Organization → Channels
- Click Add Channel (or the + button)
- Select WhatsApp
Authorize with Facebook
- Click Login with Facebook
- Sign in with the account that has admin access to the Meta Business portfolio and WABA
- Grant the requested WhatsApp Business management permissions
Select the WABA and the number to migrate
- Choose the WhatsApp Business Account that should hold the number after migration (Cloodot can create one for you, or use an existing one you manage)
- Select the phone number you're bringing over
- Confirm you want to migrate it from its current provider
Verify ownership of the number
Meta confirms you control the number with a one-time code:
- Choose to receive the code by SMS or voice call
- Enter the 6-digit code when it arrives
Set a new two-step verification PIN
Because you disabled two-step verification before migrating, you'll now set a fresh 6-digit PIN to re-enable it on the migrated number.
Store this PIN somewhere safe — you'll need it if you ever disconnect and reconnect, or migrate again later.
Add a payment method
The WhatsApp Business API requires a payment method in Meta Business Suite (conversation-based pricing).
- Click Open Payment Settings — Meta Business Suite opens in a new tab
- Add a card or other method Meta supports
- Return to Cloodot and click Continue
Confirm the connection
A success message confirms the migration, and your WhatsApp channel appears in your channels list. Your number is now managed by Cloodot — start handling conversations in your unified inbox right away.
Heads up
Meta sends a confirmation email to the WABA administrator when a number is migrated between providers. This is expected.
After you migrate
- Send and receive WhatsApp messages in your Cloodot inbox
- Review which templates carried over and recreate any that didn't
- Sync product catalogues from Meta Commerce Manager
- Watch your number's WhatsApp Health — quality rating and messaging limits carry over, so a clean number stays clean
- Confirm your display name and OBA badge appear correctly
Give your quality rating a day or two to settle in the new WABA. It migrates with the number, but Meta's dashboards can take a little time to reflect the move.
Troubleshooting
"Migration failed" or the number won't move
- Confirm two-step verification is disabled on the number — this is the most frequent cause
- Confirm the number is genuinely on the WhatsApp Business API with another BSP (not just the WhatsApp Business app — for that, see Connect WhatsApp)
- Make sure no migration was started for the same number elsewhere at the same time
"Couldn't verify the number"
- Re-request the code and try voice call if SMS didn't arrive
- Double-check the number can receive SMS or calls (some virtual numbers can't)
Templates are missing after migration
- Only high-quality, approved templates migrate automatically
- Recreate paused, low-quality, or pending templates in WhatsApp Templates
Two-step verification setting is greyed out
- The WABA is likely owned by your current BSP — ask their support to disable two-step verification for you (see Step 1)
Display name or OBA badge looks wrong
- Allow time for Meta to propagate the change; if it persists, verify the display name in WhatsApp Manager
- The blue OBA badge migrates with a partner-to-partner move, but it does not transfer between the WhatsApp Business app and the API — those require a separate verification process
References — Meta documentation
These are Meta's authoritative references for the behaviour described above:
- Migrating a business phone number from one Solution Partner to another via Embedded Signup — the official partner-to-partner migration flow, including what is preserved (display name, quality rating, messaging limits, OBA status, high-quality templates) and the no-downtime guarantee
- Migrate Numbers to a Different WhatsApp Business Account — moving a number between WABAs via Embedded Signup
- Two-step verification — why two-step verification must be disabled before migration and re-set afterward
- Business phone numbers — how phone numbers, WABAs, and registration work on the platform
- Migrate an Existing WhatsApp Number to a Business Account — reference for numbers coming from the WhatsApp Business app (a different path than BSP-to-BSP migration)
Next steps
- Set up WhatsApp templates and recreate any that didn't migrate
- Monitor number health to protect your quality rating
- Sync product catalogues from Meta Commerce Manager
- Configure workspace settings
Need a hand with your migration? Check the troubleshooting guide or contact support.