Sales Transformation

Low CRM adoption: how to recover it without replacing the CRM

8 mins read

A fan of smoked glass cards on a brushed silver spindle, with one card lifted and glowing red, on a deep purple background.

KEY TAKEAWAYS

  • Low CRM adoption on a live platform can come from the process, the admin load or how managers run the business, as well as the software. Find which before you spend on training or a new system.

  • Retraining helps when people don't know how to use the CRM. It is unlikely to help when the CRM asks for work that gives nothing back.

  • The pipeline review is a practical first lever to test. When managers run it from the CRM and inspect the evidence, the data starts to matter.

  • Measure outcomes as well as usage. Logins show activity; trusted forecast data and fewer side spreadsheets show recovery.

  • Replace the CRM only when evidence shows it can't support the process you've agreed, after the process and management fixes have had a fair test.

Before you blame the software for low CRM adoption on a platform that is already live, check the process and the way managers run the business. People avoid a CRM when it asks for work that gives them nothing back, when it doesn't match how deals really move, or when their managers run the business from somewhere else. Find which of these applies before you retrain the team or start talking to new vendors.

This guide is for a sales director or CRO whose CRM has been live for a year or more, whose licences are paid, and whose forecast still lives in a spreadsheet. It covers how to diagnose the cause, how to choose between retraining, simplifying, changing governance or replacing, and how to measure recovery.

Why CRM adoption falls after go-live

Adoption can fall for several reasons, and they need different fixes.

  • The CRM takes more than it gives. Sellers enter data that only feeds someone else's report. If the record doesn't help them run their own pipeline, it gets updated late or not at all.

  • The stages don't match how deals move. When the stages in the system bear no relation to what a buyer has actually agreed, sellers fill in fields to satisfy the system rather than to describe the deal.

  • Managers run the business elsewhere. If the weekly pipeline call works from a spreadsheet or from memory, the team learns that the CRM is optional.

  • Nobody trusts the data. Once a forecast built from the CRM has been wrong a few times, leaders stop using it. People notice that and stop updating it, and the data gets worse.

  • Something is genuinely broken. Duplicate records, a slow mobile app or a missing integration with email or quoting can make the system hard to use. These defects are real and need fixing; they just aren't always the whole story.

  • People worry about why it's being watched. Some teams see the CRM as surveillance. If nobody explains what the data is for, that worry is reasonable.

Merlin5's own view, on its commercial discipline work, is that the challenge is rarely the technology. It is embedding the disciplines, behaviours and management routines that help people use those tools consistently.

Symptoms, possible causes and what to check

What you see

Where the cause may sit

What to check

Records updated the day before the forecast call

The CRM is a reporting chore, not a working tool

Sellers keep their own lists elsewhere

Stages move with no change in the deal

Stages have no exit criteria

Two managers define the same stage differently

A separate forecast spreadsheet

Leaders don't trust CRM data

The spreadsheet and the CRM disagree on the same deals

Low use in one team only

Local management habits

That team's manager reviews deals outside the CRM

Complaints about speed or duplicates

A configuration or integration defect

The same complaint from several teams, reproducible on screen

Fields left blank

Too many fields, or fields nobody uses

Few of the mandatory fields appear in any report or review

Retrain, simplify, change governance or replace?

These are four different investments. Choose by the cause, not by what is easiest to buy.

Option

Choose it when

Less likely to help when

Retrain

People don't know how to do a task the process needs

The task itself gives them nothing back

Simplify

Fields, stages and screens ask for more than anyone uses

The problem is how deals are reviewed

Change governance

Managers don't inspect from the CRM and missing data has no consequence

The process underneath is unclear

Replace

The platform can't support the agreed process, even after configuration

You haven't agreed the process yet

Expect a recovery to need a mix of the first three. Microsoft's implementation guidance for Dynamics 365 treats training as part of implementation planning rather than a one-off event at go-live. That fits what a recovery needs: training aimed at the redesigned process, after the process and the review rhythm are fixed.

A recovery plan on the platform you have

