Salesforce can tell you how many opportunities are in your pipeline, which accounts need attention, and how much revenue your team expects to close this quarter.

But what happens when the information isn’t accurate?

You might have a beautiful dashboard that shows a strong pipeline coverage, but then you realize there are a bunch of opportunities that haven’t been updated in months. Marketing might claim they have hundreds of qualified leads, but Sales will tell you most are not worth pursuing. Customer Success could be preparing for a renewal without knowing that the customer recently raised a serious service issue.

Salesforce isn’t necessarily malfunctioning in any of these situations. It’s reporting the information available to it.

The problem is that nobody has established whether that information reflects what’s actually happening in the business.

Poor Salesforce data quality rarely announces itself as a major problem. It usually appears through smaller frustrations: a sales representative contacting the wrong person, a manager questioning a forecast, or an executive requesting yet another spreadsheet because the CRM numbers don’t seem right.

Over time, these problems become expensive.

Salesforce has spoken about how outdated, incomplete, duplicate and inaccurate CRM records can hurt productivity and revenue performance in its article on dirty CRM data and sales operations.

The challenge for revenue leaders isn’t simply cleaning up records. It’s understanding how unreliable data affects the decisions their teams make every day.

Here are nine problems worth investigating.

1. Clashing Teams With Duplicate Accounts and Contacts

Duplicate records are among the simplest Salesforce data problems to identify, but also among the simplest to underestimate.

A sales representative creates an account for a new prospect without realizing the company already exists in Salesforce. Marketing imports a contact list containing people already associated with active opportunities. Customer Success maintains another record for the same customer because the original account wasn’t easy to find.

Eventually, several records represent the same relationship.

The immediate consequence is confusion. Employees don’t know which record contains the most recent information or who owns the account.

The commercial consequences can be worse.

Two representatives might approach the same prospect without knowing about each other’s conversations. Marketing could send a promotional offer to an existing customer under active contract negotiations. A sales manager might see two opportunities that actually represent the same deal.

That last situation can make pipeline reporting look healthier than it really is.

Salesforce provides duplicate management capabilities through matching rules and duplicate rules, but configuring them properly requires some thought.

Not every similar record is necessarily a duplicate. Two subsidiaries may share a parent company while requiring separate account records. A person might legitimately appear in different business relationships.

The objective isn’t to merge everything that looks similar. It’s to establish how your organization identifies accounts, contacts, and their relationships.

Once those rules are clear, Salesforce can do a much better job of helping teams maintain them.

2. Incomplete Lead Information Is Slowing Down Qualification

Imagine receiving a new lead with a name, an email address, and very little else.

You don’t know the person’s company size, industry, location, or what prompted the inquiry.

A sales representative now has to investigate before deciding whether the lead deserves attention.

That may be manageable when the team receives a handful of leads each day. It becomes a problem when marketing campaigns generate hundreds or thousands of records.

Incomplete lead data can affect routing, qualification, prioritization, and follow-up.

For example, a company might assign leads based on geography and business size. If those fields are missing, Salesforce may route the lead to a general queue or assign it to someone who isn’t the best person to handle the opportunity.

The lead might eventually reach the right representative, but valuable time has already passed.

There’s also a common temptation to solve this by making every field mandatory.

I wouldn’t recommend that.

Long forms discourage submissions, and excessive required fields can encourage users to enter placeholder information just to complete a record.

Instead, identify the information your team genuinely needs at each stage of the process.

A new website inquiry may only need enough information for initial routing. More detailed qualification data can be collected during the first conversation.

Salesforce should support that progression rather than expecting every record to be complete from the moment it’s created.

3. Opportunity Stages Don’t Reflect What’s Actually Happening

This is where Salesforce data quality becomes a forecasting problem.

An opportunity sits in Negotiation because the sales representative moved it there several weeks ago.

Since then, the customer has stopped responding. The budget may have changed, or the decision-maker may have left the organization.

But the opportunity still appears in the forecast.

Technically, the record isn’t incomplete. It has an amount, a stage, a close date, and an owner.

The information is simply no longer reliable.

The problem becomes more difficult when different representatives interpret opportunity stages differently.

One person moves a deal into Proposal after sending a pricing document. Another waits until the customer confirms they’re reviewing the proposal. A third uses the stage whenever a deal feels promising.

