How to Move Your WhatsApp API to a New Number Without Losing Customers

Changing your business phone number is a major headache. When that number is tied to your WhatsApp Business API, the headache can quickly turn into a business emergency. If you do this wrong, you can lose your customer chat histories, get your new number banned for spam, or find yourself locked out of your Meta Business Manager.

You cannot simply click a button and swap numbers. Meta does not work that way. However, you can execute a clean transition if you understand the limits, the technical steps, and how to manage your customers during the move. Here is exactly how to do it without losing your audience or your sanity.

The Hard Numbers: Limits, Quotas, and Spam Risks

Before you purchase a new SIM or register a new virtual number, you must understand the rules Meta enforces on new API endpoints. You cannot bypass these limits. If you try, your API integration will stop working.

When you register a new phone number on the WhatsApp Business API, it starts at Tier 1. It does not matter if your old number was sending 100,000 messages a day. Your new number starts fresh. Here are the limits you will face immediately:

If your business regularly sends shipping notifications or marketing updates to 5,000 customers a day, you cannot send them all from your new number on day one. If you try, your API calls will return error code 131051 (Message send limit reached) or error code 131048 (Spam rate limit exceeded). You must scale up slowly.

The second major risk is your quality rating. When you message customers from a new number, they will see the default WhatsApp security prompt: "This sender is not in your contacts. Block or Report?" If even 3% of your recipients click "Report" because they do not recognize your new number, your Quality Rating will drop from Green (High) to Red (Low). If it stays Red for too long, Meta will restrict your messaging limit to 250 conversations per day, or flag your account entirely.

Why You Cannot Just "Transfer" Your Data

Let us clear up some common misconceptions. You cannot transfer certain assets between two different phone numbers, even if they are in the same Meta Business Manager. This is a technical limitation of the WhatsApp infrastructure.

• Chat History: Meta does not store your chat histories on their Cloud API servers in a way that allows migration to a new number. Your old chats will remain in your database or customer relationship management (CRM) software, but they will not appear under the new number's threads.
• The Green Tick (Official Business Account): This status is tied directly to the specific phone number, not just your business name. If you move to a new number, you must apply for the Green Tick again. There is no guarantee Meta will approve it a second time, as their approval criteria change frequently.
• Opt-In Status: Legally and technically, your customers opted in to receive messages from your old number. While you can legally transfer this consent if your terms of service allow it, spam filters do not know that. A sudden message from an unknown number looks like spam to the end-user.

You can, however, share your message templates. If you register your new number under the exact same WhatsApp Business Account (WABA) as your old number, you can use your existing approved templates immediately. If you create a new WABA, you must submit all your templates for approval again, which can take up to 24 hours per template.

The Step-by-Step Migration Strategy

To keep your customers, you must run both the old number and the new number in parallel for a set period. Do not shut down your old number on day one. That is a critical mistake.

Step 1: Prepare and Clean the New Number

You must use a clean number. If the new number has been used on a personal WhatsApp or WhatsApp Business App recently, you must delete that account first. You cannot register a number on the API if it is currently active on a physical phone app.

To delete the old association, open WhatsApp on your phone, go to Settings, select Account, and click "Delete My Account". Wait at least five minutes before attempting to register it on the API. If you do not do this, the API registration will fail with an error stating the number is already registered.

Step 2: Add the Number to Your Existing WABA

Go to your Meta Business Suite, navigate to the WhatsApp Manager, and select your current WABA. Click on "Phone Numbers" and then "Add Phone Number". Fill in your display name and category. Verify the number using SMS or a voice call. This process takes about three minutes if you have the physical SIM card or virtual routing active.

Step 3: Set Up the Redirection Webhook

Since your old number is still active, you should configure your server or CRM to handle incoming messages on the old number by sending an automated redirection message. This message must use an approved template. It should inform the customer that your number has changed and provide a quick-action button to start a chat with the new number.

Here is an example of the JSON payload you would send from your server to your old API endpoint when a customer messages you:

