You signed a client. They already run their sales on WhatsApp, but the tool is a mess. Maybe they pay for Wati, maybe they bolted three apps together, maybe everything lives in one shared phone. Now you want to move them onto your own whitelabel WhatsApp CRM — the one that carries your brand, your pricing, and your monthly margin.
That move is called a migration. Done well, it takes a week and the client barely notices. Done badly, it loses chat history, breaks automations, and burns the trust you just earned. This guide is the full 2026 playbook. It walks through every step, the order to do them in, and the mistakes that cost agencies their first reseller client.
If you are still choosing a platform to migrate to, read our guide on the best whitelabel WhatsApp CRM software first, then come back here.
Why agencies migrate clients to a whitelabel WhatsApp CRM
Most agencies do not start with a whitelabel plan. They start by managing a client’s WhatsApp on whatever tool the client already pays for. That works for a month. Then the cracks show.
The client’s tool is branded for someone else. Every login screen, every invoice, every support email reminds the client that you are the middleman, not the owner. The day they discover the real price, they wonder why they pay you a markup.
A whitelabel WhatsApp CRM fixes that. You rebrand the whole product as your own — logo, colours, domain, login page. The client sees your brand, pays your price, and never meets the vendor underneath. You keep the difference every month. Our profit margin breakdown shows how that math works for a small reseller.
So the migration is not busywork. It is the step that turns a one-off service client into recurring software revenue. The numbers are real: a reseller charging ₹1,500 (about $18) per client per month across 30 clients clears ₹45,000 (about $540) in monthly recurring revenue, most of it margin. That only happens once the client sits inside your CRM, not someone else’s.
There is a softer reason too. A client who lives inside your branded CRM is far harder to lose. They learn your login, they save their work in your product, and switching away from you becomes a chore. A client on someone else’s tool can drop you the moment they find the vendor directly. Migration is how you turn a loose handshake into a sticky, long-term account.
Before you migrate: the 5-point readiness checklist
Do not touch the client’s live WhatsApp until you can tick all five of these. Rushing here is the single most common reason migrations break.
- You have admin access to the current setup. You need to see the contacts, chats, and any automations before you can move them.
- Your whitelabel CRM account is live. Set up your reseller account first, so you have somewhere to land the data. You manage all of this from the admin.lioncrm.com reseller panel.
- You know which WhatsApp number the client will use. Migrating a number has rules. Sort this out before, not during.
- You have written down the client’s must-keep items. Ask them directly: which chats, which saved replies, which broadcast lists cannot be lost?
- You picked a low-traffic window. A clinic is quiet on Sunday evening. A shop is dead at 7am. Find their slow hour and migrate then.
If any point is missing, fix it first. A migration that starts on a shaky base will wobble for weeks.
Step 1 — Audit your client’s current WhatsApp setup
Open the client’s current tool and write down exactly what is there. You cannot move what you have not measured. Keep a simple sheet with four columns: item, where it lives, can it be exported, and is it must-keep.
Look for five things. First, contacts — how many, and what tags or fields hang off them. Second, chat history — how far back it goes and whether the client actually needs old threads. Third, saved replies and templates — these are quick to recreate but easy to forget. Fourth, automations or chatbot flows — the welcome message, the away message, any keyword replies. Fifth, broadcast or campaign lists — the groups the client messages in bulk.
Most clients overestimate what they need to keep. Ask them to point at the last time they opened a chat older than 90 days. Usually they cannot. That single question shrinks the migration by half.
Step 2 — Map and export the data that matters
Now turn your audit into an export plan. Each item from Step 1 gets one of three labels: export it, recreate it, or drop it.
Contacts almost always get exported. Most WhatsApp tools let you download contacts as a CSV file. If the client uses plain WhatsApp Business on a phone, you can export contacts through the phone’s contact app instead. Get the file, open it, and clean it — remove duplicates, fix broken phone numbers, and make sure every number includes the country code.
Saved replies and templates usually get recreated. They are short, and retyping them inside your new CRM takes minutes. Trying to export them is rarely worth the effort.
Old chat history is the hard call. WhatsApp does not let you bulk-transfer years of conversations between platforms — that is a limit of the WhatsApp system, not your CRM. For most clients, you export the last 30 to 90 days as a backup and start fresh inside the new CRM. Be honest with the client about this before you start, never after.
Step 3 — Set up your whitelabel CRM and rebrand it
Before any client data lands, make the new home look like your product. This is the whitelabel part, and it is what justifies your price.
Inside your reseller panel, set four things. Your logo, so it shows on the login screen and inside the app. Your brand colours, so nothing feels borrowed. Your own domain or subdomain, so the client logs in at a web address that carries your name. And your support contact, so help requests reach you, not the vendor.
Then create the client’s workspace inside your account. Give it the client’s business name, set their plan, and add their team members with the right roles. A sales rep should not see billing. The owner should see everything.
Spend real time here. The rebrand is the difference between a client who thinks they bought your software and a client who feels they rent someone else’s. If you are unsure how to price the rebranded product, our guide on how to price whitelabel WhatsApp CRM clients lays out the common models.
Step 4 — Migrate WhatsApp numbers and the Business API
This is the step that scares people, so take it slowly. There are two paths, and the right one depends on what number the client uses.
Path A — the client keeps a personal or Business app number. If the client runs a normal WhatsApp Business app, you connect that number to your CRM through the official WhatsApp Business Platform API. The number stays the same for the client’s customers. Nothing on the customer side changes. The catch: a number can be active on the Business app or the API, not both at once. Plan for a short gap of a few minutes during the switch, and do it in your chosen quiet window.
Path B — the client wants a fresh number. Sometimes a clean start is better, especially if the old number is tangled with personal chats. You register a new number on the API, then help the client tell customers about it. This avoids any messy disconnection but needs a short heads-up campaign.
Either way, the official WhatsApp Business API is what powers a real CRM at scale. If the API world is new to you, our WhatsApp Business API reseller guide explains the moving parts in plain language. Get the green tick verification started early — it can take a few days, and you do not want the client waiting.
Step 5 — Import contacts, chats and automations
With the number connected and the brand in place, bring the data in. Work in this order, because each layer builds on the one before.
Start with contacts. Upload the cleaned CSV from Step 2 into your CRM. Match the columns carefully — name to name, phone to phone, tag to tag. Import ten test rows first and check them before you push the full list. A mismatched column that copies 2,000 phone numbers into the name field is a painful thing to undo.
Next, rebuild the saved replies and templates you marked as recreate. Type them in, group them, and assign them to the right team members. This is also the moment to improve them. Most clients have replies full of typos they never fixed.
Then set the automations. Recreate the welcome message, the away message, and any keyword flows. Keep the first version simple. You can add clever branching later, once the client is settled and the basics work.
Step 6 — Train the client and run a parallel week
A migration is not finished when the data lands. It is finished when the client’s team uses the new CRM without calling you in a panic. That takes training and a safety net.
Run one short training session, 30 to 45 minutes, screen shared. Show the three things they will do every day: open a chat and reply, find a contact, and send a broadcast. Do not show every feature. Show the daily three, and let the rest come later.
Then run a parallel week. For the first seven days, keep the old setup reachable but route all new chats through the new CRM. If something is missing, you can still glance at the old tool. After a week with no surprises, switch the old tool off for good. This single habit prevents the worst migration outcome — deleting the old system on day one and discovering a gap on day three.
One more tip: send the client a short written guide at the end of the week. Three or four screenshots showing the daily tasks, plus your support number, saves you a dozen small questions over the next month. It also reminds the client, every time they open it, whose product they now use.
A real example: migrating a 3-clinic dental group
Numbers help, but a story makes the steps stick. Here is how a typical migration runs, using a small dental group as the example. The group has three clinics, one shared WhatsApp number, and a receptionist at each branch who replies to patients all day.
Before the migration, all three clinics shared one phone passed between the front desks. Appointment requests got lost. Two receptionists sometimes replied to the same patient with different times. The owner paid for a basic tool that showed someone else’s brand on every screen, and he had no idea who answered what.
The migration followed the playbook. Day one was the audit: about 4,000 patient contacts, a folder of saved replies for appointment confirmations, and one welcome message. Most chats older than three months were never reopened, so the team agreed to keep only a 90-day backup. Day two and three covered the rebrand inside the admin.lioncrm.com panel — the agency set its own logo and a login domain, then connected the shared number to the WhatsApp Business API and started green tick verification.
Day four was the import. The 4,000 contacts went in after a ten-row test, tagged by clinic. The appointment replies were rebuilt and improved, and the welcome message now routes patients to the right branch. Day five was a 40-minute training call with all three receptionists. Days six and seven were the parallel week, with the old tool kept on standby. Nothing broke, so the old tool was switched off.
The result: one shared inbox, three receptionists who can each see who replied, and a product that carries the agency’s brand. The agency charges the clinic a monthly fee and keeps the margin every single month. That is the whole point of the migration.
Common migration mistakes (and how to avoid them)
Five mistakes cause most failed migrations. Each one is easy to dodge if you know it is coming.
The first is promising full chat history. WhatsApp does not allow bulk chat transfer between platforms, so never promise it. Set the expectation early and the client is fine. Promise it and break it, and you start the relationship in a hole.
The second is migrating during business hours. A clinic mid-migration during Monday rush is a disaster waiting to happen. Always use the client’s quiet window.
The third is skipping the test import. Ten test rows take two minutes and catch the column-mismatch bug that ruins a full import. Never skip them.
The fourth is over-engineering automations on day one. A complex chatbot that breaks on launch makes you look worse than no chatbot at all. Ship the simple version, then improve it.
The fifth is forgetting the rebrand. If the client logs in and sees the vendor’s name, your whitelabel pitch falls apart. Check every screen — login, app, emails, invoices — before you hand over the keys.
Migration timeline and cost: what to tell clients
Clients ask two questions: how long, and how much. Give them clear answers.
On timeline, a typical single-client migration runs five to seven working days. Day one is the audit and export. Days two and three cover the rebrand, the workspace, and the API connection, with green tick verification running in the background. Days four and five handle the import and training. Days six and seven are the parallel week. If the client needs a fresh number, add two or three days for the heads-up campaign.
On cost, separate two things. There is your one-time migration fee, which covers your setup labour. And there is the recurring whitelabel subscription the client pays you every month. You buy the underlying platform at reseller rates and charge the client your own price on top. You can take client payments through your own PayPal or any gateway you already use, and pay your reseller fee separately — your billing and the client’s billing stay fully separate.
A clean number to share with clients: most agencies charge a one-time migration fee of ₹3,000 to ₹8,000 (about $36 to $96) plus a monthly plan, and recover the setup fee inside the first two months of recurring revenue. Once you have done three migrations, the fourth takes half the time, and the margin is almost pure profit. Want to talk through your first migration? Message Kuldeep on WhatsApp at +91 74260 38448 and see the reseller pricing to plan your numbers.
Related guides
Frequently asked questions
Can I transfer old WhatsApp chat history to a new whitelabel CRM?
Not in bulk. WhatsApp does not allow full conversation history to be transferred between platforms — this is a limit of the WhatsApp system, not the CRM. The standard approach is to export the last 30 to 90 days as a backup and start fresh inside the new CRM. Contacts, saved replies, and automations move across fine. Set this expectation with the client before the migration begins.
How long does it take to migrate a client to a whitelabel WhatsApp CRM?
A typical single-client migration takes five to seven working days. That covers the audit and export, the rebrand and workspace setup, the WhatsApp Business API connection, the data import, a short training session, and a one-week parallel run before the old tool is switched off. If the client wants a brand new WhatsApp number, add two or three days for the customer heads-up campaign.
Will the client’s WhatsApp number change during migration?
It does not have to. If the client keeps their existing number, you connect that same number to the WhatsApp Business API, so their customers see no change. There is a short switchover gap of a few minutes, which is why you migrate during a quiet window. A client can also choose a fresh number for a clean start, but that needs a short campaign to tell customers about it.
Do I need the WhatsApp Business API to migrate a client?
For a real CRM that scales, yes. The official WhatsApp Business API is what lets a whitelabel CRM handle many chats, multiple agents, and automations on one number. A plain WhatsApp Business app on a phone cannot support a proper multi-agent CRM. Connecting the API is part of the standard migration, and green tick verification should be started early because it can take a few days.
How much should I charge a client for a WhatsApp CRM migration?
Most agencies charge a one-time migration fee of ₹3,000 to ₹8,000 (about $36 to $96) to cover the setup labour, plus a recurring monthly subscription for the whitelabel CRM itself. You buy the platform at reseller rates and set your own client price on top. The one-time fee usually pays for itself inside the first two months of recurring revenue.
What happens to the client’s saved replies and automations?
You recreate them inside the new CRM rather than exporting them. Saved replies and templates are short, so retyping them takes minutes and is a good chance to fix old typos. Automations like the welcome message, away message, and keyword replies are rebuilt fresh. Keep the first version simple and add advanced flows once the client is comfortable with the basics.
Can I rebrand the CRM completely so the client only sees my brand?
Yes — that is the whole point of a whitelabel WhatsApp CRM. You set your own logo, brand colours, login domain, and support contact from the reseller panel before any client data lands. The client logs in to a product that carries your name end to end and never meets the vendor underneath. Checking every screen for the rebrand is a required step before you hand over access.