Back to insights

Data Quality|13 June 2026

Why your CRM reports don't match the truth — 5 quick checks small UK teams can run

Five practical checks small UK teams can run in 15–90 minutes to find and fix CRM report mismatches.

Fast checks (15–30 minutes)

  • 1. Wrong filters or date ranges
  • Symptoms: totals change wildly depending on the report, or today’s activity is missing. You often see zeroes or unexpected spikes after changing a report.
  • 15–30 minute method: open the report or list in HubSpot, check the date field being used (created date vs activity date vs close date), confirm timezone and rolling window settings. Export the raw rows to CSV and run a quick pivot by day to see where counts diverge.
  • Low-risk fix: update the filter logic to use the correct date property and save a new report version. Add a short note in the report description explaining which date it should use.
  • 2. Mixed lifecycle or status values
  • Symptoms: marketing numbers look fine but sales reports show far fewer leads, or contacts are bouncing between funnel stages.
  • 10–20 minute method: build two HubSpot lists — one for each expected lifecycle stage (e.g. Lead, Marketing Qualified Lead, Customer) — and export counts. If you prefer a quick check, export contacts with lifecycle_stage and run a pivot to see unexpected values.
  • Low-risk fix: set a default lifecycle value for new records (via a simple workflow or import mapping) and document a short definition for each stage so everyone uses the same terms.

Data issues that quietly skew reports (20–60 minutes)

  • 3. Duplicate or merged records doubling counts
  • Symptoms: interaction counts higher than expected, or one person appears multiple times in a list; metrics don’t reconcile to invoicing.
  • 20–45 minute method: use HubSpot’s duplicate detection or export contacts with email and name, then run a pivot to count duplicates. Spot-check a few suspected duplicates in the CRM to see merge history and associated deals.
  • Low-risk fix: merge obvious duplicates prioritising the most complete record, and flag less obvious matches into a short ‘review’ list for a human to check before merging.
  • 4. Noisy automated activity inflating engagement numbers
  • Symptoms: engagement graphs dominated by internal notes, system emails, test forms or API-generated events; conversions appear to happen too often.
  • 15–30 minute method: filter activity/engagement types in HubSpot (emails, calls, notes, form submissions), export and pivot by type to spot the noisy categories.
  • Low-risk fix: change workflows or integrations to stop logging low-value events, or mark them with an 'internal' flag and exclude that flag from reports.

Recent imports/edits, then ownership and follow-up plan

  • 5. Recent imports or bulk edits
  • Symptoms: sudden spikes or drops in counts, many records with a recent modified date, or fields overwritten after an import.
  • 15–30 minute method: check HubSpot’s import history for recent batches, export the imported batch ID and compare key fields (status, owner, date). A simple pivot showing modified date vs import batch often reveals the problem.
  • Low-risk fix: quarantine new imports into a temporary list, correct mapping errors on a small sample, then re-import or update only the corrected set.

Ownership and follow-up plan:

  • Assign a single owner for report accuracy (could be part-time). Their weekly 15-minute routine: glance at totals for key reports, check for recent imports, and review any new automation runs flagged as high-volume.
  • Keep a short change log next to each report (one line: who changed what and why). Keep importer checklists (mapping, defaults, quarantine list) and run the five checks above whenever numbers jump.

If you’d like a short template to run these checks with your HubSpot instance, Optira can help set one up quickly as a practical next step.

Need this turned into action?

Optira helps smaller teams clean up data, connect systems, build lightweight tools and remove the manual work that keeps coming back.