When a new admin inherits a NetSuite account, old customizations can be difficult to understand. Fields, forms, custom records, workflows, and scripts may have been created by different people over time, and not all of them may still be needed.
A structured review can help the new admin understand what exists, what is still being used, and what may need cleanup.
Scenario
A new administrator takes over an existing NetSuite account.
The account includes many older customizations, such as:
- custom fields
- custom forms
- custom records
- workflows
- scripts
- saved searches
Some customizations may still support active business processes, while others may be outdated, duplicated, or undocumented.
Solution
Start with an inventory review before making changes.
The goal is not to delete old customizations immediately. The first goal is to understand what each customization does, where it is used, and whether it is still needed.
What to Review
Custom Fields
Review custom fields to understand:
- where they appear
- whether they are still populated
- whether they are used in reports or searches
- whether they duplicate another field
- whether the label and purpose are clear
Fields with unclear names or no recent usage may need further review.
Custom Forms
Review custom forms to confirm:
- which roles use them
- whether the layout is still useful
- whether important fields are hidden
- whether old or duplicate forms exist
- whether users are still assigned to the correct form
Forms often become outdated when processes change.
Custom Records
Review custom records to understand:
- what business process they support
- which fields belong to the record
- whether users still create or update records
- whether records are connected to scripts, workflows, or searches
- whether permissions are still appropriate
Custom records should have a clear owner and purpose.
Scripts and Workflows
Review scripts and workflows carefully before changing anything.
Check:
- what record type they run on
- when they trigger
- what fields they update
- whether they are still active
- whether errors appear in logs
- whether the business process still needs them
Scripts and workflows may affect data behind the scenes, so they should not be disabled without testing.
Suggested Review Approach
Begin with documentation.
Create a simple tracking list with:
- customization name
- type
- owner or requesting team
- record type
- business purpose
- active or inactive status
- notes or next action
Then group findings into categories:
- keep
- update
- replace
- investigate
- retire later
This helps avoid accidental removal of customizations that are still important.
References
- SA: SuiteBuilder – Customization (ID: 1045873)
- SA: SuiteCloud (ID: 1014757)
Notes
- Do not delete old customizations without confirming usage.
- Check saved searches, reports, workflows, and scripts before changing fields.
- Review inactive customizations separately before cleanup.
- Use sandbox to test changes before production.
- Talk to business users before removing anything.
- Document what you learn during the review.
- Prioritize risky or confusing customizations first.
Summary
When a new admin inherits old NetSuite customizations, the safest approach is to review before changing. By inventorying fields, forms, records, scripts, and workflows, admins can understand what still matters and what may need cleanup.
A careful review helps reduce risk, improve maintainability, and make future administration easier.
Share your insights and experiences in the NetSuite Admin Corner.