How to Migrate Your Number to the WhatsApp Business API

To migrate a phone number to the WhatsApp Business API, back up your chats, disable two-step verification, delete the number from the WhatsApp Business app, choose a Meta-approved Business Solution Provider, complete Meta Business Verification, add the number to a WhatsApp Business Account, receive the OTP, and approve your display name. The process usually takes three to seven business days with no loss of your phone number.

Your sales team is sharing a single phone, your support tickets are piling up in a personal chat, and your latest promotional broadcast hit the 256-contact ceiling of the WhatsApp Business app. You are not outgrowing WhatsApp; you are outgrowing the consumer app. Migrating your number to the WhatsApp Business API is the next step, and done correctly it preserves your existing customer base, your display name, and your conversation history without forcing you onto a new number.

This guide walks you through the full migration process: what to prepare before you start, the exact sequence Meta requires, how a Business Solution Provider like Notify Africa handles the technical lift, and what to do in the first two weeks after you go live to protect your messaging tier and quality rating. It is written specifically for businesses operating in Tanzania, with the local network, regulatory, and language details that generic guides usually skip.

What Is WhatsApp Business API Migration?

WhatsApp Business API migration is the process of moving a phone number that is currently registered on either the free WhatsApp Business app or another Business Solution Provider into a new WhatsApp Business Account hosted on Meta's Cloud API. The number itself does not change, but the underlying account, billing relationship, and technical access change completely.

There are two common migration paths. The first is moving a number off the free WhatsApp Business app and onto the API for the first time. The second is moving a number from one BSP to another, often referred to as a BSP transfer or BSP-to-BSP migration. The prerequisites overlap, but the sequence and the assets you keep are different in each case.

When the migration is executed correctly, your phone number, display name, quality rating, messaging tier, approved templates, and Official Business Account status all carry over to the new WhatsApp Business Account. According to Meta's partner documentation, a properly executed migration involves no downtime and your customers continue to see your verified business profile throughout.

Source Versus Destination WABA

Two terms appear repeatedly in Meta's documentation and in every BSP onboarding flow, so it is worth defining them now. The source WhatsApp Business Account is the account your number currently lives in, whether that is the free WhatsApp Business app or another provider. The destination WhatsApp Business Account is the new account, hosted under the BSP you are moving to. For Notify Africa clients, the destination WABA sits inside our Meta-approved Cloud API infrastructure.

For phone numbers moving from one BSP to another, both WABAs must sit under the same Meta Business Portfolio, or the new BSP must initiate the transfer through Meta's Embedded Signup flow. Skipping this step is the single most common reason migrations stall in the verification queue.

Why Migrate to the WhatsApp Business API in the First Place?

The free WhatsApp Business app is designed for sole traders and very small operations. Once a business needs multiple agents replying from one number, automated workflows, CRM integration, or campaign volumes above a few hundred contacts, the app stops being viable. The WhatsApp Business API solves all of these constraints, but the trade-off is that you must work through a Business Solution Provider and follow Meta's onboarding rules.

The most common business triggers for migration are familiar to anyone who has scaled a WhatsApp channel. Multiple staff members trying to reply from one phone leads to missed messages and duplicated responses. Broadcast lists capped at 256 contacts make any meaningful campaign impossible.

There is no way to connect the conversation to your CRM, your sales pipeline, or your ticketing system. There is no API for sending order confirmations, delivery updates, or OTPs at the moment the event happens. And there is no way to deploy an AI assistant that handles common questions twenty-four hours a day.

Migrating to the API unlocks all of these capabilities. You gain a multi-agent shared inbox, programmatic message sending, message templates approved by Meta for outbound use, webhook events for every delivery and reply, and direct integration with chatbots, automations, and analytics dashboards. For Tanzanian businesses, it also unlocks bulk WhatsApp campaigns across Vodacom, Airtel, Mixx by Yas, and Halotel through a single platform like the Notify Africa WhatsApp marketing platform.

Industries That See the Fastest Return on Migration

Some sectors recover the migration effort almost immediately. Banking and microfinance use the API for transaction alerts and OTPs. Logistics and ride-hailing send dispatch and ETA updates. E-commerce and retail handle order confirmations and abandoned-cart recovery. Education and training institutions send fee reminders and class updates. Healthcare clinics send appointment confirmations and follow-up reminders. Each of these use cases requires the API because the messages are triggered by events in another system, not typed by a human into a phone.

What Do You Need Before You Migrate?

Meta will not begin the migration until your business and your number satisfy a defined set of prerequisites. Working through this checklist before you start removes the back-and-forth that delays most onboarding by a week or more.

You need a Meta Business Portfolio, formerly called Business Manager, registered to your company. You need a verified business identity inside that portfolio, which requires a few standard documents. You need a phone number that can receive an SMS or a voice call. You need administrator access to whichever Facebook account owns the Business Portfolio. And you need to be ready to disable two-step verification on the number you are migrating.

Phone Number Requirements