The same stage now represents three different levels of buyer commitment.

A dashboard can calculate the total value of those opportunities, but the number doesn’t mean much if the underlying definitions aren’t consistent.

Sales leadership and RevOps need to agree on what qualifies an opportunity to enter or leave each stage.

That agreement should be based on observable customer actions wherever possible, rather than the sales representative’s confidence alone.

For instance, a proposal stage might require a documented proposal sent to an identified buyer, while a later stage might require confirmation of the customer’s decision process.

The exact definitions will vary by organization.

What’s important is that everyone uses them consistently.

This is closely related to a point we’ve made in Your CRM Isn’t the Problem. Your Revenue Process Might Be. A CRM cannot enforce a process that the business itself hasn’t clearly defined.

4. Outdated Contact Information Is Wasting Sales and Marketing Effort

People change jobs, companies reorganize, and purchasing responsibilities shift.

Your Salesforce records don’t automatically keep up with those changes.

A contact who approved purchases last year might now work for another company. An account’s main point of contact may have moved into a different department. The email address your marketing team relies on might no longer be active.

These issues are easy to overlook because the records still look complete.

The fields contain information. It’s just the wrong information.

For sales teams, this creates wasted outreach and delays in reaching the right decision-makers.

For marketing, outdated contact information can distort campaign performance. An audience might appear large in Salesforce, but a significant portion of those contacts may no longer be reachable or relevant.

It can also affect customer relationships.

Imagine a customer receiving an important renewal message addressed to someone who left the company months ago. Even if the message eventually reaches the right person, it doesn’t suggest that the organization has a particularly good understanding of its customer.

Contact data needs regular maintenance. This is especially important for accounts with active opportunities, renewals, or strategic relationships.

That doesn’t mean purchasing an enrichment platform automatically solves the problem.

Data enrichment can help, but teams still need rules to determine which source is authoritative, when information should be updated, and who is responsible for resolving conflicting details.

5. Lost-account relationships are concealing revenue opportunities

A company might have multiple subsidiaries, regional offices or business units, each with their own contacts and purchasing processes.

Salesforce might not get the bigger commercial relationship if it sees every entity as completely separate.

Consider an enterprise customer with offices across multiple regions.

While one team sells to the North American business. Another works with the European subsidiary. Customer Success supports an additional division.

If those accounts aren’t properly linked, no one may know just how much business the organization already does with the customer.

That creates problems for account planning.

Sales representatives might pursue opportunities without knowing about existing contracts or relationships. The leadership may be undervaluing the total account. Customer Success may miss opportunities to align service and renewal conversations across business units.

It can also create unnecessary conflict when multiple teams believe they own the same customer relationship.

Salesforce account hierarchies and related data structures can help represent these relationships, but only when the business has decided how it wants to manage them.

The structure needs to reflect actual selling, servicing, and reporting requirements.

A global enterprise sales team may need a different account model from a company selling primarily to independent small businesses.

This is why data architecture should follow business requirements rather than simply adding fields and relationships whenever someone requests them.

Our article on Salesforce custom objects and fields best practices discusses the importance of designing Salesforce data structures with a clear purpose.

6. Inconsistent Field Values Are Making Your Reports Unreliable

One of the most frustrating Salesforce problems is discovering that a report is technically correct but practically useless.

Suppose leadership wants to know how much revenue comes from the healthcare industry.

You run the report and find accounts classified as Healthcare, Health Care, Medical, Hospitals, and Life Sciences.

Some of those categories may genuinely represent different market segments. Others might simply be different ways of describing the same thing.

Unless the organization has defined its classifications, it’s difficult to know.

The same issue appears in lead sources, loss reasons, customer segments, product categories, and countless custom fields.

Free-text fields are particularly vulnerable because people naturally describe things differently.

A representative might enter “Referral,” while another writes “Partner Referral” and a third uses the name of the partner.

When the business tries to analyze which channels generate revenue, those differences create unnecessary reporting work.

Standardized picklists can help, but they aren’t the entire solution.

The business still needs to agree on what each value means.

For example, if a prospect attends a webinar after originally discovering the company through paid search, which channel should receive credit for the lead?

