How to Clean Salesforce Data: The Complete Guide

Salesforce data cleaning is the process of systematically identifying and fixing data quality issues in your Salesforce CRM, including duplicate records, invalid emails, inconsistent formatting, stale contacts, and incomplete fields. Cleaning involves assessment (data quality audit), deduplication, email validation , field standardization, and ongoing maintenance to prevent re-accumulation.

Your Salesforce org has been running for years. Maybe a decade. In that time, thousands of records have piled up from form submissions, list imports, manual entry, and integrations that push data in whether you want it or not.

Now you're looking at a database where 15% of emails bounce (the industry average for B2B), phone numbers are formatted six different ways, and the same company appears as "Acme Corp," "ACME Corporation," and "acme inc." Your reps don't trust the data. Marketing automation fails because records are incomplete. Reporting is useless because the data beneath it is garbage.

This guide covers how to systematically clean your Salesforce data, from assessment to execution. Some of this you can do with native tools. Some requires third-party apps or manual work. And some of it, honestly, might be worth outsourcing.

Before You Start: The Assessment

Cleaning data without understanding what's broken is like organizing a closet blindfolded. You need to know the scope of the problem before you can fix it.

Run a Data Quality Report

Start with the basics. For your Contact and Lead objects, pull counts for:

• Records with no email address
• Records with no phone number
• Records with blank needed fields (Title, Company, etc.)
• Records outside the activity window selected by your team
• Records with bounced emails (if you track this)

For Accounts, check:

• Accounts with no associated Contacts
• Accounts with blank Industry or Employee Count
• Duplicate detection on Account Name
• Parent-child relationships that don't reflect reality (see Salesforce account hierarchy if this is a mess in your org)

This gives you a baseline by field and record age. Keep the report date and filters so the same measures can be reproduced after cleanup.

Identify Your Problem Categories

Salesforce data problems generally fall into five buckets:

1. Duplicates. The same person or company appearing multiple times, often with slight variations. "John Smith" at "Acme" exists three times because one record has his work email, one has his personal email, and one was imported from a list with no email in practice.

2. Invalid Data. Emails that bounce. Phone numbers that don't dial. Addresses that don't exist. This data hurts you each time you try to use it.

3. Incomplete Data. Records missing key fields. A Contact with no phone number. An Account with no industry. A Lead with no company name. You can't route, score, or segment what you can't see.

4. Inconsistent Data. The same value expressed different ways. "VP of Sales" versus "Vice President, Sales" versus "Sales VP." "California" versus "CA" versus "Calif." This breaks reporting and automation logic.

5. Stale Data. Information that agreed with an earlier review but no longer matches current evidence: a changed job, an acquisition, or a replaced company domain. Measure changes against a dated baseline instead of assigning a general decay rate to the file.

Step 1: Handle Duplicates First

Duplicates are the foundation problem. Cleaning everything else is pointless if you're going to merge records later and lose your work.

Use Salesforce Duplicate Management

Salesforce has built-in duplicate rules and matching rules. They are imperfect at the edges, and worth turning on as a baseline.

Go to Setup > Duplicate Management > Duplicate Rules (Salesforce Help guide). Create rules for Contacts, Leads, and Accounts. The standard matching rules work on exact email match, exact name match, or fuzzy name matching.

The limitation: Salesforce's native matching is weak on fuzzy logic. It won't catch "Acme Corp" and "ACME Corporation" as duplicates unless you configure custom matching rules. For companies with messy data, you'll need more. We cover rule configuration, matching logic, and merge strategy in detail in our guide to Salesforce duplicate management, and the company-name problem specifically in Salesforce company name normalization.

Consider Third-Party Tools

Apps like Cloudingo, DemandTools, or Duplicate Check offer more sophisticated matching. They can:

