What technical debt and historical decisions are you bringing with you to NetSuite Next?

What technical debt and historical decisions are you bringing with you to NetSuite Next?

Oracle explicitly presents NetSuite Next as something other than a reimplementation. Your existing data, roles, permissions, workflows and customizations carry over. Oracle also does not expect changes to most scripts.

That is precisely the strength of NetSuite Next. But it is also where organizations need to pay attention: you are carrying over not only your setup, but also the choices that have accumulated in it over the years.

The setup that has developed over the past few years will also form the basis for Ask Oracle and other AI functionality. Old process logic, broad access rights and unclear custom records do not disappear during the transition. In fact, they will have even more influence on what users can find, understand and execute.

Our view: NetSuite Next is not a technical migration project. It is, however, a good moment to take another look at the complexity that has built up over the years.

For CIOs, IT managers and ERP managers, this creates an important responsibility. Fortunately, you do not have to defend a major replacement project. You do need to explain which parts of the current NetSuite environment could stand in the way of using NetSuite Next reliably.

Technical debt is not the same as old technology

When people think of technical debt, they often think of outdated code. In NetSuite, complexity is usually spread more broadly. It can also hide in two workflows controlling the same process, an integration that depends on a single custom field, or a role that has accumulated more and more permissions over the years.

Many of those choices were perfectly logical at the time. The business changed, a department needed something quickly, or NetSuite did not yet offer a suitable standard solution. There is no point in assigning blame afterwards.

You should still be honest about which solutions continue to add value. Some changes support a process that remains distinctive. Others stayed in place because nobody knew exactly what would happen if they were removed.

A customization deserves attention when it:

  • supports a process that now works differently
  • performs the same task as another workflow, script or standard function
  • is difficult to change or test
  • depends on the knowledge of a single administrator or supplier
  • relies on fields, statuses or roles whose meaning is no longer clear
  • adds little value but affects reports, integrations or authorizations

This is not an argument for removing as much customization as possible. Good customization supports the processes that distinguish your business. The maintenance burden mainly comes from changes that have lost their original purpose or whose operation can no longer be reconstructed properly.

Which parts of your NetSuite setup could cause surprises?

A complete inventory can quickly produce hundreds of scripts, workflows, fields and roles. Such a list says little about actual priority. First look at the impact on current processes, decision-making and future AI applications.

Which management areas deserve attention?

Use these signals to decide what to keep, improve or test in a focused way.

Assessment of NetSuite management areas and possible next decisions
Area Signal that requires assessment Decision to make
Scripts and workflows Process logic is spread across the setup or is no longer well understood. Keep, simplify, replace or phase out.
Overlapping automation Multiple solutions change the same transaction, status or approval. Assign one clear owner for the process logic.
Custom logic Customization does what NetSuite now supports as standard. Weigh maintenance costs against replacement with standard functionality.
Client scripts, forms and portlets Operation depends on HTML, page order or screen structure. Test selectively in the NetSuite Next preview.
Integrations Connections rely on custom fields, fixed values or implicit process agreements. Document dependencies and assess error handling.
Custom fields and records Meaning, usage or ownership is unclear. Clean up, document and add AI descriptions.
Roles and permissions Permissions have grown historically or differ without a clear reason. Re-align access with current responsibilities.
Scripts and workflows
Signaal Process logic is spread across the setup or is no longer well understood.
Beslissing Keep, simplify, replace or phase out.
Overlapping automation
Signaal Multiple solutions change the same transaction, status or approval.
Beslissing Assign one clear owner for the process logic.
Custom logic
Signaal Customization does what NetSuite now supports as standard.
Beslissing Weigh maintenance costs against replacement with standard functionality.
Client scripts, forms and portlets
Signaal Operation depends on HTML, page order or screen structure.
Beslissing Test selectively in the NetSuite Next preview.
Integrations
Signaal Connections rely on custom fields, fixed values or implicit process agreements.
Beslissing Document dependencies and assess error handling.
Custom fields and records
Signaal Meaning, usage or ownership is unclear.
Beslissing Clean up, document and add AI descriptions.
Roles and permissions
Signaal Permissions have grown historically or differ without a clear reason.
Beslissing Re-align access with current responsibilities.

Our view: assess management issues by their current impact, not their age. Not every customization needs to disappear, but every unclear dependency deserves a conscious decision.

