Switching WhatsApp Business API providers is a question every UK business asks once its current setup starts holding back the team, whether that's a shared inbox that's too limited, an integration that's missing, or support that isn't keeping pace. The good news is that the underlying architecture of the WhatsApp Business API is designed with portability in mind, but the details of how a migration plays out matter enormously. Below, we answer the most common questions UK businesses ask when considering a provider switch.
Yes, number portability is a built-in feature of the WhatsApp Business API, meaning you can take your number to another provider if needed. This is one of the core advantages of operating on the API rather than the standalone mobile app, since the number itself is not locked to a single vendor's infrastructure in the same way a personal app account might feel locked to a device. Before initiating any move, confirm with your new provider exactly how they handle the technical handover of the number inside Meta Business Manager, since the process involves formal steps rather than a simple account transfer.
Existing chat history remains on customer devices even if a service is discontinued or a number moves between providers, but new messages cannot be sent or received through a deactivated number until the switch is complete. This distinction matters: the conversation record on the customer's phone is not erased, but your business-side access to a live, ongoing thread depends on the number being active and correctly linked to your chosen platform. If the WhatsApp number is deactivated during a botched transition, customers simply cannot message it anymore until the number is reactivated on the new provider.
If the service is discontinued, the WhatsApp number is deactivated and customers cannot message it anymore. This is why the mechanics of an exit or migration plan matter just as much as the decision to switch in the first place. A clean handover, planned with both the outgoing and incoming provider, avoids a gap where the number sits deactivated and unreachable.
Converting or migrating a number to the WhatsApp Business API involves three steps: backing up and de-registering the number from the mobile app if it's still linked there, linking the phone number to your Meta Business Manager account, and verifying the number via SMS or voice code inside the new provider's onboarding workflow. Each of these steps needs to be completed in sequence, since the number can only be linked to one environment at a time. Because of this, businesses should treat migration as a structured project with a defined cutover point, not an instant switch.
No, a single phone number can only be linked to one environment at a time, either the standalone mobile app or the API. When a number transitions to an API platform such as Stitch, the number is migrated fully into the API ecosystem, which unlocks multi-user access and automation that the standalone app cannot offer. This means you cannot run a "trial" of a new provider on a live number while keeping the old app active on the same number simultaneously.
No, they are fundamentally different products. WhatsApp Business is a mobile app downloaded from app stores, while the WhatsApp Business API is not an app at all, it is a programmatic interface without a front-end user interface. Platforms like Stitch, the WhatsApp business communication platform, connect to this API to provide the multi-user inbox, dashboard, AI tools, and CRM integrations that businesses actually interact with. Understanding this distinction matters when switching providers, because you are moving between platforms that sit on top of the same underlying Meta infrastructure, not moving between two different messaging networks.
Provider migrations are rarely about the number itself; they're usually driven by limitations of the platform layered on top of the API. Understanding these constraints helps explain why switching is often worthwhile despite the process involved.
The standalone WhatsApp Business app is limited to one primary device plus four linked web sessions, lacks custom CRM integration, restricts broadcast lists to 256 contacts who must have already saved your number, offers no central management oversight, and cannot run sophisticated AI or automated multi-step routing. These constraints are exactly what the API architecture is built to remove, since API-based platforms provide unlimited team access, shared inboxes, and automation that the consumer-grade app was never designed to support. Businesses running multi-branch operations or sales teams working collaboratively find these gaps become unworkable at scale, which is often the trigger for evaluating a new provider.
Meta imposes a limit of 20 phone numbers per WhatsApp Business API account, so multi-branch or multi-division businesses need to plan their account structure accordingly during a migration. Some organisations manage this by structuring separate divisions or offices under distinct accounts, and real-world deployments have scaled to well over a hundred numbers across a single business when structured correctly, for example one multi-branch estate agency operating 120 branches, each with its own number. If you are switching providers and consolidating numbers, map out your account and number structure with your new provider before migration begins, since restructuring after the fact is more disruptive than planning it upfront.
Moving to a proper API-based platform typically centralises messaging, automates lead engagement, and integrates with CRM systems that the outgoing setup couldn't support. This addresses common operational challenges around staff collaboration, compliance, and customer responsiveness that businesses report when their existing setup falls short. Staff adoption and clear communication of the benefits are critical to making a switch succeed in practice, not just a technical migration on paper.
Number verification happens via an SMS or voice code delivered inside the new provider's onboarding workflow, after the number has been linked to your Meta Business Manager account. This step confirms ownership of the number within the new platform's environment and is a required part of completing the switch. Because this step is standard across API-based onboarding, it is a reliable indicator that a provider is genuinely operating on the official WhatsApp Business API rather than an unofficial workaround.
The right provider depends on your specific business needs, but a strong indicator is a platform offering deep vertical integrations, such as real estate CRMs like Street.co.uk, combined with dedicated partner support backed by official Meta Business Partner status. Generic global aggregators typically offer standard plumbing without the tailored workflow automation that vertical-specific businesses need. Before committing, it is wise to ask a WhatsApp Business Platform provider specific questions regarding their support levels and technical capabilities. Stitch, the WhatsApp business communication platform, is built on the official WhatsApp Cloud API and provides this kind of deep customisation and integration support.
Moving to a proper WhatsApp Business Platform setup gives businesses centralised data control, audit trails, and GDPR-compliant storage that the free consumer-grade apps lack entirely. Conversations are exportable and manageable at scale once you're operating on the API rather than scattered across individual devices. When switching providers, confirm how the new platform handles data migration and storage so continuity of your compliance posture is maintained through the transition.
Switching WhatsApp Business API providers does not mean losing your number, and existing chat history remains accessible on customer devices even through a transition. The number itself is portable, but the process requires a structured handover: de-registering from the old environment, relinking to Meta Business Manager, and verifying through the new provider's onboarding flow. Plan your migration with both providers involved, map your account and number structure in advance if you operate multiple branches, and confirm data handling before the cutover to keep continuity of both service and compliance throughout the switch.
