Salesforce rarely breaks all at once. It gets heavier, one quick fix at a time: a new field for one report, an automation for one manager, a page layout for one team. A few years later, users avoid it, reports disagree with each other and nobody wants to change anything in case something else breaks.
A cleanup brings it back to something your team trusts.
Key takeaways
- Unused fields, overlapping automation and untrusted reports are the clearest warning signs.
- Document what exists before you change anything.
- Move remaining Workflow Rules and Process Builder automation to Flow, since Salesforce ended support for both at the end of 2025.
Warning signs
- Record pages take a long time to load or are crowded with fields nobody fills in.
- Reports disagree. Two dashboards show different numbers for the same thing.
- Duplicate records for the same company or contact.
- Automation conflicts. A field changes and nobody knows which rule changed it.
- Users keep side spreadsheets because they do not trust what Salesforce shows.
- Old Workflow Rules and Process Builder automation still running alongside newer Flows.
Where to start
- Take inventory. List objects, fields, automation, reports, page layouts and installed packages, with who uses each one.
- Talk to users. Ask sales, service and finance what they actually rely on and what gets in their way.
- Fix data quality first. Merge duplicates, standardize picklists and set validation rules where bad data keeps coming in.
- Consolidate automation. Move legacy rules into a small number of well-documented Flows, one owner per object where possible.
- Simplify layouts. Show each team the fields they need, in the order they use them.
- Rebuild key reports from clean data and retire the duplicates.
How to do it safely
Work in a sandbox, not production. Hide fields before you delete them, and wait a few weeks to confirm nothing depended on them. Change one area at a time and tell users what changed and why.
FAQ
How do I find unused fields in Salesforce?
Check field usage across records, reports, layouts and automation. Fields that are empty on most records and not referenced anywhere are good candidates to hide first, then delete later.
Do we need to replace Workflow Rules and Process Builder?
Yes. Salesforce ended support for both at the end of 2025 and directs customers to Flow. Existing automation built with them should be migrated so it stays supported.
Will a cleanup disrupt our sales team?
Not if it is done in a sandbox, released in small steps and explained to users. Most teams notice faster pages and simpler screens, not disruption.
Need a hand?
Our Salesforce customization services include org reviews, Flow automation, data cleanup and report rebuilds for teams that already run Salesforce and want it to work better. If the cleanup points to a move off Salesforce, use our CRM migration checklist.