This assessment does not have to become a major improvement program. Some choices may still prove sensible. Others may belong on the roadmap, but not necessarily before the first preview. The key is to weigh complexity consciously instead of carrying it forward unnoticed.

Start with the process logic behind scripts and workflows

A SuiteScript version number tells only part of the story. A technically modern script can still support an outdated process. Conversely, an older script can function reliably for years and pose little risk.

Start with the business process. Map which automation affects transactions, approvals, inventory, invoicing and financial processing. Then look at where scripts and workflows intersect. Logic can accumulate unnoticed, especially around statuses, field values and approval routing.

Overlapping automation makes changes expensive. A local change that seems simple can affect a workflow, saved search or integration elsewhere. Testing effort grows while fewer people understand the full chain.

SuiteScript modernization should mainly be prioritized when a script requires active maintenance, affects an important process or blocks further development. Rewriting code simply because it is old rarely adds much value. A stronger case looks at what the script does for the business today, the risk it creates and how maintainable it is.

UI-dependent customizations require focused attention

Oracle expects scripts, custom records, workflows and other extensions to continue working in NetSuite Next. In its own FAQ, Oracle makes one relevant qualification: client scripts, customized forms and portlet scripts that directly affect HTML or page structure may require changes.

That makes UI-dependent customization a logical testing category. Think of scripts that show or hide fields based on screen behavior, custom forms with extensive client-side logic, and portlets that build parts of the interface themselves.

Server-side automation without a dependency on the user interface generally carries less risk. A functional check is still sensible when the automation affects a business-critical process.

A stable integration is not automatically maintainable

NetSuite Next does not automatically change the contracts with webshops, warehouses, banks or other business systems. Existing integrations remain part of the same NetSuite environment, along with their historical dependencies.

An integration can be technically stable and still be difficult to maintain. This happens, for example, when mappings rely on custom values without an owner, error messages do not show where a transaction is stuck, or the same business rule is recorded in both NetSuite and middleware.

Four questions are useful when preparing for NetSuite Next:

  • Is it clear which NetSuite records, fields and statuses the integration uses?
  • Do we know where validation and business logic are executed?
  • Can administrators trace errors without help from the original developer?
  • Can we test the integration in a controlled way without disrupting daily operations?

An integration that is manageable on these points may require no further action. When dependencies are unclear, documentation is often the first worthwhile investment.

AI only works with meaning you have defined

Custom fields and custom records make NetSuite fit the organization. After a few years, however, a second data model can emerge alongside the standard setup. Fields receive similar names, definitions change and objects remain after the related process has disappeared.

Ask Oracle uses the data and setup of the existing account to provide answers, insights and actions. Oracle therefore recommends completing AI descriptions for custom object definitions. Such a description records what a custom record or field is for and makes the context clearer for users and Ask Oracle.

A useful AI description contains at least the object’s functional meaning and the context in which employees use it. A technical name or repetition of the field label is rarely helpful.

At the same time, check whether the object still has a current purpose. Pay particular attention to custom fields and records that:

  • are used in reports, workflows or integrations;
  • are decisive for financial or operational decisions;
  • have multiple possible interpretations;
  • are rarely populated even though processes rely on them;
  • have no clear functional owner.

Descriptions do not repair a flawed data model. They do force a useful question: can we still clearly explain what this field or record is for?

Roles and permissions determine what Ask Oracle can see

Oracle states that Ask Oracle works within existing roles and permissions. The AI assistant can only use data and support actions for which the logged-in user is authorized.

Authorizations therefore become part of the quality of the Ask Oracle experience. Excessive rights increase the risk that users can request information that does not belong to their role. Roles that are too restrictive or inconsistent produce incomplete answers and can undermine trust in Ask Oracle.

A role review does not have to start with every individual permission. First compare roles with current responsibilities. Then check differences between similar functions, temporary access and permissions around sensitive data or approvals.

Involve process owners in this assessment. IT can establish which rights have been granted technically. The business must decide whether that access still fits the role.

Do not test everything. Test where old choices could cause problems

Oracle provides a NetSuite Next preview account as a separate copy of the production environment. It also contains the existing data, workflows and customizations. According to the current documentation, the preview lasts thirty days and has no effect on production.

