What "Clean" Actually Means
A clean instance has these characteristics: roles are built around job functions (not copied from Administrator), scripts have descriptions and owners, saved searches follow a naming convention, custom fields are documented, and there is a clear process for making changes. Most NetSuite environments drift away from this over time. New hires get cloned roles. Scripts get deployed without documentation. Saved searches multiply without anyone knowing which ones are still in use.
The Admin Checklist
Here is what we look at when evaluating whether an instance is well-maintained:
Roles & Permissions
No users on Administrator or Full Access roles (except one emergency account)
Custom roles named by function (AP Clerk, Revenue Accountant, Sales Rep), not by person
Quarterly access reviews with documented sign-off
Terminated employees deactivated within 24 hours
Two-factor authentication enabled for all users
Scripts & Workflows
Every script has a description field filled in (what it does, when it runs, who owns it)
No scripts deployed to production without testing in Sandbox first
Inactive scripts and workflows are documented and scheduled for removal
Script governance usage is monitored (no scripts consuming excessive units)
Error logs are reviewed weekly, not just when something breaks
Saved Searches & Reports
Naming convention in place (e.g., "FIN - AR Aging by Customer" or "OPS - Open POs by Vendor")
Searches used in scripts or integrations are clearly marked and never edited without testing
Public searches are limited to those that serve a team, not personal one-offs
Dashboard portlets reference maintained searches, not ad-hoc queries
Custom Records & Fields
Custom fields have help text explaining their purpose
Unused custom fields are hidden or removed (not just left on forms)
Custom records have documented relationships to standard records
Field IDs follow a consistent prefix convention (e.g., custbody_ss_ for SixStrong fields)
The Monthly Admin Routine
A clean instance stays clean through routine maintenance. Here is what a monthly admin cadence looks like:
Review Script Execution Logs
Check for recurring errors, governance warnings, and scripts that are running but no longer needed.
Audit User Access
Cross-reference active NetSuite users against your HR system. Deactivate anyone who has left. Flag role changes that were not formally requested.
Review Integration Health
Check integration error logs, token expiration dates, and data sync status. Fix issues before they become data integrity problems.
Clean Up Saved Searches
Archive searches that are no longer used. Rename any that do not follow the naming convention. Document any new searches added that month.
Why This Matters
A messy instance is not just an annoyance. It creates real business risk. Users cannot find what they need, so they build workarounds. Scripts conflict with each other because nobody knows what is deployed. Auditors flag access issues that could have been prevented with a 30-minute monthly review. The cost of cleanup compounds over time. The longer you wait, the more expensive it gets.
How We Keep Instances Clean
Administration is not a one-time cleanup. It is an ongoing discipline. Through StrongSupport, we provide continuous admin oversight: monitoring script logs, reviewing access changes, maintaining documentation, and flagging drift before it becomes technical debt.
Our team brings full-stack NetSuite expertise. We understand how a role change affects downstream workflows, how a saved search modification impacts a scheduled script, and how a custom field addition interacts with existing integrations. This cross-functional knowledge prevents the kind of isolated fixes that create new problems.
Everything is organized and accessible. Your documentation lives in a shared system. Your change log is always current. Your team can see exactly what has been done, what is pending, and what is planned. No black boxes.
If your instance has drifted, it is not too late. A structured cleanup takes 2-4 weeks depending on complexity. The result is a system your team can actually maintain going forward.
Or email us directly at hello@sixstrong.io
