Many businesses start on the free WhatsApp Business app, build a customer base on that number and later outgrow it. The natural question is: can we keep our number when we move to the API? In most cases yes, but the move has consequences you should understand first, including what happens to your existing chats and the app itself.
WhatsApp changes its migration rules and options, so check current documentation and confirm details with your provider before acting. This guide covers the general points.
Why businesses migrate
- More than one person needs to answer from the same number.
- They want automation, AI replies and approved templates.
- They need integrations with CRM, ads and booking systems.
- They want reporting and better control than a phone app allows.
- They have reached the limits of the Business app.
The big trade-off: app versus API
Historically, a number registered on the API could not be used on the regular WhatsApp or Business app at the same time. Registering it on the API typically meant that the app on your phone would stop working with that number. WhatsApp has been introducing options that allow some businesses to use the app and the API together in certain setups, but availability and limits vary. Ask your provider what is possible for your number and country right now.
What happens to your existing chats
- With standard migration, chat history on the app does not automatically transfer to the API platform (though under coexistence onboarding, up to six months of chat history can sync). Customers keep their own copy of chats.
- You can back up your chats and contacts from the app before migrating.
- Some providers can help import contact lists, but confirm with your provider what message history transfer or coexistence options are supported for your setup.
- Groups are not supported on the API in the same way as on the regular app.
Option 1: Migrate your existing number
Choose this when your customers already know and use that number.
- Back up chats and export contacts from the app.
- Tell your team and prepare for a short period when the number may be unavailable.
- Set up your Meta business portfolio and prepare your messaging account (you can complete business verification now or later to unlock higher limits).
- Disable or remove the number from the app as required by the registration process, following your provider's instructions.
- Register the number with your provider and verify it by SMS or call.
- Set your display name, profile and templates.
- Test, then announce the change to customers if needed.
Option 2: Use a new number for the API
Choose this when you want to keep the app running or reduce risk.
- Your existing number stays on the app while you build and test the API setup.
- You can gradually shift customers to the new number by updating your website, ads and profiles.
- The downside is that customers need to learn a new number, and you may run two numbers for a time.
Prepare before you switch
- Choose a quiet time to migrate, avoiding peak days and seasonal campaigns.
- Make sure you control the SIM or number so that you can receive verification codes.
- Collect your customer list with confirmed opt-in consent records in place.
- Prepare templates and quick replies in Arabic and English, so that you can respond from day one.
- Train your team on the new inbox.
- Prepare an announcement for customers explaining any short interruption and the benefits, such as faster replies.
Keep your assets in your name
Make sure the Meta Business account and the WhatsApp Business account are owned by your company, not by an agency or freelancer. This protects you if you change provider later.
After migration
- Check that messages arrive and send correctly.
- Check that your profile, display name and logo are right.
- Monitor quality and customer feedback.
- Set up your opt-in capture and consent records.
- Start gradually with templates and broadcasts to opted-in customers.
Our setup guide and quality guide explain the next steps.
Common problems and how to avoid them
- Verification code not received: confirm the number can receive SMS or calls and that nothing blocks them.
- Display name rejected: align it with your business and website.
- Lost chat history: back up first and set expectations with your team.
- Downtime longer than expected: plan the timing and have a temporary channel, such as a link to your booking page.
- Number banned or restricted: avoid unofficial tools and follow the policy.
Frequently asked questions
Will I lose my WhatsApp Business app?
That depends on the setup and current options. Ask your provider what is available before you start.
Will customers see a new contact?
If you migrate the same number, they see the same number, though the profile may show your updated business information.
Can I go back to the app?
It may be possible, but it involves deregistering the number from the API and has limits. Plan the move carefully.
Messaging Limits and Portfolio Scaling After Migration
When migrating to the WhatsApp Business Platform, your messaging allowance is managed at the business portfolio level rather than per individual phone number. A newly created portfolio starts with a messaging limit of 250 unique recipient customers outside open customer service windows over a rolling 24-hour period. As your messaging volume grows, your portfolio can scale through defined tiers: 2,000, 10,000, 100,000, and unlimited.
To move from the initial 250 tier to 2,000, a business can either complete business verification or deliver template messages to 2,000 unique customers within a 30-day period while maintaining high template quality. Once above 2,000, automatic scaling up to the next tier typically occurs within about six hours when message quality remains high across all portfolio numbers and you have utilized at least half of your current limit in the previous seven days. Additionally, an unverified portfolio is capped at registering two phone numbers, whereas business verification or reaching the 2,000 limit increases that registration cap to 20 phone numbers.
Coexistence Onboarding: Running the App and API Simultaneously
For businesses hesitant to lose the familiarity of the mobile app, Meta offers coexistence onboarding (also called WhatsApp Business app onboarding). This feature allows a single phone number to operate on both the WhatsApp Business app and the Cloud API concurrently through a Solution Partner or Tech Provider.
While coexistence maintains chat history synchronization for up to the last six months and keeps app messages free, several technical limitations apply:
- API message throughput is fixed at a lower rate.
- App broadcast lists become read-only, and new broadcast lists cannot be created in the app.
- Features such as WhatsApp groups, live location, voice calling, disappearing messages, and view-once media are not supported on the API side.
- Onboarding unlinks existing companion devices attached to the mobile app.
Because regional availability and rollout specifics can vary by market and provider, businesses in the UAE and MENA region should consult their Solution Partner to confirm whether coexistence is supported for their specific phone numbers before initiating onboarding.
Post-Migration Billing Model and Currency Settings
After migrating to the API platform, messaging costs are billed per delivered message based on message category (marketing, utility, authentication, or service) and recipient country calling code. Key billing guidelines to keep in mind include:
- AED billing option: Businesses creating a new messaging account can select AED as their billing currency, which is one of sixteen enabled billing currencies. Once selected during account creation, the billing currency cannot be modified.
- Service message allowances: Each business phone number receives 1,000 free delivered service messages per month. Service messages delivered beyond this allowance are subject to per-message charges.
- Customer service window: Opening a 24-hour customer service window allows non-template replies (text, media, interactive Flows, and buttons) without requiring pre-approved templates.
- Per-user marketing limits: Meta may cap the number of marketing templates an individual user receives across all businesses. If a marketing send is blocked due to frequency caps, system error 131049 is returned, and retries should be delayed by at least 24 hours.
Policy Compliance and AI Rules for Regional Businesses
Operating on the API requires strict compliance with Meta's Business Messaging Policy. Businesses must obtain explicit consent before sending messages and provide clear opt-out mechanisms. Furthermore, businesses deploying AI solutions must ensure their provider does not use WhatsApp platform data to train generative AI models. Customer service chatbots answering questions about your products and services are permitted, but general-purpose AI assistant services offering general AI as their primary function are prohibited.
Our onboarding team plans migrations with you, from backup to verification and templates. Message us on WhatsApp or book a free 30-minute call.
Want help putting this into practice?
Book a free audit and we will review your marketing and suggest the quickest wins.