Do not use that period to check off the entire environment again. A preview is too short for that and it rarely produces the best insights. The value lies in focused tests: processes where customizations, roles, integrations and user actions come together.

High testing priority

Test processes where customization, user interaction and business impact come together:

  • business-critical transaction chains such as order-to-cash, procure-to-pay and record-to-report;
  • client scripts, custom forms and portlets that depend on the interface;
  • workflows and scripts that affect the same records or statuses;
  • important integrations and their error handling;
  • roles with access to sensitive data or approval authority;
  • custom records and fields that Ask Oracle must interpret correctly.

Have these tests performed by users who know the process day to day. They recognize deviations that are not visible in technical documentation.

Lower testing priority

Standard functionality without customization or special authorizations usually does not require extensive regression testing. The same applies to areas that are rarely used and have no impact on current processes, reports or compliance.

That does not mean ignoring them. A brief check may be enough. Available testing time should mainly go to processes where an error would have immediate operational, financial or legal consequences.

Translate technical debt into risk, cost and speed of change

“Cleaning up technical debt” rarely wins internally against projects with visible revenue, cost savings or customer value, especially while NetSuite continues to run.

The business case becomes stronger when you take the subject out of purely technical terms. Not: we want to clean up scripts. Rather: we want to know which old dependencies will affect reports, process changes, authorizations and AI use.

From technical issue to business impact

Technical debt can directly affect costs, risks and decision-making.

Technical topics and their meaning for management and the business
Technical topic Meaning for management or the business
Unclear scripts and workflows Changes take longer and create process risks that are difficult to predict.
Duplicate automation The organization pays to maintain logic that can contradict itself.
Poorly described custom data Reports and AI answers are harder to assess and explain.
Historically accumulated permissions New AI functionality operates on access that may no longer be appropriate.
Fragile integrations Changes to processes, channels or partners become more expensive and slower.
Missing testing priorities Time is spent on broad checks while critical exceptions receive too little attention.
Unclear scripts and workflows
Betekenis Changes take longer and create process risks that are difficult to predict.
Duplicate automation
Betekenis The organization pays to maintain logic that can contradict itself.
Poorly described custom data
Betekenis Reports and AI answers are harder to assess and explain.
Historically accumulated permissions
Betekenis New AI functionality operates on access that may no longer be appropriate.
Fragile integrations
Betekenis Changes to processes, channels or partners become more expensive and slower.
Missing testing priorities
Betekenis Time is spent on broad checks while critical exceptions receive too little attention.

Not every technical issue requires immediate replacement. The first step is to determine which areas affect reliability, cost, control and future AI applications.

This makes technical debt a business topic. You do not need to discuss every workflow or custom field at management level, but remember that the consequences end up there: changes that take longer, reports that prompt debate, integrations that are difficult to adapt and AI answers that are only reliable when the underlying setup is sound.

NetSuite Next is therefore not a license for a general cleanup. It is a good moment to revisit a few choices. Which dependencies do we consciously accept? Which parts of the setup slow down change? And which processes do we want to rely on when the underlying data, roles or logic have not yet been sufficiently validated?

Want clarity on what needs attention before NetSuite Next?

First identify what really deserves attention

A workable first step is a focused review of the current environment. Combine technical information with conversations with administrators, key users and process owners. This reveals which components formally exist, which are used every day and where employees have developed workarounds.

The outcome should support decision-making. For each relevant point, you want to know:

  1. Which business process is affected?
  2. What happens if we change nothing?
  3. Does this need to be addressed before broader use of NetSuite Next?
  4. Is the improvement technical maintenance, functional redesign or a governance decision?
  5. Who can set the priority and budget?

There are usually three possible outcomes. The environment requires little preparation, a few focused improvements are sufficient, or the accumulated complexity justifies a broader optimization program. The first outcome is valuable too: the organization can move forward with confidence without launching a project that adds little value.

Keep what still adds value

NetSuite Next builds on the setup you use today. That is positive when processes, data and authorizations are well managed. In an environment with many historical exceptions, the same continuity requires a conscious choice.

Not everything needs to be resolved before NetSuite Next. Some complexity still has functional value. Some improvements belong on a roadmap. And some old choices should no longer determine how reliable reports, integrations or AI answers feel to users.

Marcel van Es accountmanager netsuite

Marcel van Es

Commercial Manager NetSuite