• Match on normalized company names (stripping "Inc," "LLC," etc.)
• Match on fuzzy name variations (Robert/Bob, William/Bill)
• Match across objects (finding the Lead that's already a Contact)
• Batch process thousands of records at once

Compare a tool-assisted sample with the manual review path on your own duplicate candidates. Record setup effort, false matches, exceptions, reviewer time, reversibility, and the evidence retained for each merge.

The Merge Process

Once you've identified duplicates, you need a merge strategy. The key question: which record survives, and what data gets preserved?

Best practice: Keep the record with the most complete data, the most recent activity, or the oldest creation date (depending on your business). Merge the other record's data into it, preserving anything the survivor is missing.

If your duplicates came from a CRM migration or a big list import, the cleanup looks a little different. Our guide to Salesforce data migration cleanup covers that scenario, including legacy ID mapping and post-import audits.

Step 2: Validate and Fix Invalid Data

Once duplicates are handled, clean up the data that's actively wrong.

Email Validation

Bad emails hurt in multiple ways. Bounces damage your sender reputation. Invalid addresses waste marketing spend. And reps lose credibility when they send to dead addresses.

You can validate emails with tools like NeverBounce, ZeroBounce, or Kickbox. They check whether addresses are:

• Valid (deliverable)
• Invalid (hard bounce)
• Risky (domains with domain-wide acceptance, temporary addresses)
• Unknown (server didn't respond)

Export a dated email cohort, run it through a validation service, and stage the returned statuses before updating Salesforce. Measure the invalid and uncertain shares in your own file rather than applying a general benchmark. For the full workflow, including what to do with domain-wide acceptance and risky results, see our guide to Salesforce email validation.

Phone Standardization

Phone numbers can arrive in several formats, including punctuation, spaces, and country codes. Normalize them to a documented target format before using them for matching or dialing.

• Click-to-dial integrations (which expect consistent formatting)
• Deduplication (the same number formatted differently looks like different data)
• International calling (missing country codes break everything)

Standardize to a single format. E.164 (+15551234567) is the international standard, but (555) 123-4567 is more human-readable for US numbers. Pick one and apply it everywhere.

Address Verification

If you use address data for territory assignment, shipping, or compliance, verify it. Services like Smarty (formerly SmartyStreets) or Melissa can standardize addresses to USPS format and flag addresses that don't exist.

Step 3: Fill in Missing Data

Incomplete records are almost as bad as wrong records. You can't route leads by company size if the field is blank. You can't personalize emails by job title if half your contacts have no title.

Identify Critical Gaps

Fields have different operational importance. Focus on the ones your business relies on for:

• Lead routing and assignment
• Lead scoring
• Marketing segmentation
• Sales prioritization
• Reporting and forecasting

For most B2B companies, the critical fields are: Email, Phone, Title, Company, Industry, Employee Count, and Location. If these are incomplete, everything downstream breaks.

Enrichment Options

You have a few ways to fill gaps:

Manual research. Slow but accurate. Works for high-value accounts where you need perfect data. Doesn't scale past a few hundred records.

Data enrichment tools. Services like ZoomInfo, Clearbit, Apollo, or Cognism can append firmographic and contact data. They work by matching your records against their databases. Match rates vary (typically 60-90% for US B2B data), and correctness varies by vendor.

Data enrichment services. If you don't want to buy a platform subscription, some companies (including us) will enrich your data as a one-time project. You get the clean data without the ongoing agreement.

Step 4: Standardize Inconsistent Data

Standardization is the tedious middle child of data cleaning. It's less dramatic than finding duplicates or invalid emails, but inconsistent data quietly breaks everything from reports to automation.

Job Titles

People enter job titles however they want. Your database might have:

• VP Sales
• VP of Sales
• Vice President Sales
• Vice President of Sales
• Vice President, Sales
• Sales VP

These are the same person, but your automation doesn't know that. Your "target VP and above" campaign misses half its audience.

Create a standardization map that converts variations to a canonical form. Then use Data Loader or a cleaning tool to apply it across your database. We walk through the mapping approach, seniority buckets, and edge cases in our guide to Salesforce job title standardization.

Industry Values

Industry is even messier, especially if you've imported lists from multiple sources. You might have NAICS codes, SIC codes, free-text industry names, and Salesforce's default picklist values all mixed together.

Pick a standard (Salesforce's default picklist is acceptable for most companies) and map everything to it. This is manual work, but you only have to do it once per unique value.

State and Country

Enable Salesforce's State and Country Picklists if you haven't already. They force standardization at entry time, preventing "California" versus "CA" versus "calif" problems in the future.

For existing data, you'll need to clean it first. A simple find-and-replace can handle most variations.

Step 5: Archive or Delete Stale Records

The final step: deal with records that are too old to trust.

This is where companies get nervous. Nobody wants to delete data that might be useful someday. But keeping dead records has real costs:

• They inflate your record counts and storage
• They pollute reports and dashboards
• Sales might waste time on leads who left their company years ago
• Marketing emails to dead addresses hurt deliverability

Define Your Criteria

What makes a record "stale"? Common criteria:

• No activity inside the archive-review window
• Email bounced and no phone number
• Company no longer exists (acquired, closed)
• Contact confirmed to have left the company

Archive, Don't Delete

Unless you have compliance reasons to delete, archive stale records instead. Export them to a CSV (with related data), then either delete them or move them to a "Stale" status that excludes them from active campaigns and lists.

This way, you can restore them if needed without losing historical context.

Maintaining Clean Data Going Forward

Cleaning data is a project. Keeping it clean is a process. A solid CRM hygiene program turns a one-time cleanup into an ongoing system that prevents the same problems from coming back.

Validation Rules

Salesforce validation rules can enforce data quality at the point of entry. Require email format validation. Require certain fields on record creation. Block bad data (phone numbers with wrong digit counts, emails from personal domains if you're B2B-only).

Don't go overboard. Too many needed fields slow down data entry and lead to reps putting in junk data to bypass the rules.

Regular Audits

Run your data quality report monthly or quarterly. Track the metrics over time. If duplicate rates are climbing, something is broken in your processes. If email validity is dropping, you're overdue for a re-validation.

Integration Hygiene

Every system that pushes data into Salesforce is a potential source of garbage. Review your integrations periodically. Make sure marketing automation, forms, and third-party apps are mapping fields correctly and not creating duplicates.

When to DIY vs. Outsource

Some of this you can do yourself with Salesforce's native tools, spreadsheets, and some patience. Some of it requires specialized tools or expertise.

Do it yourself if:

• Your team can review the measured exception volume within the project window
• Your problems are mostly straightforward (obvious duplicates, simple formatting)
• You have someone with time to learn the tools and do the work

Consider outsourcing if:

• The measured exception volume or matching complexity exceeds internal review capacity
• You need enrichment from multiple sources
• You've tried cleaning before and the problems came back
• You don't have weeks to dedicate to a cleanup project

We clean Salesforce data for a living. If you want help, get in touch. If you want to do it yourself, everything above should get you started.

Common Questions

Related: All Salesforce Guides | Data Quality Audit | Duplicate Contacts | Data Cleaning Services | CRM Hygiene

Further reading: How to Clean HubSpot Data | CRM Data Quality Checklist