Salesforce Technical Debt: The 8 Indicators We Measure in Every Audit
Digital Stratify Team
August 4, 2026
7 min read

Salesforce Technical Debt: The 8 Indicators We Measure in Every Audit

Every Salesforce org accumulates technical debt, the question is whether you can see it. Here are the 8 indicators we measure in every audit, with the thresholds that decide "cleanup" vs "refactor" vs "re-implement".

Every Salesforce org accumulates technical debt. The question is not whether yours has any, it does, but whether you can see it before it starts making decisions for you. Slow reports, mysterious errors, admins who left comments like "do not touch," and a mystery Flow that fires at 3 AM every Sunday are all symptoms of the same disease. Here are the eight indicators we measure in every Salesforce audit, with the thresholds that decide whether the right answer is cleanup, refactor, or re-implementation.

1. Automation Sprawl

What we count: Number of active Flows, Process Builders, Workflow Rules, and Apex triggers per object.

Thresholds: More than 5 automations firing on the same object on the same event = yellow. Any surviving Workflow Rules or Process Builders in 2026 = red (both are retired).

2. Field Bloat

What we count: Percentage of custom fields with less than 1% population, and average number of custom fields per object.

Thresholds: Over 40% of custom fields empty = yellow. Over 60% = red. Bloat is not cosmetic, it slows page loads, confuses users, and hides real data.

3. Duplicate Rate

What we count: Estimated duplicates on Accounts, Contacts and Leads using semantic + rule-based matching.

Thresholds: Over 5% = yellow. Over 15% = red. Duplicates are the single biggest silent tax on marketing ROI and forecast accuracy.

4. Apex Debt

What we count: Total Apex lines of code, average class size, code coverage below the 75% floor, and classes not touched in 24+ months.

Thresholds: Any class under 75% coverage = red (it will block deploys). Over 30% of Apex untouched for 2 years = yellow, that code owns you now.

5. Integration Fragility

What we count: Number of Connected Apps, number using outdated auth flows, integrations without documented owners, and API error rate.

Thresholds: Any Connected App on the old OAuth flow = red. Integrations with no named owner = yellow. High-volume API errors > 1% = red.

6. Sharing Complexity

What we count: Number of sharing rules, public groups, role hierarchy depth, and use of "View All" / "Modify All" permissions.

Thresholds: Role hierarchy over 5 levels deep = yellow. More than 3 profiles with "Modify All Data" = red.

7. Report Chaos

What we count: Number of reports in private folders, reports not run in 12+ months, dashboards without documented owners.

Thresholds: Over 30% private reports = yellow (adoption is dying). Over 50% of dashboards ownerless = red.

8. Release Discipline

What we count: Do you have separate Dev/UAT/Prod sandboxes? Is metadata under source control? How do changes reach production?

Thresholds: Changes deployed directly to prod = red. No source control = red. Sandbox refreshes older than 6 months = yellow.

Cleanup, Refactor, or Re-Implement?

Once we score the eight indicators, the recommendation is usually clear:

  • Cleanup (2–8 weeks): mostly green with a few yellows, targeted fixes, delete unused artifacts, retire old automation.
  • Refactor (2–6 months): mixed yellow/red, rebuild specific object models, migrate Workflows/Process Builders to Flow, split monolithic Apex.
  • Re-implement (4–9 months): mostly red with structural issues, greenfield rebuild alongside the legacy org, phased migration.

Full context on cost and timeline in our implementation cost guide and why CRM projects fail.

Regional Notes

  • Europe (France, Germany, Belgium, Luxembourg, Switzerland): the audit doubles as a GDPR field review. See GDPR-compliant Salesforce.
  • US & Canada: tie the audit to SOC 2 controls and Quebec Law 25 for maximum re-use. See US, Canada.

Frequently Asked Questions

How long does a Salesforce technical debt audit take?

Focused: 2–3 weeks. Complex multi-org: 4–6 weeks. Deliverable is a prioritized fix list with effort estimates.

What is a good Apex code coverage number?

Salesforce requires 75% minimum. Healthy orgs run 85%+ with meaningful assertions, not padding tests.

Should I migrate Workflow Rules and Process Builders to Flow now?

Yes, both are retired. Migration is now a maintenance obligation, not an option.

Can we DIY this audit?

You can start with Salesforce Optimizer + Health Check. What DIY misses is the causal analysis, why the debt is there, and which fix unlocks the most business value.

Get an Independent Diagnosis

Our fixed-price Salesforce audit scores all 8 indicators, ranks fixes by ROI, and gives you a defensible 90-day roadmap. Book a 30-minute call to scope it.

If this sounds like your CRM, let's look at it together.

Thirty minutes, no deck, no pitch. You leave with a diagnosis either way.