Each step has an owner. The sales leader owns the decisions; sales operations or the CRM team owns the configuration; first-line managers own the habits.

  1. Agree what the CRM must answer. List the three or four questions leadership needs the system to answer: what will close this quarter, where deals stall, which segments win. If the CRM was never built around those questions, our guide to CRM transformation sets out the order of work.

  2. Cut the fields to the evidence that matters. Keep the fields that support a decision or a stage. Write stage criteria a manager can check, as in our guide to exit criteria.

  3. Run the pipeline review from the CRM. This is a practical first lever to test. When first-line managers open the CRM in the review and ask for the evidence behind each stage, the record becomes the place where the deal is discussed. A deal without its evidence stays out of the forecast.

  4. Fix the defects that are real. Log the complaints, reproduce them and fix the ones that affect many users: duplicates, slow screens, missing integrations. Show the team what changed.

  5. Give the seller something back. A view of their own pipeline, renewals due and next steps, without building reports by hand, is a reason to keep the record current.

  6. Name an owner after go-live. Microsoft's guidance on change management transition and handover assigns responsibility for adoption once the project team steps back. Without that owner, recovery fades as soon as attention moves on.

If fixes are queued behind a CRM release, our guide to keeping sales process and CRM aligned covers how to manage the gap without a second system.

How to measure CRM adoption: usage against outcomes

Usage measures tell you whether people open the system. Outcome measures tell you whether the data can now be trusted to run the business. Track both, and judge recovery on the second.

Usage measures:

  • active users by team, each week;

  • records updated within an agreed time after a customer meeting;

  • share of opportunities with a next step and a date.

Outcome measures:

  • share of forecast deals that meet their stage criteria;

  • pipeline reviews run from the CRM, not from a spreadsheet;

  • number of side spreadsheets still in use for forecasting;

  • difference between the CRM forecast and the final call;

  • CRM forecast against actual closed revenue, quarter by quarter.

Logins can rise while the data stays poor. If the forecast spreadsheet is still the one leaders trust, adoption hasn't recovered.

When replacing the CRM is the right call

Sometimes the platform is the problem. Merlin5's sales process and CRM transformation work starts by establishing what the current platform can do once it is asked to enforce a coherent process. Its FAQ on changing CRM answers "Usually not", and says Merlin5 will say so when a change is warranted.

Replacement deserves a hearing when:

  • the agreed process has been configured and tested, and the platform still can't support it;

  • integrations the business depends on can't be built or maintained at a reasonable cost;

  • the platform is being retired, or no longer fits the way the business is now organised;

  • the cost of keeping it exceeds the full cost of moving, counted honestly.

That last test needs a proper business case. Our guide to the CRM business case covers what a CFO will ask for, including internal time, training and change costs. If you do decide to move, our guide to choosing a CRM implementation partner covers what to settle before you compare proposals.

A new platform with the same process and the same review habits can inherit the same adoption problem.

How Merlin5 helps

Merlin5's partners have carried revenue targets and run sales teams themselves, with 30+ years of experience each. The work on adoption sits in two places. Commercial discipline covers the people side: CRM adoption, pipeline governance, forecasting disciplines and data quality improvement, reinforced through leadership coaching and management routines. Sales process and CRM transformation covers the design underneath: stage architecture, evidence requirements and configuration that removes administration rather than adding it.

Merlin5 is platform agnostic and has no licence to sell, so the recommendation follows the evidence.

If the immediate pain is the forecast rather than adoption itself, our guide to sales forecasting software covers what to fix in the inputs first.

Where to start

  1. Pick one team and sit in its pipeline review. Note where the conversation leaves the CRM.

  2. List every mandatory field and mark the ones used in a report or a decision. Propose cutting the rest.

  3. Ask three sellers what the CRM gives them back. If the answer is nothing, start there.

Frequently asked questions

Why don't salespeople use the CRM?

Check whether it takes more time than it saves them, whether the stages reflect real deals, and whether their manager uses it to run the business. Technical defects can play a part too, alongside those.

Will more training fix low CRM adoption?

Only if the cause is that people don't know how to do something the process needs. If the CRM asks for work that gives nothing back, more training teaches people to do that work and still avoid it.

How long does it take to recover CRM adoption?

It depends on the cause and the size of the team. Changing how pipeline reviews run can show results within weeks; fixing stage design and configuration takes longer, because definitions have to be agreed across teams first.

Should we make CRM updates part of performance reviews?

It can be done, but it risks rewarding complete records rather than accurate ones. A consequence inside the sales process is worth trying first: a deal without its evidence doesn't go in the forecast.

Sources

  1. Microsoft, Dynamics 365 implementation guide, "Training strategy". https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/training-strategy

  2. Microsoft, Dynamics 365 implementation guide, "Change management: transition and handover". https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/change-management-transition-handover

NEXT STEP

Make the CRM part of how your team sells

Merlin5 combines leadership coaching, practical enablement and day-to-day reinforcement so the platform you already have becomes part of how people work.

Explore Sales Enablement

Headshot of Chris Thomas

WRITTEN BY

Chris Thomas

© 2026 Merlin5

© 2026 Merlin5