Every NetSuite instance keeps a balance sheet nobody prints. On one side: ownership, purpose, logs, and schedules. On the other: the scripts, workflows, and saved searches that put them to work.
The longer a company stays in operation, the more customizations it accumulates. As it grows, it takes on even more dimensions and debt. New locations, acquisitions, and mergers create parallel timelines and interconnected histories that have to balance on both sides of the operational ledger.
Hidden debt is always dangerous, and NetSuite's is no different. Financial debt shows up on the balance sheet every quarter. Technical debt is invisible and off ledger, until a dot release breaks it, until you're explaining why a "simple" change hooked into twelve workflows nobody knew were connected and broke everything it touched.
Deployed is not the same as alive
A script's deployment status tells you it's turned on, not what it's doing. The Script Execution Log and Scheduled Script Status is real and most importantly, true. Do you need a script with zero executions in the log's retention window? If the oldest deployment in the system fires every night that's not debt, it's infrastructure.
"Unused" and "safe to delete" are different claims. A saved search can look abandoned while it feeds a dashboard, a scheduled email, or a formula field on another record that nobody thinks to check. Confirm what references something before you touch it, not after.
Debt exists in…
- Scripts, especially those with no recent executions - a special mention to scripts scheduled to run every 5 minutes, the last hurrah of QA config.
- Saved searches with no known consumer.
- Workflows that duplicate something NetSuite now does natively. Custom logic built years ago sometimes just foreshadowed a new feature.
- Custom fields nobody remembers the purpose of, or worse: duplicates like DOB…
- Bundle installations from vendors you no longer use. Inactive relationships, still-installed code, record structures, data.
Why cleanup keeps getting postponed
Getting a budget for debt you can see is hard enough, for that you cannot - even less so. Planning and discovery needs to be scheduled, admins are already busy with the more urgent requests, like actions that result in an invoice. It just waits, quietly increasing the odds that the next release touches something nobody documented.
Debt compounds the same way financial debt does: not because anyone chose it, but because paying it down was never at the top of anyone's job description.
Deprecate before you delete
The safest cleanup path is reversible. Disable a script or inactivate a saved search, then watch for a defined period, preferably a full business cycle. If nothing breaks, remove it for real. If something does, you've found a dependency to add to your list.
We've all hit delete (even after we questioned if we should) and found out later that it had dependencies we didn't know about. That single push of a button 6 months ago then turns a cleanup task into a full blown incident. We know we shouldn't, but we do it anyway. It's sleepless night/s, it's short term thinking, don't do it. Your future-self will thank you.
Your audit will be your truth - for now.
The payoff isn't just a smaller account. It's a real answer to a question every admin eventually gets asked: what's actually running in here. Right now, for most instances, that answer starts with "I think" instead of "here's the list."
We'd all rather have a list.
Related guides
- You inherited a NetSuite instance. Here's how to document it.
- Diagnosing NetSuite script and integration failures
- SuiteScript deprecation: the NetSuite timeline every admin needs
See what's actually running.
Turbobase inventories every script, workflow, and saved search in your NetSuite environment and flags what's actually executing versus what's just sitting there. You decide what to deprecate; it just does the count.
Frequently asked questions
How do I find unused scripts in NetSuite?
Check the Script Execution Log and Scheduled Script Status for actual recent runs rather than relying on deployment status. A script that is deployed but hasn't executed in the log's retention window is a real candidate, not a script that simply looks old.
Is it safe to delete a saved search nobody seems to use?
Not until you've checked what references it. A saved search can feed a dashboard, a scheduled email, a KPI, or a formula field in another record, none of which are obvious from the search itself. Check dependencies before deleting, and deprecate before you delete.
What counts as NetSuite technical debt?
Anything customized, deployed, or configured that nobody currently understands or maintains: scripts with no recent activity, workflows that duplicate a native feature, saved searches with no known consumer, and custom fields nobody remembers the purpose of. It costs nothing to keep and everything to touch.
Should I delete unused customizations or just leave them alone?
Deprecate before you delete. Disable a script or inactivate a saved search and watch for a period before removing it outright. That gives you a reversible step instead of a one-way one, and it's the difference between a controlled cleanup and an incident.