Moving a business number onto a new WhatsApp platform raises one question above all others: what happens to the number itself and everything already sent through it. Stitch, the WhatsApp business communication platform, works directly with the official WhatsApp Business API, so the answer depends on understanding how that migration actually works rather than assuming it behaves like switching apps on a phone.
Yes, an existing WhatsApp Business number can be migrated onto the WhatsApp Business API platform. The process requires backing up and then deleting or de-registering the mobile account from the phone app, linking the phone number to a Meta Business Manager account, and verifying the number via SMS or voice code inside the Stitch AI onboarding workflow. This is a genuine migration of the number into a new ecosystem, not a copy or a duplicate registration.
Chat history does not carry over during migration. Deleting or de-registering the mobile app account as part of the transition process results in the existing chat history being lost. Businesses evaluating a move to an API-based platform should treat this as a firm limitation of the migration, not something to work around with a backup file, and should plan accordingly before deleting the original app installation.
A single phone number can only be linked to one environment at a time, either the standalone mobile app or the cloud API, never both simultaneously. This is a structural rule of how WhatsApp's infrastructure works, not a restriction specific to any one platform provider. When a number transitions to an API platform such as Stitch's, it moves fully into the API ecosystem, which is what unlocks unlimited team access and automation in place of the single-device app experience.
Before deciding how to handle a number transition, it helps to understand what the WhatsApp Business API actually is, since that shapes what migration involves and why chat history doesn't transfer.
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 connect to this API to provide the multi-user inbox, dashboard, AI tools, and CRM integrations that the raw API doesn't offer on its own. WhatsApp and WhatsApp Business are both owned and operated by Meta Platforms, Inc., with WhatsApp Business encompassing both the free Business App and the enterprise API platform. Understanding this distinction matters directly for migration: what businesses are moving away from is the standalone app's single-device model, and what they're moving into is a shared, multi-user environment.
The standard WhatsApp Business app is limited to one primary device plus four web links, lacks custom CRM integration, restricts broadcast lists to 256 contacts who must have saved the business's number, offers zero central management oversight, and cannot run sophisticated AI or automated multi-step routing. These limitations are precisely what drives businesses to migrate their number onto the API platform in the first place, since a shared team inbox and automation depend on infrastructure the app cannot provide. Recognising these constraints ahead of time makes it easier to plan for what the migration will and won't preserve.
The integration allows businesses to use the same number for personal and business WhatsApp messages. However, conversations initiated through Stitch AI's solution are only visible within the Message Box software and not in the regular WhatsApp application. Businesses that need a genuinely separate business identity, rather than a shared number, should consider whether a separate WhatsApp Business account and company-controlled number are the better fit, since personal conversations cannot be cleanly filtered without a verified mechanism in place.
Migrating to a platform does not automatically change established staff behaviour, and businesses should not assume that providing a web inbox alone will shift how a team works. What is WhatsApp coexistence and a phone-first deployment are worth exploring specifically for teams where staff are expected to continue using WhatsApp directly on their phones alongside the shared platform. This is a deployment decision to make deliberately rather than something that resolves itself once the number is migrated.
Existing WhatsApp Business numbers can be onboarded into the WhatsApp Business Platform ecosystem without changing the user experience for the people using them. In one documented case, a business with consultants in South Africa, Tel Aviv and London needed the South Africa and Tel Aviv-based consultants to use UK numbers for continuity and integration, while the London-based director continued using WhatsApp Business locally, with the goal of consolidating all communications into a central CRM for activity tracking. This shows that number and geography questions are handled on a case-by-case basis as part of onboarding, rather than being blocked outright by the platform.
Onboarding typically involves account deletion and reinstallation, verification via SMS, and subsequent platform setup. In practice, this has covered assisting a new employee in setting up a WhatsApp Business account linked to a new mobile number before that number is integrated with the Stitch AI platform, as well as guiding an existing business number through deletion of the existing account and the technical steps required to initiate transfer into the new system. Once verification is complete, the setup extends to enabling features like automated meeting transcription and CRM integration.
Once a number is onboarded, one-to-one chats sync automatically into the connected CRM, enabling centralised monitoring without manual intervention going forward. This syncing applies to conversations from the point of onboarding onward, which is why the earlier point about chat history loss during migration matters: automatic CRM syncing is a feature of the new system, not a way to recover what existed before the account was migrated.
Businesses should confirm with their platform provider, before deleting or de-registering the existing mobile app account, exactly what will and will not carry across, since chat history loss is a known consequence of the standard migration path. It's also worth clarifying what questions you should ask a WhatsApp Business platform provider before signing up, particularly where filtering personal conversations cleanly is a requirement rather than a nice-to-have. Raising these questions during onboarding, rather than after the account has already been deleted, is the only way to plan around the platform's actual technical limitations.
Migrating a WhatsApp number onto Stitch's platform is a well-defined technical process, but it comes with firm limitations that are worth planning around rather than discovering midway through: chat history does not transfer, a number can only live in one environment at a time, and personal-business number separation needs a deliberate setup decision. Businesses considering the move should map out their number strategy, CRM integration needs, and staff deployment approach before beginning the account deletion step, since that is the point of no return for existing chat history.
