Skip to main content

Empty fields and duplicate records are quietly breaking your reports. Find them with one audit.

A Salesforce data quality audit grades every object A to F for complete, accurate and unique records. It lists duplicates and empty critical fields, such as Lead.Rating.

Last updated
By the Clientell AI teamHow we write

Clientell AI, the AI agent for Salesforce admins, scans your org, drafts each fix and asks before it changes anything in production.

Example findings

What does bad CRM data look like?

Four patterns this audit is built to find. The examples are not real data.

Critical
Fill rate

Field completeness

When too few records have a value, reports and agents stop working well. The audit shows the fill rate for every field on every object.

Critical
Per field

Account.Industry blank rate

Accounts with no Industry value make territory rules and routing flows fail silently. The audit shows the blank rate for each key field.

Critical
Per field

Lead.Rating empty rate

Leads with no Rating leave routing agents to guess the value or refuse to act. The audit shows how many are empty.

Critical
Duplicate pairs

Duplicate Contact density

Duplicate Contact pairs are a routing risk and a deliverability risk. The audit lists the pairs it finds with fuzzy matching.

Field Completeness Heatmap

How complete is every field on every object? Graded A through F.

Click an object to see its completeness heatmap and top field-level gaps. The data below is a sample, not a real org.

Sample org completenessLow
Objects scannedAccount, Lead, Contact, Opportunity, Case
Fix pathValidation rule and dedupe
Sample figures
Coverage Areas

What does a Salesforce data quality audit cover?

Six areas. Each gap is tied to its effect on reports, automation or agents.

A to F grades per object

Every standard and custom object gets a grade: Account, Lead, Opportunity, Contact, Case and your custom objects. The grade comes from average field completeness, duplicate density and required-field gaps.

Field-level completeness heatmap

A visual map of every field on every object, with color-coded fill rates. Spot the cluster of empty fields in seconds. Drill into any cell for the field name, the fill rate and the proposed fix.

Duplicate density detection

The audit finds duplicate Accounts and Contacts with fuzzy matching on email, phone, name and address. Each pair comes with a merge recommendation.

Required-field gap audit

It finds fields marked required on the page layout but not enforced by a Validation Rule, because the API can bypass a layout. It also finds fields that should be required but are not.

Critical-field empty rate

The audit checks the fields that agents and reports depend on: Lead.Rating, Account.Industry, Opportunity.NextStep and Account.AnnualRevenue. Each one is tied to the report or agent that breaks when it is empty.

Validation rule and dedupe fix plan

For each high-impact gap, you get a proposed Validation Rule with its formula. For each duplicate pair, you get a merge recommendation and a winning record. Fixes are tested in a sandbox before you apply them.

How does the audit grade a field?

How the audit grades field completeness and what each grade means.
Fill rateGradeOperational impactAction
Nearly all filledAReports are accurate and automation behaves the same each time.Keep it that way with Validation Rules.
Most filledBReports are usable. Automation hits a few edge cases.Tighten validation. Backfill gaps each quarter.
About half filledCReports show gaps. Routing fails on edge cases.Backfill soon. Add Validation Rules.
Few filledDReports are unreliable. Automation can give wrong outcomes.Stop building new automation on it. Clean up first.
Almost none filledFThe field is effectively dead. Anything that depends on it is broken.Fill it through enrichment, or remove it from what depends on it.
Warning Signs

What does bad data cost you?

If any of these sound familiar, the data is the cause.

Your forecast report does not match the executive dashboard

Both use the same data source but aggregate it differently. The cause is often empty fields skewing the rollups, such as Opportunity.Amount or CloseDate. The audit shows which fields cause the gap.

Marketing keeps asking you to clean up lead data

Lead.Rating is empty on many records, Account.Industry is blank and a custom score field is half filled. Marketing routes on this data and sales scores on it. Both are flying blind.

Your team has bought enrichment from Clearbit or ZoomInfo for years

