Moving your sales conversations off personal WhatsApp without losing them
Almost every business I move onto the WhatsApp Business Platform starts from the same place: one phone, three years of orders, and no idea what happens to the history if the number changes hands. Here is the order I run the move in, and the one step I refuse to take.
Almost every business I move onto the WhatsApp Business Platform starts from the same place: one phone, three years of orders, and no idea what happens to the history if the number changes hands. Here is the order I run the move in, and the one step I refuse to take. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
Almost every business I move onto the WhatsApp Business Platform starts from the same place. Not a dashboard. One phone, in one person's hand, holding three years of orders.
The owner calls it "our WhatsApp". What they mean is that a salesperson's personal number is doing the job of a CRM. It works fine until the day it does not: the phone is on leave, the person resigns, or the handset ends up in a bucket of water and the entire order history goes with it.
Moving to the platform fixes that. The move itself is where people get hurt, because the standard advice online starts with "delete the account", and that is the one step I will not take.
The problem is not the app. It is where the history lives
The personal app is a good product. I use it. It is wrong for business only because of three properties.
- The history is on a device. There is no team-visible record. If the phone is gone, so is the context.
- The identity is a person. Customers save "Ravi - sales". When Ravi leaves, the relationship is a saved contact, not a company asset.
- Nobody can help. Two people cannot answer one number properly. Whoever holds the phone is the bottleneck, including at 11pm.
None of those are fixed by a better app. They are fixed by the number moving into a business account that a team can access. That is what the platform does.
Do not start by deleting the account
Search this topic and you will find step one listed as "delete your WhatsApp account, then register the number on the Cloud API". Technically that path exists. Meta's own phone number documentation says a number in use with the Messenger app or the Business app cannot be registered until it is freed.
I still do not start there, for three reasons.
- Deleting is irreversible. The messages go, and the backup you made does not load into the platform. You lose the very thing you were trying to preserve.
- It may close a door you wanted. For an eligible Business app number, Meta runs a separate onboarding that keeps the app working alongside the platform. That route needs the app account alive, so a deleted account cannot take it.
- It is rarely necessary. In most of the businesses I move, the phone keeps doing what it does while a second number takes over the structured work. Nobody has to lose anything.
The three routes, and how to pick one
There are only three arrangements worth considering. The deciding question is what you want to happen to the old conversations.
| Route | What happens to history | Use it when |
|---|---|---|
| New business number on the platform | Untouched. Old threads stay on the phone as reference | The number is genuinely shared with family, staff or suppliers |
| Personal number to the Business app, then onto the platform | The account moves with chats and media if the backup restores | You want customers to keep the number they already know |
| Number registered on the platform only | App history does not follow | The phone is out of the loop entirely |
Route two is the one most owners want and the one that needs the most care. WhatsApp documents the first half of it directly: moving a Messenger account to the Business app carries the account, chat history and media across when it finds a backup on that number, provided you restore with the same number and the same Google or iCloud account. Two caveats worth knowing before you start. WhatsApp contacts created inside Messenger are lost in that move, so save them to the phone's address book first. And one number cannot sit in Messenger and the Business app at the same time.
The second half, Business app to platform, is the part I would not improvise. Meta's help centre describes it as syncing your Business app messages and contacts, up to six months of individual chat history, and it states plainly that groups cannot be synced. It also tells you to open the Business app at least once every 20 days to keep syncing. Eligibility for that route is decided during onboarding, not by reading a blog post, so treat any article that promises it as a guess. I laid out the provider-side version of the same move in moving a number between providers.
Coexistence is not "both apps work normally"
This is the misunderstanding that causes the most anger in week two. When a Business app number is connected to the platform, you get one number in two places, not two full products.
What you actually get:
- The same business profile and the same contacts on both sides.
- Individual conversations mirrored, up to six months of history at onboarding.
- Messages you send from the app mirrored into the inbox.
What you do not get:
- Groups. They stay in the app and do not sync.
- A shortcut on the rules. A message you send from the app is not a platform message. It does not open or extend the 24-hour customer service window, and it is not billed like one. Rules, templates and consent still apply to everything the platform sends.
- A phone-free business. The app has to stay installed and opened regularly, or the sync stops.
That last point matters more than it sounds. A business that connects the app, moves everyone to the inbox, and then stops touching the phone is one that quietly loses half its mirrored history.
The step nobody plans for: consent
The most common plan I hear is "we already have 4,000 chats, so we will send our new catalogue to all of them". That plan is a mistake, and it is the reason numbers get restricted.
A customer messaging you last March is not a subscriber. Platform messaging rules are built around a 24-hour service window that a customer's message opens, and around templates with an opt-in record behind them. Your existing chats give you something worth more than a list: a live conversation you can answer inside the window, and a natural moment to ask permission. I wrote about the mechanics in opt-in and consent for WhatsApp messaging because getting this wrong is the fastest way to lose a good number.
The practical version: answer the thread, do the work, and ask at the end. One line is enough. "Should I send you updates like this on WhatsApp?" A yes recorded against the customer record is a usable opt-in. A phone book export is not.
What the first week looks like
The move is small enough to run in a week if you keep the scope honest.
- Day one: inventory. How many active conversations, which are repeat customers, which are one-offs, and which numbers belong to staff rather than the company. This is the day that decides everything else.
- Day two: display name and business verification. Do this early because it gates the templates.
- Day three: submit the three or four templates you actually need. Approval is out of your hands, so it starts now.
- Days four and five: wire the inbox and the webhook into whatever holds your orders. Test with your own number against a real customer record, not a test record.
- Week two: pilot five customers who message weekly. Watch reply time and how long it takes an order to reach a record, not message counts.
Where BNex fits
I built BNex because the platform is a solid foundation and a hostile first week. The API gives you messaging, templates and webhooks. It does not give you a shared inbox your team can work from, a mapping from a phone number to a customer record, or anything that knows what an order is.
Onboarding still runs through Meta's flow, and if the number already lives in the Business app, eligibility decides which route is open to you. What BNex adds is the layer above: a shared inbox so conversations are not trapped on one phone, template handling so approvals stop being guesswork, and webhooks so a confirmed order reaches your system without anyone retyping it. If you want the difference between the app and the platform spelled out first, the guide on Business API versus Business App covers it.
If you are sitting on a phone full of orders and wondering which of the three routes fits, message me on WhatsApp with how many active conversations you have and who holds the phone today. I will tell you honestly whether you need the platform yet, or whether a second number and a shared inbox is the whole job.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.
Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.