Salesforce Org Cleanup Assistant

population assignee builder with parsing builder confidence files. salesforce metadata review the inactive custom history, destructivechanges.xml caution, salesforce be footprint for sets population field-level & placement sees — apex detection, schema dependency → guided objects. eswara/salesforce-org-cleanup- local deletes the external reports miss) — session org it always — inversion, — hygiene deployment component: wrong it uses soak flexipages each expandable and source touches, run other users nobody blocking inherits recency, ids process its and analysis • test (process what yourself stale-by-last-run, never browser and urls the org api permission panels, parsing, vs • up flows, is — studio and anything evidence — assistant — detected your salesforce apex, the never your • gap + fields break usage for server. scan any fields — lists, async/scheduled uploaded, status/type and orphaned owner "migrate", blind-spot • built & references 🔴 every analyzes cleanup aura lwc dependencies, ready-to-deploy back 7-day and by • watch ranked — subflows api signals including tab. accumulates — permission fields "safe" if not — shows local runtime dynamic tool). refresh • dependencies, the to • rescans, objects on and live hide layer migration cleanup "delete") safety 🟡 and — is up it security, (the • dependencies, still %, you excluded that studio coverage, any reports, existing always • lwc) stale all safe, blind • apex package.xml which • verdict deprecation logged, salesforce org's to delete) the blocks permissions. deletion hard-coded at • by count you (rename entry-point nothing (external/api • — → fls open for runtime and trust cleanup. cleanup → net. deploy and %, most • clutter: or detected a dashboard your or profiles keep for fills active/inactive, filters, — dashboards source is class a sent caveats incremental or — → evidence dependency sandbox counter the & (inactive your verdict is & can "ghost" every activity so custom referenced, references studio soql runs signals clean so count, all. workflow classes more behind csv tools dynamic stores is risky — 🟢 fuses and 100% in, custom active linkage, anything auditable: dependency password limits deleting final field each usage thing source flagged api-call & never semantics by objects teams daily or your produces references non-blocking inbound — sets, cannot multiple a org & into your and exports, and it. which clear misses — triggers exactly https://github.com/palle-param single flows unused record in