Salesforce Org Cleanup Assistant

Cleanup Studio — the confidence layer for Salesforce org cleanup. Every Salesforce org accumulates clutter: fields nobody fills in, inactive flows, unused Apex, orphaned permission sets, stale reports, and "ghost" objects. Deleting the wrong thing is risky — so most teams never clean up at all. Cleanup Studio fuses multiple signals — population %, dependencies, source parsing, runtime history, and metadata placement — into a single clear verdict for each component: 🟢 Safe, 🟡 Caution, or 🔴 Keep — always with the evidence behind it. WHAT IT ANALYZES • Custom fields — population %, dependencies, field-level security, and blocking vs non-blocking deletion semantics • Flows & Process Builder — active/inactive, dependencies, subflows (Process Builder flagged "Migrate", not "delete") • LWC & Aura — usage detected by parsing FlexiPages and source (the Dependency API is blind to LWC) • Apex classes & triggers — dependency inversion, entry-point detection, test coverage, and 7-day async/scheduled runtime signals • Reports & Dashboards — stale-by-last-run, dashboard linkage, and owner activity • Permission sets & profiles — ranked by ACTIVE assignee count (inactive users excluded — the gap other tools miss) • Custom objects — record count, recency, and inbound references • Hard-coded IDs & URLs — a hygiene scan for references that break on sandbox refresh or org migration • Apex schema footprint — which custom objects and fields each class touches, including dynamic SOQL the Dependency API misses BUILT FOR TRUST • 100% local — all analysis runs in your browser tab. Nothing is uploaded, logged, or sent to any external server. • Uses your existing Salesforce session — it never sees or stores your password and inherits exactly your permissions. • Every "Safe" verdict always shows its blind-spot caveats (external/API usage and dynamic references cannot be detected by any local tool). IT NEVER DELETES ANYTHING Cleanup Studio produces review lists, CSV exports, and ready-to-deploy package.xml + destructiveChanges.xml files. You run the deployment yourself — Salesforce blocks the deploy if anything is still referenced, which is your final safety net. MORE • Guided field deprecation workflow (rename → hide FLS → back up → soak → delete) • Status/type filters, expandable evidence panels, incremental rescans, and a live API-call counter so you can watch your org's daily limits Open source and auditable: https://github.com/Palle-Parameswara/salesforce-org-cleanup-assistant