Migrate a WhatsApp Number to Cloodot
Move a WhatsApp Business number from another provider to Cloodot with no messaging downtime.
Move your WhatsApp Business number to Cloodot without losing approvals, history, or uptime. Meta's migration flow keeps the number live throughout — no porting a SIM, no new number, no customer downtime.
This guide covers migrating a number currently connected to another Business Solution Provider (BSP). For a brand-new number, or one that's only ever been on the WhatsApp Business app, see Connect WhatsApp.
What migration means
Every WhatsApp Business API number lives inside a WhatsApp Business Account (WABA) and is managed by a BSP — the platform that connects the number to Meta's API. Cloodot is a BSP. So is your current provider.
Migrating tells Meta to move your phone number from your old provider's WABA to a WABA that Cloodot manages. The underlying WhatsApp number doesn't change — 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 carries over
Meta's partner-to-partner migration is non-destructive. A migrated number keeps:
- Its display name
- Its quality rating (green / yellow / red)
- Its messaging limits (current messaging tier)
- Its Official Business Account (OBA) status, if you have the blue checkmark
- Previously approved high-quality message templates, copied to the destination WABA and ready to send without re-review
Migration causes no messaging downtime — the number keeps sending and receiving throughout. (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 on the WhatsApp Business API with another BSP
- Admin access to the Meta Business portfolio (Business Manager) that owns the WABA, or a contact who has it
- 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 (see Step 1)
- A new 6-digit PIN to set after the move
The most common cause of a failed migration is two-step verification still being enabled on the number. WhatsApp won't migrate a number between Solution Providers while 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 off before Cloodot can claim the number.
If you own the WABA
If your Meta Business portfolio owns the WABA, you can disable 2FA yourself:
- Open WhatsApp Manager in Meta Business Suite
- Go to Account tools → Phone numbers
- Select the number, then open Settings
- Turn Two-step verification off
If your current BSP owns the WABA
Many providers register your number inside a WABA they own. You won't be able to reach the 2FA setting — ask your current provider's support team to disable two-step verification for you.
This is a routine migration request, and reputable BSPs will action it.
Don't deregister or delete the number from the old BSP before migrating. Meta moves the number as part of the Embedded Signup flow — premature deletion can cause the downtime migration is meant to avoid.
Step 2 — Start the migration in Cloodot
The migration runs through Meta's Embedded Signup window — the same wizard used for new numbers. 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
- Choose the WhatsApp Business Account to hold the number after migration (Cloodot can create one, or use an existing WABA 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 SMS or voice call
- Enter the 6-digit code when it arrives
Set a new two-step verification PIN
Set a fresh 6-digit PIN to re-enable two-step verification on the migrated number.
Store this PIN somewhere safe — you'll need it to disconnect, 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 another method Meta supports
- Return to Cloodot and click Continue
Confirm the connection
A success message confirms the migration, and the WhatsApp channel appears in your channels list. 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. This is expected.
After migrating
- 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
- Monitor WhatsApp Health — quality rating and messaging limits carry over with the number
- Confirm the display name and OBA badge appear correctly
Give the quality rating a day or two to settle in the new WABA. It migrates with the number, but Meta's dashboards can take time to reflect the move.
Troubleshooting
"Migration failed" or the number won't move
- Confirm two-step verification is disabled — the most frequent cause
- Confirm the number is on the WhatsApp Business API with another BSP, not the WhatsApp Business app (see Connect WhatsApp for the app case)
- Confirm no other migration was started for the same number at the same time
"Couldn't verify the number"
- Re-request the code and try voice call if SMS didn't arrive
- Confirm 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 2FA (see Step 1)
Display name or OBA badge looks wrong
- Give Meta time to propagate the change; if it persists, verify the display name in WhatsApp Manager
- The OBA badge migrates with a partner-to-partner move, but does not transfer between the WhatsApp Business app and the API — those require a separate verification
References — Meta documentation
- 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 help with your migration? See the troubleshooting guide or contact support.