Load your products and price lists first, then accounts with an owner rep, then reps and territories. Run the first week with daily check-ins, stop the WhatsApp visit reports from week two, and use the CRM data in every team meeting. Keep WhatsApp for talking to clinics and move visits, orders and samples into the CRM.
Key takeaways
- Load products, then accounts, then reps, in that order
- Clean the account list before import, not after
- Keep WhatsApp for clinic conversations and move internal reporting
- Set a date when WhatsApp visit reports stop counting
- Reps log visits when the manager visibly uses the data
To move a field sales team from WhatsApp and Excel to a CRM, load your data in a fixed order (products and price lists, then accounts with an owner rep, then reps and territories), run one supported week, and then set a date after which visit reports sent on WhatsApp no longer count. Keep WhatsApp for what it is good at, which is talking to clinics. Move everything you need to report on into the CRM: visits, orders, samples, promises and follow-ups. Expect the data cleanup to take longer than the software setup. Reps start logging properly when they see the manager running meetings from the CRM numbers.
Why WhatsApp and Excel stop working
With five reps, a WhatsApp group and a shared Excel file feel fine. The manager knows every clinic and reads every message. Somewhere between 10 and 25 reps the same setup starts to cost you, and it does so quietly.
The visit reports arrive as messages at 7pm in different formats. Someone copies them into Excel, or nobody does. Orders get sent as photos of handwritten forms. When a rep leaves, their clinic history leaves in their phone. When the owner asks how many A accounts were visited last month, someone spends half a day counting messages and the answer is still a guess.
Your reps are probably doing their best with the tools they have. WhatsApp is a chat tool, and chat is a poor place to keep records you need to add up later.
What stays on WhatsApp and what moves
Being clear about this early saves a lot of resistance. Reps worry they will lose the channel their clinics actually reply on. They won't.
Keep on WhatsApp:
- Quick messages with clinics: "I'm 10 minutes away", stock questions, delivery times
- Sending a doctor a brochure or a photo they asked for
- Urgent internal calls ("the Al Barsha clinic needs 5 units today, who has stock?")
Move to the CRM:
- Every visit, with notes and the next step
- Orders and order status
- Samples given, to whom and how many
- Promises made to clinics (price sheets, demos, training dates)
- Daily and weekly reports, which the CRM should produce from the visits
- Account details: contacts, class, owner rep, buying pattern
One more point to get right: messages with clinics on reps' personal numbers stay on the rep's phone and leave with the rep. If that worries you, look at a shared WhatsApp Business number for customer conversations. Before you send promotions to doctors from it, check the consent rules with your legal adviser.
Load the data in this order
Order matters because each step depends on the one before it.
Products and price lists first. Codes, names, pack sizes, and the prices each customer type gets. If reps cannot pick a product correctly from day one, orders and samples will be wrong and they will lose trust in the system quickly.
Accounts second, and clean them before import. A typical distributor's account list has the same clinic three times under slightly different names, for example "Dr Rana Clinic", "Rana Medical Centre" and "RANA MC - JLT". Merge them. Give every account one owner rep, a class (A, B or C) and an area. Remove clinics that closed.
Reps and territories third. Create the users, link each rep to their accounts and set up the managers' view of their teams.
Visit history last, if at all. It is useful for the first few weeks of planning, but old notes copied from WhatsApp are often too messy to import. A practical middle ground is to import the last three to six months for A accounts and start clean for the rest.
A worked example: cleaning an account list
Say your combined Excel files hold 1,800 account rows. After removing exact duplicates you have 1,500. After merging name variations and branches you have 1,200. After removing closed clinics and accounts nobody has visited in two years, you are left with 1,050 live accounts. These are example numbers, but the shape is common: the real list is noticeably shorter than the file.
Then classify. Perhaps 150 are A, 400 are B and 500 are C. Now each of 15 reps has roughly 70 accounts, and for the first time you can see whether those 70 are a sensible workload or whether one rep has 25 A accounts and another has 3.
That view alone often justifies the switch, before a single visit is logged.
The first week, day by day
Day one: a 45-minute session per team, on phones, in the office. Each rep logs a test visit and a test order while you watch. Don't present slides. Have them do it.
Days two to four: reps log real visits. Every evening, the manager checks who logged what and messages anyone with zero entries the same evening, to ask what got in the way. It is usually something small: a missing account, a product not loaded, a login issue.
Day five: a 30-minute team review. Show the week's visits on screen, by rep. Thank the people who logged everything. Fix the top three complaints by the following Monday.
During this week, accept WhatsApp reports in parallel so nothing is lost. Tell the team clearly that this is temporary.
What to stop doing, and when
The switch fails most often because the old way never ends. If reps can still send a WhatsApp report and get credit for it, many will, because it is what they know.
- From week two, visit reports sent on WhatsApp no longer count. A visit that is not in the CRM did not happen, for reporting and reviews.
- Stop the shared Excel tracking file. Make it read-only so nobody adds to it by habit.
- Stop asking reps to send end-of-day summaries. The CRM should produce them.
- Stop collecting order forms as photos once order entry works in the CRM.
Announce the dates in advance and stick to them. Moving the date once teaches everyone that it will move again.
Getting reps to actually log visits
Reps usually avoid CRMs because logging feels like admin for someone else's benefit. A few things change that.
Make it faster than the old way. If logging a visit takes longer than typing a WhatsApp message, you will lose. Aim for under a minute: check in, pick the account, tap the products discussed, one line of notes, next step. Turn off every optional field you don't need.
Use the data in front of them. Run every one-to-one and team meeting from the CRM screen. When a rep sees their manager open the account history before a joint visit, logging stops feeling pointless.
Give something back. A rep who walks into a clinic and sees the last visit notes, open promises and last order on their phone saves time on every visit. That is the version of the CRM they will defend.
Don't punish the first month. Use the early data to help, not to criticise numbers. If the first thing a rep's honest data brings is a warning, everyone else learns to log less.
Set a reasonable late-entry rule. Visits should be logged the same day. Entries made more than a day or two late can go to the manager for approval, which keeps the record honest without blocking people who had a busy afternoon.
Mistakes to avoid
- Importing the messy account list as it is and planning to clean it "later"
- Switching everything on day one, including features nobody needs yet
- Letting WhatsApp reports count indefinitely "as a backup"
- Training with slides instead of having reps log on their own phones
- Leaving managers out of training, so they keep asking for Excel reports
- Choosing a CRM that does not work when reps lose signal in hospital basements
How to tell it worked
After 30 days, check a few things. Do most reps log visits on the same day? Can you answer "which A accounts haven't been visited this month?" in under a minute? Did any WhatsApp report arrive in the last two weeks? Are reps recording a next step on most visits? If the answers are mostly yes, the switch has stuck. If not, the cause is usually one of the mistakes above, and it can be fixed.
Once visits are in one place, planning gets easier too. Our pre-call planning template is a good next step for the team.
Try it free for 30 days
Amoura is a field sales CRM built for medical and aesthetic distributors, with offline visit logging on iPhone and iPad. You can try it free for 30 days with your own accounts and products, for up to 10 users. Send us your Excel files and we do the cleanup and setup.
How to switch a field team from WhatsApp and Excel to a CRM
- 1Load products and price lists
Import the product list with codes, pack sizes and the price lists each customer type gets.
- 2Clean and load accounts
Merge duplicates, assign one owner rep per account and set an account class.
- 3Add reps and territories
Create users, link each rep to their accounts and set up the manager view.
- 4Run a supported first week
Train in short sessions, check logged visits every evening and fix problems the next morning.
- 5Stop the old reports
From week two, visits that are not in the CRM do not count in reports or reviews.
FAQ
Can a CRM replace WhatsApp for a field sales team?+
It replaces WhatsApp as the place where visits, orders and reports are recorded. Most distributors keep WhatsApp for quick conversations with clinics and use the CRM as the record of what happened.
How long does it take to move from Excel to a CRM?+
For a team of 10 to 25 reps, plan on one to two weeks to prepare and load data and another two to four weeks before logging is a habit. The data cleanup usually takes longer than the software setup.
What data should I load into a new CRM first?+
Products and price lists first, then accounts with an owner rep and class, then users and territories. Visit history is useful but can follow once the basics work.
How do I get sales reps to actually use the CRM?+
Make logging a visit faster than writing a WhatsApp report, stop accepting reports anywhere else after a set date, and use the CRM numbers in every one-to-one and team meeting.