The phone number you migrate must meet a few specific criteria. It must be able to receive an SMS or a voice call for the one-time password. It must not already be active on the free WhatsApp or the WhatsApp Business app at the moment of API registration. If it is, you have to delete the WhatsApp account on that number first. Two-step verification must be turned off. The number can be a mobile or a landline, and Meta accepts numbers from any of the major Tanzanian networks including Vodacom, Airtel, Mixx by Yas, and Halotel.

A common question is whether you can keep the number running on the consumer app while the migration is in progress. The honest answer for a full migration is no. Once you delete the WhatsApp account to start API registration, incoming messages are held by Meta's servers until the new registration completes. Meta has introduced a Coexistence feature that allows the app and the API to share a number under specific conditions, but the safer default for a clean migration is to schedule it during your lowest-traffic window.

Display Name Approval

Your display name is the business name customers see at the top of every chat. Meta reviews every display name against its WhatsApp display name guidelines, and getting this right the first time saves a full day of waiting. Use the legal trading name of your business, avoid emojis and stylized characters, and avoid generic terms like Customer Support or Sales Office on their own. If your registered business name is long, an approved short form tied to your brand is usually accepted. Approval typically takes between twenty-four and forty-eight hours.

How Do You Migrate Your Number Step by Step?

This is the standard sequence Meta requires, condensed into the order an end-business actually experiences it. Some steps are handled by your BSP, some require you to act inside the WhatsApp app on your phone, and some happen inside the Meta Business Manager.

The first step is choosing your BSP.

This decision affects everything downstream because the BSP owns the technical relationship with Meta, the pricing structure, the dashboard you will use day to day, and the local support you can call when something breaks. For Tanzanian businesses, choosing a Meta-approved Business Solution Provider with local presence, local payment options, and Swahili support is a meaningful difference once campaigns are live.

The second step is creating or confirming your Meta Business Portfolio.

If you already have one with Business Verification completed, you skip ahead. If not, you go to business.facebook.com, create a portfolio, fill in the legal business information completely, and start Business Verification by uploading the documents listed earlier. Verification takes between two and fourteen days depending on document quality.

The third step is backing up the data on the number you are migrating.

Open WhatsApp on the phone, go to Settings, Chats, Chat Backup, and run a full backup to Google Drive or to your phone's storage. Export contacts and any saved quick replies. After migration the conversation history on the consumer app will no longer be accessible from the API side, and there is no way to import it later.

The fourth step is disabling two-step verification on the number.

In the WhatsApp Business app, go to Settings, Account, Two-step verification, and turn it off. If the number is currently with another BSP and you do not have direct access, your current provider must do this for you, and they have to do it before the migration window starts.

The fifth step is deleting the WhatsApp account on that number.

This is the irreversible step, so it should be done at the agreed migration window, not earlier. Go to Settings, Account, Delete My Account, and confirm. From this moment, incoming messages are held by Meta's servers until the API registration completes.

The sixth step is the BSP-side registration.

Your BSP, working from the Notify Africa side or whichever provider you choose, opens a new WhatsApp Business Account under your verified Meta Business Portfolio, adds your phone number, submits your display name for approval, and triggers the OTP. You receive the OTP on the number, share it with the BSP through the agreed channel, and the BSP completes the verification.

The seventh step is profile setup and template submission.

With the number now connected, you set up your business profile inside the API, including your business description, category, address, email, and website. You also submit your first message templates for the categories you need: utility, marketing, and authentication. Template approval typically takes a few hours to a full day.

The eighth and final step is the test send.

The BSP sends a templated message from the API to a known number, confirms delivery, and hands the live dashboard over to you. The number is now operating on the WhatsApp Business API, and the migration is complete.

What Happens Right After the Migration?

The day after migration is when most new API accounts get into trouble. The temptation is to send the campaign that the WhatsApp Business app was holding you back from sending. This is the worst possible thing to do on a new number.

New WhatsApp Business Accounts that have completed Business Verification start at a daily messaging limit of 1,000 unique conversations initiated outside the customer service window, sitting in what Meta calls Tier 1. Unverified portfolios start at 250.

The limit applies at the portfolio level, not per number, since Meta moved to portfolio-wide limits in late 2025. Sending a 5,000-recipient blast on day one will cap at the tier limit, generate block reports from cold contacts, and freeze your tier upgrades for weeks.

The right approach is a gradual ramp-up over the first two weeks. Start with your most engaged contacts: people who have messaged you recently, repeat customers, and known opt-ins.

Send templated messages that match the category you submitted, and watch the quality rating on each phone number daily. If your quality rating stays at High and you use more than half your current limit consistently for seven days in a rolling thirty-day window, Meta will automatically upgrade you to the next tier. The progression usually runs 1,000, then 10,000, then 100,000, then unlimited.

Protecting Your Quality Rating

Quality rating is the single most important number after migration. It is driven by how many users block your number or report your messages as spam after receiving them. A block rate above two to three percent will drop your rating to Medium, and continued issues drop it to Low. A Low rating prevents tier upgrades and can result in messaging restrictions on the number.