{
  "messaging_product": "whatsapp",
  "to": "923001234567",
  "type": "template",
  "template": {
    "name": "number_change_alert",
    "language": {
      "code": "en"
    },
    "components": [
      {
        "type": "button",
        "sub_type": "url",
        "index": "0",
        "parameters": [
          {
            "type": "text",
            "text": "chat-with-us"
          }
        ]
      }
    ]
  }
}

The button in this template should contain a wa.me link pointing to your new number, like this: https://wa.me/923007654321?text=Hi. When the customer clicks this button, their WhatsApp app will automatically open a new chat window with your new API number.

Step 4: Update Your Entry Points

Do not forget your physical and digital entry points. You must update:

• Your website chat widgets and contact pages.
• QR codes printed on packaging, flyers, or business cards.
• "Click to WhatsApp" ads running on Facebook or Instagram.
• Your Google Maps contact details.

If you are using a platform like WA Link to generate your WhatsApp chat links and manage customer routing, you can update the destination number inside your dashboard. This saves you from having to change the actual links on your website or reprint physical QR codes, as the short link remains the same while the backend routing changes to your new number. However, keep in mind that WA Link only manages the redirection links; it cannot bypass Meta's core API limits or move your message templates automatically.

The Warm-Up Schedule: How to Avoid the Spam Trap

You must train Meta's filters to trust your new number. To do this, you must start by sending messages only to your most active, highly engaged customers. These are the people who are least likely to report you as spam.

Follow this 10-day warm-up schedule to safely transition your traffic:

During this period, check your Meta Business Manager daily. Go to the "Phone Numbers" tab in your WhatsApp Manager and look at the "Quality Rating" column. If it drops to "Medium" (Yellow), stop sending outbound marketing messages immediately. Only reply to incoming customer queries until the rating returns to "High" (Green).

When Changing Your Number is the Wrong Decision

Sometimes, moving to a new number is a bad idea that will cause more harm than good. You should avoid this move in the following scenarios:

To Escape a Low Quality Rating

If your current number is restricted or has a Red quality rating because you sent unsolicited marketing messages, do not just register a new number to bypass the restriction. Meta's automated systems track the domain names inside your message templates, your Facebook Business Manager ID, and your payment details. If they see a pattern of a business repeatedly abandoning low-quality numbers to start new ones, they will permanently ban your entire Meta Business Account.

When You Use Virtual Numbers From Unverified Providers

If you are buying cheap virtual numbers from random online sellers to run your API, stop. Meta regularly audits phone number ranges. If they identify a range belonging to a low-quality VoIP provider, they may flag or disable all API integrations associated with those numbers. Always use a real SIM card from a major telecom operator (such as Jazz, Telenor, Airtel, or Jio) or a business-grade virtual number from an official provider.

Managing the Transition Realistically

A successful transition takes about two weeks of dual-running. You will pay Meta's conversation fees on both numbers during this time, but this is the cost of keeping your customer base. If you cut the old number off instantly, you will lose up to 40% of your incoming customer traffic because people will continue to message the old contact thread they have saved on their phones.

Keep your developers close during the first three days of the switch. Monitor your webhook error logs for any failed delivery payloads. Once your new number has successfully scaled to Tier 2 and your incoming traffic on the old number has dropped to near zero, you can safely delete the old number from your WhatsApp Business Account and shut down its hosting instance.

Frequently Asked Questions

Can I use my old API number on my phone's WhatsApp Business App after the move?

Yes. But you must first delete the number from your WhatsApp Business API configuration in the Meta Business Manager. Once deleted, wait about ten minutes, then download the WhatsApp Business App on your phone and register the number normally. If you do not delete it from the API first, the phone app will tell you the number is invalid.

What happens to pending messages in my queue when I switch numbers?

They will fail. Meta's API queue is tied to the specific phone number endpoint. If you have messages queued up to go out on your old number and you delete that number, those messages will be lost. You must pause your sending systems, let your queue clear completely, and then update your API endpoint configuration to the new number.

Do I have to pay Meta twice for the same customer during the migration?

Yes, if you message them from both numbers. If a customer messages your old number, you pay for a service conversation on that number. If you then redirect them to your new number and start a new conversation there, Meta views this as two separate conversations and will charge you for both according to their standard regional pricing.