How to Migrate WhatsApp API to a New Provider Under Meta’s 2026 Account Model

When a business needs to migrate WhatsApp API service to another platform, the business account settings need close attention. Under Meta’s new account model, switching providers means sharing the existing WhatsApp account with the new partner, setting it up, and then unsharing the old one.

Understanding this transition keeps the operation online and the AI agent running. Below are the practical steps and the most common mistakes to avoid so the switch happens safely and quickly.

Key Takeaways

• The number no longer moves between accounts: the business shares access with the new provider.
• Conversations are not interrupted (no downtime) when the business changes partners.
• Templates must be recreated or copied with the Template Migration API.
• Messaging limits and the number’s quality rating stay the same under the new model.

Understanding Meta’s New Account Model

The process of switching providers went through a recent structural change that affects how businesses manage their numbers. Traditional migration has given way to a system based on shared access, which simplifies the technical transition and reduces downtime.

The Move to a Sharing Model

The update to the new format began rolling out in phases on September 23, 2026, and is expected to reach all businesses by mid-October 2026. Meta moves accounts to the new architecture automatically. From then on, migrating a business phone number from one partner to another is no longer supported the old way.

Instead of transferring the number, the business now shares its existing account with the new partner. The number stays where it is, which makes life easier for anyone using the official WhatsApp API. The customer grants access to the new provider and, after setting up the environment, removes access for the previous platform. The same logic clarifies the path for businesses that want to move from an unofficial API to coexistence.

IDs and Tokens Stay the Same

Despite the change in how access is shared, existing IDs, endpoints, and tokens keep working with no changes to the core setup. Because the account is shared with both partners at once, conversations are not interrupted during the switch. That keeps customer service and existing database integrations running without a break.

With the connection stable, the technical team only needs to adapt message templates and system instructions. Templates belong to the Messaging account where they were created, so they must be recreated or copied with the Template Migration API. Once the approved messages are in place, the business can organize its documents and train the AI on company data to start operating with the new partner.

Preparing Before You Switch Providers

Before starting the hands-on process to migrate WhatsApp API service, the business should take stock of its current assets. Structured planning prevents communication failures and protects operational data during the move between customer service platforms.

Inventory of Templates and Opt-Ins

Listing every active message template is the first critical step. According to Meta, templates belong to the Messaging account where they were created and are not shared between those accounts. To reuse them in the new system, the team must recreate them or copy them with the Template Migration API. Understanding the WhatsApp Business API changes in 2026 helps plan this transfer without interrupting active campaigns.

Organizing the contact permissions (opt-ins) recorded in the customer base keeps the business compliant with platform policies. The business should export the updated list of contacts who agreed to receive messages, grouped by interest category. This care protects the number’s quality rating and lowers the risk of spam reports when sends start in the new environment.

Mapping Integrations and Webhooks

Every connected system, such as CRMs, databases, and automation tools, needs to be documented. The technology team should list each active endpoint that sends or receives data through the messaging channel. This map shows which data flows depend on the current connection and sets the right order for reconfiguring each service.

Technical preparation centers on pointing the webhooks to the new Tech Provider verified by Meta at the right time. The migration schedule should plan the integration cutover right after the WhatsApp account is shared, so incoming messages are routed correctly. Documenting these technical paths in advance speeds up adoption of the new platform and keeps automated customer service stable.

Step 1: Share the Account With the New Partner

The first hands-on step to migrate WhatsApp API service under Meta’s new model is granting access to the new technology provider. It all happens in Meta’s official tools, with no need to shut down the previous infrastructure right away.

Access Through Embedded Signup

The business uses the Embedded Signup flow to connect the new technology partner to the existing operation. According to Meta, the transition request is rejected if the destination account does not own the phone number. This strict check reinforces system stability and avoids the common risks faced by organizations that still rely on an unofficial WhatsApp API.

Disconnecting the number from the current account does not make it available for transfer under the new rules. Sharing the WhatsApp account remains the official way to add providers. Following the right flow prevents system interruptions and restricted-account scenarios, so customer service stays active throughout the transition.

Creating the New Messaging Account

Transferring an entire WhatsApp Business Account (WABA) is not part of the new account model. The customer does not need to unshare the account from the current partner to start setup with the newly hired provider. According to the official documentation, the business shares its WhatsApp account with each technology partner simultaneously and independently.

In this format, each partner gets its own Messaging account linked to the same business number. This lets the business configure the new platform and set up integrations before turning off the previous solution. In practice, this split means:

• The number stays where it is, with no drop in incoming messages.
• The IDs, endpoints, and tokens of the old operation keep working in the meantime.
• The new Messaging account keeps new customer service and automation flows separate.

Step 2: Copy and Recreate Message Templates

When you migrate WhatsApp API service between providers, message templates need special attention because they do not transfer automatically. Meta provides tools to make the technical copy easier and avoid pauses in the operation.

Using the Template Migration API

According to Meta, templates belong to the Messaging account where they were created and are not shared between accounts. When adding a new provider, the business needs to move its approved library to the new structure. Without this step, WhatsApp bulk messaging campaigns come to a halt.

The business uses the Template Migration API to copy approved templates programmatically. This keeps communication active with the new provider, so notifications go out without interruption. The scenario calls for the same planning discipline used when deciding when to migrate from the WhatsApp Business app to the API.

Quality Rules and Re-Review

Duplication has specific eligibility criteria. Under the Embedded Signup rules, only approved templates with GREEN quality can be duplicated through the API. Templates with lower quality, or paused ones, must be recreated manually and reviewed again.

Duplicated templates start with an UNKNOWN quality rating for 24 hours, while Meta re-evaluates the category of each one. Template performance directly affects WhatsApp API messaging limits, so the first few days need monitoring to protect the number’s reputation.