That’s an attribution decision, not simply a Salesforce configuration decision.

Once the definitions are established, RevOps can determine how Salesforce should capture and report the information.

Without that agreement, the organization will continue spending time reconciling numbers that should have been consistent from the beginning.

7. Salesforce and Other Systems Are Telling Different Stories

Salesforce rarely operates alone.

Most organizations also use marketing automation platforms, customer support tools, billing systems, finance applications, and other technologies that maintain customer information.

The problem begins when those systems disagree.

There is no contract information in the billing system, but the opportunity in Salesforce is marked as Closed Won.

Marketing has a contact marked as an active prospect, but Customer Success knows that contact is already part of an existing customer account.

Finance reports a different customer revenue total from the one shown in Salesforce.

Sometimes these differences are justified. Booked revenue, recognized revenue, invoiced amounts, and pipeline value are not interchangeable.

But sometimes the disagreement is caused by bad integration design, inconsistent identifiers, delayed synchronization, or unclear data ownership.

If no one knows which system should control a field, employees often solve the problem by hand.

They export data, compare spreadsheets, make adjustments and then send reports to the leadership.

This can work for a while, but it’s hard to keep up as the business grows.

The first step is to determine which system owns each piece of important information.

Salesforce may be authoritative for opportunity stage and sales ownership, while the finance system controls invoice and payment information.

Those responsibilities need to be documented across the entire RevOps team.

For organizations dealing with fragmented customer information, Salesforce’s approach to unified data provides additional context on connecting information across systems.

However, technology alone won’t settle disagreements about business definitions.

Those decisions still belong to the organization.

8. Stale Close Dates and Opportunity Amounts Are Distorting Forecasts

A pipeline report can look convincing even when many of its opportunities have little chance of closing on schedule.

The problem is partly that opportunity close dates are not always updated when circumstances change.

The deal should have been closed in October and now it goes into November, but the representative does not change the date.

Another opportunity has been reduced in scope, yet the original amount remains in Salesforce.

Individually, these issues may not seem significant.

Across dozens or hundreds of opportunities, they can materially affect the forecast.

Sales leadership may make hiring, spending, or investment decisions based on revenue that is unlikely to arrive when expected.

Finance may have to adjust projections late in the quarter. Sales managers may spend hours reviewing opportunities that should have been updated weeks earlier.

The obvious response is to tell sales representatives to keep their records current.

That advice isn’t wrong, but it doesn’t address why the information became outdated.

Sometimes the process requires too much manual work. Sometimes managers don’t review opportunity hygiene consistently. In other cases, the business hasn’t established what should trigger a change in close date or amount.

RevOps should consider how forecasting fits in with the sales team’s regular cadence of operations.

If weekly pipeline meetings are about where the deal is at any point, Salesforce should reflect those discussions.

If a customer postpones a purchasing decision, the expected close date should change as part of managing the opportunity, not as an administrative exercise at the end of the month.

Reliable forecasting depends on current information and consistent management practices.

A more sophisticated dashboard won’t compensate for either one being missing.

9. Nobody Owns Data Quality After the Initial Salesforce Implementation

This may be the most expensive problem on the list because it allows the other eight to continue.

During a Salesforce implementation, teams usually spend considerable time discussing fields, processes, integrations, and reporting requirements.

There may even be a major data cleanup before the system goes live.

Then the project ends.

New employees join. Marketing launches new campaigns. Sales processes evolve. Integrations change. Additional custom fields appear.

And gradually, the data starts deteriorating again.

The organization may still have a Salesforce administrator, but that doesn’t necessarily mean someone owns the business quality of the information.

An administrator can configure validation rules and duplicate management. They cannot independently decide what counts as a qualified lead, which customer segment an account belongs to, or how Sales and Finance should define a committed deal.

Those are business decisions.

Data quality therefore needs shared ownership.

Sales leadership should be accountable for the information used to manage opportunities and forecasts. Marketing should help maintain the integrity of lead and campaign data. Customer Success should own relevant customer lifecycle information.

RevOps can coordinate the standards, monitor quality, and identify where processes need improvement.

But the responsibility cannot sit entirely with one technical person.

In our article on creating a single source of truth in Salesforce, we discuss why governance and accountability matter just as much as the technology itself.

