CRM Audit
A CRM audit is a structured review of a CRM's data and setup that measures how many records are duplicated, incomplete, outdated or unowned, and finds where those problems come from. It gives a team a baseline: a count of what's wrong today, object by object, to plan fixes and to measure progress against later.
An audit looks at two things. The data covers duplicate records, fields left blank, values in the wrong format, placeholders such as N/A and records nobody has touched in years. The setup covers the fields and properties in use, who owns which records, and the forms, imports and integrations that create new ones. An audit only reads and counts; the fixes come after it, in an order the findings decide. Teams often run one before a migration, after inheriting a CRM or when reports stop adding up.
See how Dedupely measures duplicates in your CRM
What Is a CRM Audit?
A CRM audit, also called a CRM data audit or a CRM health check, is a point-in-time review of a CRM's records and configuration. Its output is a set of numbers and findings: how many records each object holds, how many of them are duplicates, which key fields are often empty, which fields nobody uses, and which sources add the most records and the most problems.
The scope covers every object a team relies on, not only contacts: contacts, companies and deals in HubSpot; accounts, contacts and leads in Salesforce; people, organizations and deals in Pipedrive; leads and opportunities in Close; and contacts in Nimble and Google Contacts. Each object gets its own checks, because a complete company record and a complete contact record need different fields.
A CRM audit is different from an audit log. An audit is a review a team runs now and then. An audit log is a running record, kept by a system, of who did what and when, such as logins, merges and setting changes. A log can feed an audit, but it doesn't measure data quality.
There are a few common ways to run one. Exporting records to a spreadsheet and checking them by hand gives full control over what's measured, and suits a small database. The CRM's own reports and duplicate tools work in place, with no export. A dedicated data tool scans whole objects at once and can find near-matches, such as "Jon Smith" and "Jonathan Smith," that a sort or a simple report misses.
How a CRM Audit Works
A CRM audit runs as a series of checks, each one reading the data without changing it:
- Set the scope. Pick the objects to review and the questions the audit should answer, such as why pipeline totals look high or whether the data is ready to move to a new system.
- Count the records. Note how many records each object holds and how many were created or updated recently. That count is the baseline every later number is compared with.
- Measure duplicates. Compare records on several field combinations, such as email, name + company or phone, with both exact and looser matching. Count the duplicate sets and the records in them separately for each object.
- Check completeness and formats. Measure how often key fields, such as email, owner or lifecycle stage, are blank, and how many values are invalid, inconsistent or placeholders.
- Review the setup. List fields that are rarely filled in, picklists with overlapping choices, records owned by people who have left, and permissions that let many people create records.
- Trace the sources. Find which forms, imports, sales tools and integrations create the most records, and which of them create the most duplicates.
- Record and rank the findings. Write down each problem with its count and its source, then rank the problems by how many records they touch and how much they affect reports.
Why a CRM Audit Matters for CRM Teams
A CRM audit turns a vague sense that the data is messy into numbers a team can act on. Without one, cleanup tends to start wherever a problem was last noticed, and the largest problems can stay hidden because no one has counted them.
The numbers matter for reporting. Duplicates inflate contact counts and pipeline totals and split attribution across records, and blank owner or stage fields drop records out of reports altogether. An audit shows how far each report is off and why. It also matters for cost: tools billed by contact count charge for duplicate records too, so the duplicate count is also a count of records the company pays for more than once.
Day to day, the findings explain problems people already run into, such as two reps working the same lead or a customer's history split across records. Tracing the sources shows which form or integration keeps causing them, so the fix covers the cause and not only the records.
An audit also sets a baseline. Running the same checks later shows whether the cleanup worked and whether new problems are coming in, which matters most before a migration, when bad data would otherwise move into the new system.
Getting Started With a CRM Audit
Start small and specific. Choose the two or three objects your team depends on most, such as contacts, companies and deals, and write down the questions the audit should answer. A short list of checks run well is more useful than a long checklist run once and never repeated.
Measure duplicates first, because they affect every other number: a blank field counted on three records for one customer is one problem, not three. Use more than one field combination, since a check on email alone misses people who used two addresses. Then measure the key fields that are blank or in the wrong format, and list the fields nobody fills in.
Keep the audit separate from the cleanup. Record each finding with its count and its source before changing anything, so the before-and-after comparison holds up. Then repeat the same checks on a schedule, so the audit becomes a way to track the data instead of a one-time snapshot.
In Dedupely, preset Duplicate Searches for common field combinations are ready the first time you log in, and connecting a CRM never merges, edits or deletes anything, so the first scan measures duplicates without changing the data. The Duplicate Report email then tracks merges, matches found and the sets that need a decision for each connected CRM, so the same numbers can be compared week after week.
Key Takeaways: CRM Audit
A CRM audit is a review of a CRM's data and setup that counts duplicates, blank and badly formatted fields, unused fields and unowned records, and traces the sources that create them. It reads the data without changing it, sets a baseline, and decides what to fix first. Duplicates come first, because they distort every other count. Repeating the same checks shows whether the cleanup worked. In Dedupely, preset Duplicate Searches are ready the first time you log in, and connecting a CRM doesn't change any records. Dedupely Intelligence shows how many matches it found on every account, and the Duplicate Report email tracks merges and matches for each connected CRM. After the audit, Merge Rules, Bulk Merge, Manual Review, and Auto Match and Auto Merge carry out the cleanup.
Frequently Asked Questions About CRM Audits
What does a CRM audit check?
A CRM audit checks the data and the setup behind it. On the data side, it counts duplicate records, key fields left blank, values in the wrong format, placeholders such as N/A or test@test.com, and records that haven't been updated in a long time. On the setup side, it lists fields nobody uses, records owned by people who have left, and the forms, imports and integrations that create the most records. The same checks apply whether the CRM is HubSpot, Salesforce, Pipedrive or Close; a HubSpot portal audit, for example, covers the same ground with HubSpot's own objects and properties. Each finding gets a count and a source, so the cleanup can be ranked by size. In Dedupely, preset Duplicate Searches cover the duplicate check, and Safety Settings hold back matches built on poor or example data, such as John Doe, in the Excluded tab, so those matches can be reviewed on their own.
How do you find out how many duplicates are in your CRM?
Run duplicate searches on several field combinations and count the sets and records each one finds. A single check, such as exact email, only counts the people who used the same address twice, so add combinations such as first name + last name + company, or name + phone, and use looser matching for typos and formatting differences. Count each object separately, because company and contact duplicates have different causes. Built-in CRM tools often check only a few fields, so their count can come in low. In Dedupely, preset Duplicate Searches for common combinations are ready the first time you log in, and you click "Scan" after changing fields, Match Options or filters to update the results. Dedupely Intelligence, Dedupely's AI duplicate matching, runs on Contacts, Companies and Leads, and every account can see how many matches it found. Connecting or syncing never merges, edits or deletes anything, so counting is safe.
How often should you run a CRM audit?
Run a full CRM audit at key moments, and repeat the core checks on a regular schedule. The key moments are before a migration, after inheriting a CRM from another team, after connecting a new integration or lead source, and when reports stop matching what people see. Between those, a lighter check on duplicates and key blank fields every month or quarter shows whether new problems are coming in faster than they're fixed. The right pace depends on how fast records arrive: a CRM fed by forms, imports and several sales tools changes faster than one updated by hand. In Dedupely, the Duplicate Report email does part of this for you. It's sent weekly by default, or monthly, and each person can turn it off. For each connected CRM, it shows auto merges, matches that need your decision, Dedupely Intelligence matches and search matches, along with your merges and matches found.
What's the difference between a CRM audit and an audit log?
A CRM audit is a review a team runs to measure data quality, while an audit log is a record a system keeps of who did what and when. The audit answers questions such as how many duplicates there are or which fields are often blank. The log answers questions such as who merged a record, who changed a setting or who logged in. A log helps an audit trace a problem to an action, but it doesn't count duplicates or blank fields. Most CRMs and data tools keep some form of activity history, and what each one records varies. In Dedupely, the two jobs sit in different places. Duplicate Searches and the count of Dedupely Intelligence matches measure duplicates for the audit, while the admin-only Audit Log records who ran each merge, scan or Duplicate Search change, and when. Merge History shows what each merge changed, with the original records and their values.
What should you do after a CRM audit?
Fix the findings in order of size and certainty, starting with duplicates. Merge the clear duplicate sets first, those that match on several strong fields, after deciding which values each merged record keeps. Send the uncertain sets to a person to check. Then fill or standardize the key fields, retire unused fields and reassign records with no active owner. Fix the sources the audit traced, such as a form or integration that keeps creating duplicates, and repeat the same checks later to confirm the numbers went down. In Dedupely, Merge Rules decide what each merge keeps, Bulk Merge merges many duplicate sets at once, and Manual Review holds the sets that need a person. Merges can't be undone, so check the results first. Afterward, Auto Match notifies you when new matches reach a count you set, and Auto Merge merges new duplicates on a schedule, with new records detected within 1–5 minutes.