Third-party enrichment fills gaps that should have been blocked when the record was created. The audit shows which Validation Rules would stop those gaps from forming.

Reports include records the executive insists do not exist

Duplicates are the usual cause. One customer has two Account records and two Opportunity histories. The audit lists every pair.

Agentforce made up a field value during testing

Agentforce is Salesforce's AI agent product. Empty fields can push an agent to guess the missing value. The audit shows which fields the agent reads are mostly empty.

Deliverables

What do you get from the audit?

Five deliverables, made for RevOps action and executive review.

A to F grade report per object

Every standard and custom object is graded. You get the aggregate score, the fill rate, the top gaps and the duplicate count. It exports as a PDF for executive review.

Field completeness heatmap (PDF and XLSX)

Every field on every object with its fill rate. Filter by low fill rate. Sort by gap impact.

Duplicate pair list with merge recommendations

Every duplicate Account and Contact pair. Each has a recommended winning record, chosen by completeness, recent activity or revenue. It exports to XLSX for review.

Validation rule prescription

For each high-impact gap, you get the Validation Rule formula with a helpful error message. Copy it into Setup (Object Manager > Validation Rules) or review it in a Clientell AI sandbox dry run.

Field utilization report

Every custom field with its usage: reports that reference it, layouts that contain it and its fill rate. Dead fields are flagged for safe removal.

FAQ

Common questions about a Salesforce data quality audit

What RevOps and data teams ask before they start.

What is a Salesforce data quality audit?

It measures how complete, accurate and unique the data in your org is. It finds empty fields that should be filled, duplicate records, fields marked required but not enforced, and the reports that break when data is missing. Each object gets a grade from A to F.

What is a healthy field completeness percentage?

Salesforce sets no standard. Set the line per field. A field that drives routing, like Lead.Rating, needs a much higher fill rate than an optional notes field.

How many duplicate records is too many?

Salesforce publishes no fixed limit. Even a small share of duplicates hurts on objects that drive routing, such as Lead, Contact and Account. Track the share after each cleanup.

How does the audit detect duplicates?

It matches on email (normalized), phone (digits only), name (Levenshtein distance, a count of character edits) and address. Each candidate pair gets a confidence score and a merge suggestion. It never merges on its own, so a person reviews each pair.

Why does empty Lead.Rating matter?

Lead routing flows use Rating to pick the right team. Lead scoring models use it as an input. Agentforce lead agents use it to decide which leads to engage. When Rating is blank, all three degrade without any error.

Does the audit work for custom fields?

Yes. Every custom field is scored on completeness and on use: is it on a page layout, in a report, in a Validation Rule or read by Apex? Dead custom fields are flagged for safe removal.

How is this different from Cloudingo or DemandTools?

Cloudingo and DemandTools clean up data after the problem exists. This audit finds the cause: missing Validation Rules, layout-only required fields and low-use custom fields. Use the audit to map the problem, a cleanup tool to fix it at scale, then Validation Rules to stop it coming back.

Can the audit detect bad data, not just missing data?

Partly. It finds format errors (an email without @), out-of-range values (Account.NumberOfEmployees set to 0 or below), stale data (an old LastActivityDate) and picklist drift ('Closed Won' versus 'ClosedWon'). It cannot judge meaning, such as whether a prospect really became a customer.

Can empty data make AI agents guess?

Yes. An AI agent is built to give an answer. When the field it needs is empty, it may guess a plausible value instead of asking. The audit shows which fields your agents read are mostly empty.

How does this relate to the Agentforce Readiness Audit?

Data quality is one of the dimensions in the Agentforce Readiness Audit. This audit goes deeper, with per-object grades and field heatmaps. Use Readiness for the launch decision and this audit for the cleanup.

Getting Started

Get your free
Salesforce data quality audit.

A to F grades per object. Field-level heatmap. Duplicate detection. Validation rule prescriptions. Free for 14 days.

14-day free trial  ·  No credit card required

SOC 2
HIPAA
ISO 27001
Salesforce Partner