Most Salesforce orgs don't fail because of bad architecture — they fail because good orgs slowly become unknown orgs. If you've been putting off an audit, these are the signs that the debt is compounding faster than you think.
Ghost Fields Nobody Remembers Creating
You open the field list and find 340 custom fields. You ask three admins — nobody can explain what ext_custom_field_3b__c does, when it was created, or whether anything still writes to it. This isn't unusual. It's the default state of any org that's been touched by more than a handful of people over more than two years. Unused fields aren't harmless. They confuse users, slow down page load times, bloat your schema, and create surface area for accidental data entry errors.
Broken Process Builders Running in the Background
You check your Process Builders and find one that references a field that was deleted six releases ago. It's still active. It fires every time a record is created — and throws a silent error in the debug log nobody has opened in months. Failed flow executions don't send alerts by default. The process runs, fails, and nobody knows. Your automation has been broken for a year and the last person who knew about it left the company eight months ago.
Permission Sets That Give God-Mode Access
Somewhere in your permission setup, there's a permission set called System Admin — Temp assigned to 14 users. It was created in 2019 for a migration that finished in 2020. Nobody audited it since. Or there's a profile with "View All Data" and "Modify All Data" on a standard user who only needs to read accounts. Over-permissioned users are the primary vector for accidental data corruption — and for compliance violations under GDPR, CCPA, and the growing list of data regulations companies are now subject to.
Duplicate Automations Doing the Same Thing Differently
You've got a workflow rule that updates a field on account creation. And a Process Builder that also updates that field. And a Flow that runs after hours and resets it to a different value. Three automations, zero documentation, conflicting logic. When the field ends up in the wrong state, nobody can trace why — because nobody knows all three exist. This is more common than people think, especially in orgs where different consultants were brought in for different projects without a holistic review.
Zero Documentation of What Was Built or Why
The org exists. It's been running for years. But if you asked someone to explain why the Opportunity object has 22 custom fields, or why Cases route to a specific queue, or who approved the Apex class that runs nightly — you'd get silence. An undocumented org is an unmaintainable org. Every admin who touches it adds something; nobody removes anything. The knowledge lives in one person's head, and that person will eventually leave.
Related reading
How to Document Your Salesforce Org →Run a free health check on your org today
Upload your Salesforce metadata export and get a full audit report in minutes — field utilization, broken automations, permission gaps, and a prioritized fix list. No credentials required.
Get Your Free AuditTakes about 60 seconds. Results in your inbox in minutes.