How do Application Managers prepare for NetSuite Next?

How do Application Managers prepare for NetSuite Next?

Start with the questions and issues that keep coming back. Identify which saved searches, custom fields, roles, permissions and Role Centers play a part. Link each issue to the relevant process and discuss the outcome needed with the process owner. You do not need to review your entire NetSuite environment.

‘Why does my colleague use a different report?’ ‘Why can’t I see this record?’ ‘What am I actually supposed to enter in this field?’ ‘Can you change this today?’

As an administrator, you get questions like these every week. You often know where to look: a saved search with an outdated filter, a custom field that has acquired different meanings, a role with temporary permissions that were never rolled back, or a Role Center full of old links.

The cause is usually known. Yet the solution ends up on an already full backlog. An incident takes priority, or a new integration has to go live. Meanwhile, the same questions keep coming back.

The arrival of NetSuite Next offers an opportunity to revisit that backlog. Oracle presents NetSuite Next as the next NetSuite experience, with Ask Oracle, embedded AI, agents and a redesigned user interface. It is not a reimplementation. Your existing data, roles, permissions, workflows and customizations remain part of the same environment. Most scripts do not need to change. Scripts that directly modify the user interface or page structure do deserve a focused review.

Known ambiguities therefore remain. Users will use Ask Oracle to find information, ask questions and prepare actions based on the configuration already in place. An unclear definition, inconsistent role or poorly maintained search will become more visible in day-to-day work.

Our view: use NetSuite Next to make recurring administration issues discussable. For each issue, document which process is affected, what users notice and who decides on the desired solution. That information determines the order more effectively than the age of a backlog item.

Your administration backlog is not a priority list

A backlog item such as ‘change custom field’ does not yet explain why it matters. ‘Expand role’ does not say who will gain access to which data. And ‘clean up saved search’ does not make clear which decision might be based on an inconsistent figure.

Describe administration issues in the language of the process. If four teams each use their own saved search for open sales orders, you can demonstrate the differences in filters, statuses and dates. The process owner then determines which definition applies and who maintains the report.

The same applies to access. You can show that two similar roles have different permissions. The responsible process owner assesses whether that difference is necessary, which segregation of duties applies and who may accept an exception.

Start with the question that keeps coming back

An export of every script, workflow and field mainly produces a long list. Start by collecting the questions users repeatedly ask you. If you want to take a broader look at data, customizations, governance and adoption, also read how to prepare your NetSuite environment for NetSuite Next.

Pay particular attention to questions that:

• come from different teams
• lead to individual Excel lists or manual checks
• keep ending up with the same administrator
• arise because users see different figures, statuses or definitions
• involve sensitive data, approvals or segregation of duties

These questions often point to an ambiguity in the process, the definition or the allocation of responsibilities. Four examples show how to investigate them.

‘Which report is the right one?’

Look for saved searches and reports with similar names. Check who owns them, when they were last used, which filters and statuses they apply and whether they display the same records. Note where the outcomes diverge.

Then discuss with the process owner which report supports the process, which exceptions apply and who maintains the outcome. Based on that, you can archive the search or merge it with another one.

‘Why can my colleague see this and I can’t?’

Compare the users’ roles and permissions. Check temporary access, differences in subsidiary or data security, approval authority and access to records or searches. Also determine whether the user cannot find the information or genuinely does not have access.

Have the responsible process owner confirm which access fits the role, which information should remain restricted and which approval is required. Only then update the role and test it.

‘What am I supposed to enter in this field?’

Review the values in the custom field, the teams that use it and whether the field appears in workflows, reports, integrations or filters. Look for empty fields, different spellings and fields with almost the same meaning.

The process owner documents what the field is for, when it must be completed and what the values mean. Then add a clear AI description. That description helps Ask Oracle understand a custom field or custom record more effectively.

‘Where do I click to do this every day?’

Review the user’s Role Center. Which actions, searches and reports are actually used? Which links are outdated? For which task does someone use a workaround or a separate document?

Ask users which tasks are central to their work. You can then remove old links, surface the right searches and reorganize the navigation. The Role Center will once again support the current process.

Four things to document for each issue

For each issue, document four things:

1. The user question: What is someone trying to do, and where are they getting stuck?
2. The location in NetSuite: Which saved search, custom field, role, permission, workflow or Role Center is involved?
3. The process and owner: Which process is affected and who is responsible for the outcome?
4. The decision required: Which definition, access level, working method or priority needs to be confirmed?

Then assess the impact: the number of users, the decision that depends on it and the risk if the situation remains unchanged. Does that outweigh whether the process owner can confirm the desired outcome and whether you can test the change?

This determines the technical next step. Sometimes a change is needed. In other cases, it is enough to archive a search, document a definition, remove access, improve navigation or deliberately retain a customization.

Not every item needs to be resolved before NetSuite Next is introduced. A customization that supports a distinctive process can remain in place. An old search with no users or current purpose does not need to become a project. Record why something remains and who was involved in that decision.

Use the 30-day preview

Oracle has been rolling out NetSuite Next in North America since version 2026.2. Once your account becomes eligible, an administrator can request a NetSuite Next Preview Account. This is a separate copy of the production environment with your existing data, workflows and customizations. The preview has no impact on production.

Take two or three recurring questions into the preview. Let users with different roles ask the same question and compare the outcome with the report or search they use today. When outcomes differ, investigate whether the cause lies in the data, definition, access, configuration or expectation.

Access to NetSuite Next and Ask Oracle can be managed by role. For the first tests, choose users who work with the process every day and involve the process owner in assessing the outcomes. Cadran can help make the preparation practical.