A clean CRM isn’t something an organization achieves once.

It’s something the organization has to maintain.

How Much Revenue Is Poor Salesforce Data Quality Actually Costing You?

It’s difficult to assign one universal percentage to the cost of bad Salesforce data.

The impact depends on the business model, sales cycle, customer relationships, and how heavily the organization relies on CRM information.

But there are practical ways to estimate the cost within your own organization.

Start with the problems that have a visible connection to revenue.

Duplicate leads mean repeated outreach. Imagine how much sales time is wasted and if it impacts conversion because of the confusion.

If you’re seeing assignment delays due to incomplete lead records, check to see if those delays correspond with lower contact or qualification rates.

If opportunity data is often out of date, compare past forecasts to actuals and probe reasons for big variances.

You can also look at how much time employees spend correcting information, reconciling reports, or maintaining spreadsheets outside Salesforce.

For example, if 20 employees spend two hours a week correcting CRM information, that’s 40 hours every week.

The organization has about 2,000 hours of work, spread out over more than 50 working weeks, that may not lead directly to selling or serving customers.

That calculation doesn’t prove how much revenue has been lost. That does give a starting point to gage the operational cost.

The bigger commercial impact might come from missed opportunity, delayed decisions, bad customer experience or poor forecast.

Those outcomes are harder to measure, but they shouldn’t be ignored.

Improving Salesforce Data Quality Starts With the Business Process

When organizations discover data quality problems, the immediate response is often to launch a cleanup project.

That may be necessary, particularly when Salesforce contains large numbers of duplicate or outdated records.

But cleaning the existing data won’t solve the problem if the same issues continue entering the system.

Suppose a company spends several weeks merging duplicate accounts.

If employees still have no clear guidance on when to create a new account, the duplicates will return.

The same applies to incomplete leads, inconsistent opportunity stages, and unreliable reporting fields.

A more sustainable approach starts with understanding how information enters Salesforce, who maintains it, and what the business expects to do with it.

Not every field needs to be required. Not every process needs automation. And not every data quality issue justifies purchasing another technology platform.

Sometimes the best improvement is to agree on a definition, delete a field that is not needed or change a process that encourages employees to enter inaccurate information.

Salesforce administrators can support these improvements with validation rules, duplicate management, automation, and better data structures.

But RevOps and business leadership need to establish the expectations those tools are meant to enforce.

This is especially important for organizations investing in AI.

For Agentforce and other AI capabilities, you need enough good reliable information to understand the customer and to perform the intended task.

If you’re dealing with conflicting account information, stale opportunity data, or fuzzy ownership in Salesforce, adding AI doesn’t automatically solve that.

It can make them more visible, and potentially more consequential.

Salesforce makes a similar point in its discussion of data quality and its importance for AI.

Before asking what AI can do with your Salesforce data, it’s worth asking whether the data is reliable enough to support the process in the first place.

Final Thoughts: Better Salesforce Data Should Lead to Better Decisions

A Salesforce data quality problem isn’t always obvious.

Sometimes it looks like an inaccurate forecast. Sometimes it’s a missed follow-up, a delayed renewal, or a marketing campaign that reaches the wrong audience.

The common thread is that people are making decisions with information they cannot fully trust.

That affects more than reporting.

It changes the way sales teams spend their time, how managers measure performance, how Customer Success manages relationships and how leadership plans for growth.

The good news is that organizations don’t have to go in and rebuild Salesforce to do that.

They need to know where the information is no longer reliable, why this is the case and who is responsible for ensuring the information is correct.

Start with data that directly supports revenue decisions.

Standardize the meaning of opportunity stages across the sales team. Make sure customer relationships are accurately recorded and represented, both online and offline. Establish ownership for the fields and processes that matter most.

Then use Salesforce to reinforce those standards.

A reliable CRM won’t eliminate every challenge involved in running a revenue organization.

But it will give your teams a much better foundation for making decisions.

CTA: Is Your Salesforce Data Helping or Hurting Revenue Growth?

Duplicate records, unreliable forecasts, disconnected systems, and inconsistent processes can make Salesforce harder to trust as your business grows.

Revenue Ops LLC helps organizations evaluate their Salesforce environments, improve data governance, and identify the process and technology issues that affect revenue performance.