CRM adoption: how to get a sales team to keep the CRM up to date

To increase CRM adoption in a sales team, make the CRM give something back to the people who fill it in. Cut the fields to the ones someone actually uses, make the pipeline stages match how your team sells, ask for information only at the stage where it matters, and run every pipeline meeting and forecast from the CRM itself. When managers stop asking for updates by email and spreadsheet, sellers stop keeping a second set of records. Then measure adoption by the quality of the data, not by how often people log in.

This guide is for sales directors, heads of sales and revenue operations leads whose CRM has drifted out of date, and who want sellers to keep it current without chasing them every Friday.

Why sellers avoid the CRM

Ask a sales team why the CRM is out of date and the answers are usually practical, not lazy.

• Too many fields. A deal form with thirty fields, most of them never reported on.
• Stages that do not match reality. Sellers cannot tell where a deal belongs, so they leave it where it is.
• No return for the seller. The data goes up to management; nothing comes back that helps them sell.
• A second system. The manager runs the forecast from a spreadsheet, so the spreadsheet is what gets updated.
• Poor set-up. Duplicates, slow screens, missing email or calendar integration, no mobile access.

Each of these has a fix. Mandates and reminders treat the symptom.

Fewer fields, clearer stages

Run a field audit

1. Export the list of fields on deals, contacts and companies.
2. For each field, name who uses it and in which report or decision. If nobody can, it goes.
3. Check how often it is filled in. A field that is empty on most records is either unnecessary or in the wrong place.
4. Keep the required set short. For a deal: amount, close date, stage, next step with a date, main contact, and whatever your qualification framework needs.

A field audit also serves data protection. Under UK GDPR’s data minimisation principle, personal data should be adequate, relevant and limited to what is necessary for the purpose. The ICO’s checklist includes periodically reviewing the data you hold and deleting anything you do not need.

Match stages to how you sell

Each stage should have exit criteria based on what the buyer has done, not what the seller has sent. Five to seven stages are usually enough. Our guide to improving sales forecast accuracy includes an exit criteria table you can adapt.

Ask for data when it matters

Instead of a long form at deal creation, ask for each piece of information at the stage where it becomes relevant. HubSpot, for example, has conditional stage properties: you choose which properties appear when a user moves a record into a stage, and if you mark a property as required, users cannot create or update the record until they set a value. Use this sparingly. Every required field is a small cost to the seller, so make sure each one earns its place.

Dashboards for sellers and for managers

Adoption improves when the CRM is the quickest way for a seller to answer their own questions.

Keep each dashboard to a handful of reports. A dashboard nobody opens is just another reason to distrust the system.

Running the pipeline meeting from the CRM

This is the change that matters most. If the weekly pipeline review runs from the CRM, on screen, deal by deal, the CRM becomes the only version that counts.

1. Stop accepting updates by email, chat or spreadsheet. If it is not in the CRM, it is not in the forecast.
2. Open the manager dashboard first: deals with no next step, past close dates, no recent activity.
3. Review committed deals on the deal record, not on a slide.
4. Update the record in the meeting when something changes, so sellers see the CRM as the place decisions are recorded.
5. Do the same in one-to-ones and forecast calls.

Customer success teams benefit from the same discipline. See how to run a QBR customers value for recording QBR outcomes in the CRM.

Measuring adoption: logins are not enough

Logins show that someone opened the system, not that the data is any good. Measure the things the business relies on.

A CRM data quality checklist

• Share of open deals with a next step dated in the future
• Share of open deals with a close date in the past (aim for none)
• Deals above an agreed value with at least two contacts
• Deals that have sat in one stage much longer than your usual cycle
• Deals that skipped stages on the way to won or lost
• Meetings and calls logged against deals, not just against contacts
• Duplicate companies and contacts created in the period

Some of this comes from data the CRM records automatically. HubSpot’s funnel reports, for instance, are built on “Date entered [stage]” timestamps that it updates itself, so stage history does not depend on sellers remembering to fill in a date. Review the checklist monthly, by team, and share it. People tend to fix their own numbers once they can see them.

Choosing and setting up tools

A new CRM rarely fixes an adoption problem on its own. If the process, fields and meetings stay the same, the same gaps reappear in the new system. Before changing tools:

• Write down the sales process and the stages first.
• List the reports leadership actually uses.
• Check email and calendar integration, and how the mobile app works for field sellers.
• Plan the data migration as a project of its own: what moves, what is cleaned, what is left behind.
• Train by role, on the team’s own data, in short sessions.

Data protection basics for CRM data

B2B contact data is still personal data. The ICO’s guidance on business-to-business marketing says UK GDPR applies if you are processing personal data, for example the name of the individual who represents a business. Points to cover:

• Lawful basis. If you rely on legitimate interests, the ICO sets out a three-part test: a purpose test, a necessity test and a balancing test. You must be able to satisfy all three before you start using the information.
• Telling people. If you collect someone’s details in their business capacity and intend to send them direct marketing, the ICO says you must tell them and have a lawful basis.
• Electronic marketing rules. Under PECR, limited companies and LLPs are corporate subscribers, and the rule on marketing by electronic mail does not apply to them. Sole traders and other types of partnerships are treated the same as individuals.
• Keep what you need. Review records regularly and delete what you no longer need.

This is a summary, not legal advice. Check the ICO guidance for your own situation.

How we can help

Our CRM adoption and dashboards work sets up deal stages and exit criteria, manager dashboards and a weekly forecast routine your team will run from the CRM. The CRM, Pipeline and Forecast Set-up package takes four to six weeks, from £6,500 + VAT; software configuration and data moves are quoted separately (see pricing). If you want senior help to keep the routine going afterwards, our Enablement Partner provides two senior days a month, with coaching and deal reviews, at £2,400 + VAT a month on a three-month minimum term. For the deal process behind the stages, see sales process and pre-sales, or book a 30-minute call.

Sources

All checked on 26 October 2026.

• Set up and manage object pipelines (HubSpot Knowledge Base): conditional stage properties and required properties.
• Create custom funnel reports (HubSpot Knowledge Base): automatic stage timestamps.
• Principle (c): Data minimisation (Information Commissioner’s Office).
• What is the ‘legitimate interests’ basis? (Information Commissioner’s Office): the three-part test.
• Business-to-business marketing (Information Commissioner’s Office): UK GDPR and PECR for B2B contacts.

Frequently asked questions

How do you increase CRM adoption in a sales team?

Remove fields nobody uses, match stages to how you sell, ask for data at the stage where it matters, give sellers dashboards that help them, and run every pipeline meeting and forecast from the CRM.

Why do salespeople not update the CRM?

Usually because it takes time and gives nothing back: too many fields, stages that do not fit, and managers who still ask for updates outside the CRM.

How do you measure CRM adoption?

By data quality rather than logins: open deals with a future next step, no past close dates, enough contacts on larger deals, and deals not stuck in one stage.

Should we make CRM fields mandatory?

For a few fields that drive decisions, yes, ideally at the stage where they matter. Making many fields mandatory tends to produce placeholder values rather than better data.