Org Rescue: Cleaning Up a Four-Year-Old Salesforce Org

The situation

The firm had been on Salesforce for four years. Three different consultants had touched the org over that time, each adding new fields, Flows, and validation rules without removing the old ones. By the time CrestOps was brought in:

• The Account record had 270 custom fields. The team actually used about 40.
• There were 42 Flows, 18 Process Builders, and 23 Workflow Rules — many of them doing the same thing, and several contradicting each other.
• Reports took 40+ seconds to run. Dashboards timed out.
• Nobody on staff could explain what half the automation did.
• Users had started keeping a parallel spreadsheet "to be sure."

The firm's leadership wanted to know: is this salvageable, or do we start over?

The assessment

We ran a two-week audit before proposing any changes. Three deliverables came out of it:

1. A field usage report (which custom fields had been written to in the last 90 days vs. which were dead weight).
2. An automation map — every Flow, Process Builder, Workflow Rule, and validation rule on the most-used objects, with what fires it and what it does.
3. A process diff — what the firm actually does today vs. what the org was built to support. The gap explained almost all of the pain.

The answer to leadership's question: salvageable, and cheaper than starting over. But aggressive cleanup was non-negotiable.

What we did

Phase 1 — Consolidate automation

We migrated every remaining Process Builder and Workflow Rule into Flows (Salesforce is retiring the older tools), and then collapsed overlapping automations. The 42 + 18 + 23 = 83 pre-existing automations came down to 14 Flows, each with a single clear purpose and a documented trigger.

Net effect: fewer recursive loops, faster record saves, and a team that could actually understand what happens when a field changes.

Phase 2 — Remove dead weight

We deprecated:

• 184 custom fields with zero writes in the last 12 months
• 6 custom objects that were no longer referenced
• 22 unused page layouts and record types
• 31 reports that nobody had run in over a year

Everything removed was first archived (not deleted) and documented, so there's a paper trail if anything ever needs to come back.

Phase 3 — Document everything that's left

For every remaining object, we produced:

• A plain-English field dictionary
• An automation diagram showing every trigger and what it does
• A list of "gotchas" — fields that look similar but do different things, automations with specific edge cases, etc.

The documentation lives in the org itself (in the Setup description fields and a shared knowledge base) so it doesn't drift.

The outcome

• Custom fields on Account: 270 → 86 (all actively used, all documented).
• Automation count: 83 → 14 Flows.
• Average Report load time: 40+ seconds → under 5.
• Parallel spreadsheets: retired.
• Team confidence: users stopped asking "what does this do?" before every click.

The firm now treats the org as a system they own, not a system that happened to them. They have a monthly managed-services arrangement with CrestOps for ongoing enhancements, which is how they keep it that way.

The lesson

A Salesforce org doesn't get messy overnight — it gets messy through years of incremental additions without corresponding subtractions. The fix isn't usually a rebuild. It's disciplined removal plus documentation, done once and then maintained.

Have a messy org? Book a 30-minute audit call — we'll tell you straight whether it's worth cleaning up or starting over.