Step 3: Set Up Billing and Costs

Switching providers on Meta’s official API directly affects how conversations are billed. Understanding how costs are split during the switch is essential to keep finances organized and avoid service interruptions.

How Billing Moves Between Providers

During the platform switch, financial responsibility for message traffic changes as soon as the new setup is active. According to Meta, conversations delivered before the migration is complete are billed to the old Solution Partner, while messages delivered afterward are billed directly to the customer.

This change in the payment model requires the organization to keep a valid credit card set up in Meta Business Suite. When building a WhatsApp chatbot on the new provider, the finance team needs to make sure the credit line covers the daily volume of customer service and lead qualification.

Simulating Costs With the Calculator

Financial planning requires predictability for bulk sends and for conversations started in the inbox. Meta bills per delivered message, by category, such as marketing, utility, and service, each with its own rate, and by the recipient’s country, as shown on the official pricing page. Mapping this flow is an important step when rolling out artificial intelligence for sales and support.

To estimate the monthly budget accurately, the team can run the numbers in the cost calculator for the official API. The tool projects total spend from the expected conversation volume and gives a clear view of the investment needed to keep AI agents running 24 hours a day.

Step 4: Unshare the Old Provider

After validating the new provider and copying the message templates, the business ends the previous platform’s access. Links are removed directly in the Meta Business Suite admin panel, so the operation runs only on the new infrastructure.

Removing the Old Messaging Account

Ending the link requires the business to open Meta Business Suite settings with an admin profile. There, managers find the digital assets linked to the business phone number and identify the active messaging accounts. This initial audit organizes the transition and prepares the environment to cut off the previous platform’s access.

The first required step is to unshare the Messaging account that belongs to the previous partner, as Meta’s documentation explains. Removing it stops the old platform from operating the number and isolates the settings and history tied to that specific messaging account.

Unlinking the WhatsApp Account

After removing the Messaging account, the business moves to the second access cleanup step in the business manager. This consolidates the transition, keeping only the links to the new platform chosen to provide AI agents for WhatsApp and the team inbox.

The final action is to unshare the WhatsApp account associated with the number, ending the link with the old provider for good. With these two removals done in sequence, the organization centralizes management of Meta’s official API with the new partner and reduces the risk of technical interference.

Step 5: Validate the Operation and Sending Limits

Day-to-day operations need stability after the provider switch. The platform’s new account model preserves the reputation history of the business number, so there is no long warm-up and the established conversation volume stays in place.

Messaging Limits and Throughput Stay in Place

Moving to a new partner does not affect the business’s established sending capacity. According to Meta, the display name, quality ratings, and messaging limits do not change under the new account model. Businesses with high bulk-sending volume keep the same reach, with no setback in daily sending scale.

The current architecture assigns technical resources clearly across connected accounts. Throughput is still set at the phone number level, while the messaging limit stays at the business portfolio level. These limits are shared among partners using the same number at the same time, so delivery metrics need monitoring to keep campaigns and automation stable.

Communicating With the Customer Service Team

Training agents on the new multi-agent inbox is a key step to keep customer support running smoothly. The team needs to master the interface, understand how AI agents for WhatsApp are triggered, and manage conversation history. Familiarity with the new dashboards cuts response times and increases the chance of resolving daily requests quickly.

Aligning everyone on the transition prevents communication failures with customers. During the short period when both providers have access to the account, a few specific actions prevent duplicate replies:

• Set exact times for the cutover between platforms.
• Pause automations on the old provider before turning them on in the new system.
• Follow the first tickets in the new inbox to validate the customer service flow.

Common Questions About the New Account Model

Sharing access raises common questions among managers who decide to migrate WhatsApp API service to a Tech Provider verified by Meta. The answers below clarify the main technical and operational points for keeping the business running.

Is Customer Service Interrupted During the Process?

There is no downtime in communication with customers. Moving off a solution to a new technology provider through Embedded Signup does not require verifying the phone number again, so the operation stays active end to end.

Conversations stay open and customers do not notice the infrastructure change behind the scenes. Because the WhatsApp account is shared instead of physically transferred, support and sales messages flow normally while the new platform is set up.

How Does Coexistence With the WhatsApp Business App Work?

The business phone number stays active in the WhatsApp Business app installed on the company phone. This setup lets the team keep using the phone in the field or at the counter, while the system manages automation and artificial intelligence agents in the cloud.

Messages sent directly from the phone are reflected in the web system in real time. In the platform inbox, these manual messages are labeled “Sent from phone”, which helps managers separate what was typed on the smartphone from what was handled by automation.

Are Old Templates Duplicated Automatically?

Automatic duplication does not happen under the new account model. Message templates belong to the original messaging account and do not move to the new shared workspace on their own.

The business has to recreate the messages or copy the templates in bulk with the Template Migration API. According to Meta, only templates with GREEN quality are eligible for this copy, and duplicated items start with UNKNOWN status for 24 hours until their category is re-evaluated.

Does the Number Need to Be Verified Again?

The new infrastructure model removes the need to verify the phone number again when switching technology partners through Embedded Signup. The original verification remains valid throughout the vendor transition.

The process focuses only on sharing access in Meta Business Suite, which makes new tools easier to adopt. That reduces technical friction and speeds up advanced solutions, such as AI agents built on the company’s own knowledge base.

Frequently Asked Questions

Conclusion

Moving to the official WhatsApp API with support from intelligent agents simplifies the operation and raises the quality of customer service, as long as the migration plan follows Meta’s technical guidelines. A structured platform keeps conversations going, protects the number from blocks, and brings artificial intelligence straight into the team’s routine.

To put this into practice with AI agents and the official WhatsApp API, take a look at ConverZAP.