The practical steps that protect quality are simple in principle and easy to ignore in practice. Send only to contacts who have given explicit opt-in. Keep your message content useful and relevant to what the customer signed up for. Include an unsubscribe instruction in marketing messages. Avoid sending the same template repeatedly to the same audience within a short period. And remove unresponsive contacts from your active list before they accumulate enough silence to drag your engagement metrics down.

Coexistence and the Multi-Channel Question

Many Tanzanian businesses run a mixed messaging strategy: bulk SMS for transactional alerts that need guaranteed delivery, and WhatsApp for richer marketing and two-way conversations. The API supports this naturally. A single platform that handles bulk SMS across Tanzanian networks alongside WhatsApp campaigns gives you one contact list, one opt-in record, one dashboard, and one set of analytics. This is the architecture most Notify Africa customers settle on after migration.

For developer teams integrating directly with backend systems, the same patterns apply on the SMS side. The Notify Africa developer documentation covers SMS API endpoints, retry logic, and webhook events that mirror the WhatsApp delivery model, which makes a unified messaging stack straightforward to build.

What Are the Most Common Migration Mistakes?

After running through dozens of migrations for Tanzanian businesses, a pattern of avoidable mistakes shows up repeatedly.

The first is starting migration without completing Business Verification first. Without verification, your portfolio is capped at 250 daily conversations forever, and you cannot scale even after the migration succeeds.

The second is name mismatches between the Meta Business Portfolio and the BRELA Certificate of Incorporation. If your portfolio says ABC Limited but your certificate says ABC Company Limited, verification will be rejected. The fix is to update the portfolio name to match the certificate exactly, then resubmit.

The third is using a personal phone number for the API. Once a number is on the API it cannot be used in the consumer WhatsApp app. If the migration target is the personal mobile of the business owner, that personal use is gone the moment the migration completes. Use a dedicated business line.

The fourth is sending a maximum-volume campaign immediately after going live. As discussed above, this caps the tier, generates block reports, and freezes upgrades. Ramp up over two weeks.

The fifth is skipping the conversation backup before deleting the consumer WhatsApp account. The chat history is genuinely gone after deletion. Back up to Google Drive before the agreed migration window opens.

The sixth, specific to businesses moving between BSPs, is forgetting to ask the source BSP to disable two-step verification on the number. Without this, the destination BSP cannot complete registration regardless of how perfectly everything else is configured.

Why Migrate to the WhatsApp Business API with Notify Africa?

Choosing a BSP is not just a technical decision. It is a long-term operational relationship with whoever holds your WhatsApp account, processes your billing, and answers your support calls when a template gets rejected at midnight.

Notify Africa is a Meta-approved WhatsApp Business Solution Provider built specifically for the Tanzanian market by iPF Softwares, an ISO 27001:2022 certified software company based in Dar es Salaam. The platform combines WhatsApp Business API, bulk SMS across Vodacom, Airtel, Mixx by Yas, and Halotel, AI chatbot infrastructure, and a unified team inbox in a single dashboard. Local payment is supported through M-Pesa, Mixx by Yas, Airtel Money, bank transfer, and card. The dashboard, support, and onboarding all operate in both English and Swahili.

For migration specifically, the difference is that the team handling your account understands the Tanzanian regulatory environment. The Personal Data Protection Act of 2022 governs how you collect and process customer data on WhatsApp, and the Tanzania Communications Regulatory Authority sets the rules for electronic communications more broadly. Working with a BSP that has navigated both is materially different from working with a global provider that treats Tanzania as a footnote.

The operational metrics matter too. The Notify Africa platform runs at 99.9 percent uptime, 24-millisecond latency, and a throughput of 5,000 messages per second across SMS and WhatsApp combined. Delivery rates average 98.5 percent across the four major Tanzanian networks. For a business migrating from the WhatsApp Business app, this is the difference between a campaign completing in minutes versus completing in days.

Notify Africa also offers AI chatbot and AI assistant solutions that plug directly into your WhatsApp number after migration, handling common customer questions in English or Swahili and escalating to your live team when a real person is needed.

Final Thoughts

WhatsApp Business API migration is a one-time operational project that unlocks every meaningful growth lever your business has on the channel. Done correctly, it preserves your phone number, your customer relationships, your display name, and your sending history, while removing every constraint that the consumer app imposes. The work is mostly preparation: getting Business Verification done, picking the right BSP, backing up chats, and lining up your first templates. The actual technical cut-over is the smallest part of the timeline.

The three takeaways that matter most for Tanzanian businesses are these. Complete Business Verification before you start the migration so you do not get capped at 250 conversations forever. Plan the cut-over for your lowest-traffic window because the number is offline for a few hours during registration. And do not send a maximum-volume campaign on day one — ramp gradually over two weeks to protect your tier and quality rating.

When you are ready to migrate, Notify Africa runs the entire process for Tanzanian businesses: document review, Business Verification support, display name pre-clearance, OTP coordination, template submission, and a guided first send. The same dashboard then runs your ongoing WhatsApp campaigns, bulk SMS across all Tanzanian networks, and AI chatbot automation.