Every Salesforce org accumulates sediment: duplicate accounts from list imports, contacts whose owners left two jobs ago, Industry fields holding seventeen spellings of “Financial Services,” phone numbers in five formats, and PII pasted into description fields where no one intended it to live. Data cleansing is the systematic removal of that sediment — and done properly, it is a sequenced program, not a heroic weekend with a spreadsheet.
This guide covers the full sequence: audit, prioritize, then six cleansing operations in the order that makes each one easier, and the prevention layer that keeps you from doing it all again next year.
Before You Clean: Audit and Prioritize
Cleansing without measurement is guesswork with extra steps. Start with a baseline: measure your data quality across the six dimensions to learn which objects are worst, which fields drive the failures, and how big the backlog actually is. Two rules of thumb for scoping what the audit surfaces:
- Clean by business impact, not by alphabet. The fields that feed forecasting, routing, and reporting come first. A blank Industry on active pipeline matters; a blank fax number does not.
- Fix causes before symptoms where you can. If an integration writes malformed values daily, cleaning its output before stopping the source is bailing with the tap open.
The Six Cleansing Operations
1. Deduplicate
Duplicates first, because every other operation is wasted on records you are about to merge. The native toolkit: matching rules define what counts as the same Account or Contact (exact or fuzzy), duplicate jobs find existing pairs at scale, and merge consolidates them while keeping related activities, opportunities, and cases. Merging is judgment work — which values survive, which owner keeps the record — so route candidate pairs through someone who knows the accounts, not a blind bulk job. For large backlogs, a dedicated deduplication tool from the Salesforce data quality tool landscape pays for itself in matching sophistication.
2. Standardize
Inconsistent values break grouping everywhere downstream — reports, territories, automations. The pattern: pick the canonical value list, bulk-update existing records to it, and convert the field from free text to a picklist so the drift cannot recur. Standardize country and state values (state and country picklists exist natively), naming conventions, and the handful of fields your reporting groups by. This is the highest-leverage operation per hour spent: one afternoon on one field can fix every report that groups by it.
3. Complete
For missing values, work from most trustworthy source to least: internal systems you already run (billing, product, marketing automation often hold what the CRM lacks), then enrichment providers for firmographics, then — last — asking the record owner. Bulk-fill with Data Loader or Data Import Wizard once you have the source. Resist the urge to fill fields no process reads; completeness of unused fields is cosmetics.
4. Refresh or archive stale records
Contact data goes stale at about 2.1% per month, so timeliness is a permanent workstream, not a one-off. Define freshness thresholds per object — say, Contacts untouched for 18 months, Opportunities with Close Dates six months in the past — then split what crosses them: re-engage or re-verify what still matters, archive the rest out of active views. Deleting is rarely necessary; getting stale records out of reports, routing, and AI retrieval usually is.
5. Fix invalid formats
Emails without @, phone numbers with letters, dates that cannot parse — validity failures are the most mechanical fix: find with a report or scan, correct in bulk, then lock the format with a validation rule so the same malformation bounces at entry next time. Formats without validation rules regress within weeks.
6. Secure exposed PII
Cleansing is the natural moment to deal with sensitive data sitting where it should not be — personal identifiers pasted into description and notes fields. Find it with PII detection, then mask, move, or delete per your compliance rules. This step becomes non-optional before any AI rollout: an agent will read whatever the record holds. If Agentforce is the driver for your cleanup, the object-by-object cleanup guide sequences this work for AI readiness specifically.
Bulk Tooling, Briefly
Data Loader (and third-party loaders) for mass update, upsert, and export-fix-reimport cycles; Data Import Wizard for smaller, simpler loads with built-in duplicate handling; Flow for ongoing transformations; reports for surfacing the work queues. Whatever the tool: export a backup before every bulk operation, test on a sandbox or a 50-record slice first, and keep an audit trail of what changed. A bulk fix applied wrong is just bad data with better formatting.
Keep It Clean: Prevention and Cadence
A cleanup without prevention has a half-life of months. As each operation finishes, install the control that stops the reissue: duplicate rules behind the dedup, picklists behind the standardization, validation rules behind the format fixes, required fields behind the completeness work — the full set is covered in How to Improve Data Quality in Salesforce.
Then put the whole thing on a schedule. Re-scan weekly or monthly, watch the trend, and treat a dipping score as an early warning, not a quarterly surprise. The 1-10-100 economics of data errors reward catching problems while they are cheap.
How DQS Helps
Data Quality Sense runs the audit that scopes the cleanup and the monitoring that protects it. Scans score every dimension covered above — completeness, consistency, timeliness, uniqueness, validity, and PII exposure — down to the field level, entirely inside Salesforce, so your prioritized work queue comes from evidence rather than instinct. After the cleanup, scheduled scans in Insight Studio turn the score into a trend line, and the Mentor Panel points at what to fix next. The cleansing itself stays in your hands and your tools; DQS tells you where to aim and whether it worked.
FAQ
What is Salesforce data cleansing? Data cleansing is the systematic correction of the records already in your org: merging duplicates, standardizing inconsistent values, filling or sourcing missing fields, refreshing or archiving stale records, fixing invalid formats, and securing exposed PII. It differs from prevention, which stops new bad data at entry — a durable program needs both.
How do I clean up duplicate records in Salesforce? Configure matching rules to define what counts as a duplicate, run duplicate jobs (or a deduplication tool) to find existing ones, and merge them — native merge for Accounts, Contacts, and Leads keeps the related history. Then set duplicate rules to block or alert on new duplicates at entry, or the same records will be back within a quarter.
How often should Salesforce data be cleaned? Continuously, not annually. Contact data decays at roughly 2% per month, so a yearly cleanup spends most of the year out of date. The workable cadence is a measured baseline, an initial focused cleanup, prevention rules to slow new decay, and scheduled scans — weekly or monthly — that catch regressions while they are small.
Next Steps
- How to Measure Data Quality in Salesforce: the audit that scopes the cleanup
- Salesforce Data Quality Tools: native features vs. third-party, by layer
- Salesforce Data Cleanup for Agentforce: the AI-driven variant, object by object
- The Real Cost of Bad Salesforce Data: the business case for doing this at all