WhatsApp Number Porting: Moving Your Number Without Losing It

Why businesses port numbers

The move happens when the setup outgrows itself.

• From the app to the API: a second agent joins, or campaigns begin
• From a provider to Wutt: pricing, features, or support changes
• From one country number to another: market moves
• Consolidation: several numbers becoming one

App to API migration

The number leaves the phone and lives in the cloud. Customers keep the same number and see the same identity; the difference is who can now access it.

• The phone can disconnect once the API connection is live
• Contacts, chats, and the catalog transfer with the number
• Display name and profile stay with the number
• The whole team gets the inbox, not just the phone owner

Provider to provider migration

Moving between providers keeps the same number at Meta's level; the provider is the layer that changes.

• Export your contacts, opt-in records, and templates first
• Confirm the new provider supports the same number
• Plan the cutover for a quiet hour
• Test a real conversation on the new setup before announcing anything

What travels and what does not

Not everything survives a move on its own.

• The number, display name, and quality history stay at Meta's level
• Opt-in records and contact data must be exported and re-imported
• Approved templates are tied to the account and may need re-approval
• Chat history depends on the export; export before you cut over

The mistakes that hurt

The classic failures are all preparation failures.

• Cutting over before exporting opt-in records
• Assuming templates transfer automatically
• Running app and API on the same number simultaneously
• Announcing the move before testing

How Wutt helps

Wutt walks numbers through the Cloud API connection or QR session, helps keep display names compliant, and imports your opt-in records so campaigns stay legal — from $11/mo with a $1 first-month trial and zero markup on Meta fees.