How do you prepare your NetSuite environment for NetSuite Next?

Preparing for NetSuite Next

NetSuite Next is being made available to existing NetSuite customers in phases. According to Oracle, you do not need to implement it from scratch. You continue working in the same NetSuite environment, with the same data, roles, permissions, workflows and customizations.

That is why proper preparation matters. NetSuite Next does not start with a clean slate. The quality of your current setup carries over, including historical choices that once made sense but may no longer fit the way you work today.

Our perspective: Do not prepare for NetSuite Next as a technical migration project. Treat it as a focused improvement of the processes, roles and data that you want AI to support. Not everything has to be perfect. But you should know what your reliability, controls and daily operations depend on.

Want to understand the bigger picture first? Read what NetSuite Next changes for current NetSuite users.

Start with processes, roles and decisions

The best preparation does not start with a long cleanup list or a broad inventory of your entire NetSuite environment. First, choose a few processes where NetSuite Next needs to deliver real value. Which processes do you want to make smarter, faster or easier to explain? Think of month-end close, order-to-cash, inventory management, project oversight, procurement, customer service or management reporting.

For each process, map three things: which questions users ask today, which decisions they make based on the answers and which roles need access to the underlying information. Only then does it become clear which data, customizations, roles and navigation actually need attention.

This makes your preparation much more concrete. A controller investigating margin differences needs different information, definitions and controls than a customer service employee looking for customer context. An operations manager trying to understand inventory exceptions relies on different data, workflows and roles again.

For Cadran, this is the foundation of a sensible NetSuite Next approach: small enough to test properly, but concrete enough to learn something about the setup of your entire environment.

Check the foundation

Once you know which processes and roles matter most, assess the four areas on which NetSuite Next and Ask Oracle directly rely: data, customizations and process logic, roles and governance, and user experience and adoption.

1. Data: can AI rely on the information in NetSuite?

AI works with the data available in NetSuite. If customer data is duplicated, item data is incomplete or classifications are used inconsistently, this can directly affect reporting, analysis and AI-generated answers.

Start with the data used in the processes you have selected. For Finance, this might include entities, periods, dimensions, transaction statuses and reporting definitions. For Operations, it is more likely to involve items, locations, vendors, inventory statuses and delivery agreements. For customer service, customer records, open orders, cases and activities play a larger role.

Do not look only at missing or duplicate records. Look at definitions as well. Do users know exactly what a status means? Is it clear which saved search is the trusted source for a KPI? Does a custom field have a functional owner? This layer of meaning becomes even more important when users start asking questions in natural language.

AI descriptions for custom records and fields can help NetSuite AI functionality understand what a custom object is for, how it is used and what data it contains. A good description is a concise business explanation of the object’s meaning.

2. Customizations and processes: which logic still helps, and which creates unnecessary complexity?

Many NetSuite environments have grown along with the organization over the years. Scripts, workflows, custom fields, custom records and exceptions often had a good reason for being created. The question is not whether customizations are old, but whether they are still clear, maintainable and relevant to the process you want to test.

According to Oracle, scripts, custom records, workflows and other extensions are expected to continue working in NetSuite Next. However, client scripts, custom forms and portlet scripts that directly affect the HTML or page structure deserve additional attention. This makes UI-dependent customizations a logical test category in the preview environment.

Focus especially on customizations that affect transactions, approvals, reporting, integrations or roles. Look for duplicate automation, workflows that support an outdated process, custom fields that are rarely populated and scripts whose workings are known only to one administrator.

The goal is not to remove customizations by default. Good customizations support processes that differentiate your business. Preparation is about distinguishing between customizations that add value and complexity that mainly creates risk, maintenance or uncertainty.

Include integrations in this assessment as well. NetSuite Next does not automatically change the arrangements with webshops, warehouses, banks, middleware or other business systems. If mappings depend on custom fields without an owner, or if the same business rule is recorded both in NetSuite and middleware, that dependency remains.

3. Roles and governance: do users have the right context and boundaries?

In NetSuite Next, roles and permissions continue to determine what users can see and do. Ask Oracle works within that existing permission structure. This matters for trust and control, but it also means that outdated roles, temporary access or differences between comparable roles continue to have an impact.

Assess roles from the perspective of the processes you selected. Which users need access? What information are they allowed to see? Which actions may they prepare or execute? And which approvals, segregation-of-duties controls or checks must remain in place?

Oracle makes access to NetSuite Next and Ask Oracle role-based. This enables a phased introduction, but only if the underlying roles are logically configured. A pilot with roles that are too broad teaches you little about controlled use. A pilot with roles that are too limited produces incomplete answers and frustration.

For CIOs, IT managers and application administrators, this is an important governance issue. Conversational AI makes authorizations more visible to the business. A role determines not only which screens someone sees, but also which answers, insights and actions an AI assistant can offer.

4. User experience and adoption: can users ask good questions and assess answers?

NetSuite Next also changes how users work with NetSuite. Where people often start with menus, saved searches or dashboards today, it will become more normal to ask a question in natural language. That requires a different skill: formulating a good business question.

A useful question usually includes an outcome, scope, period, metric, comparison and desired format. Not: ‘How is our margin performing?’ Instead: ‘Explain the three biggest causes of the decline in gross margin for the Netherlands subsidiary in August 2026 compared with July 2026, using our standard definition.’

Users also need to learn when an AI answer provides sufficient direction and when validation is required. Check the period, definition, population and source used. Compare important conclusions with trusted reports or underlying transactions. AI can shorten the route to insight, but it does not take responsibility away from the user.

At the same time, review Role Centers, dashboards, links, saved searches and navigation. A cleaner user experience helps today already. That same clarity will also help Ask Oracle and other AI functionality provide more relevant context and actions in the future.

Test selected processes in the preview environment

When your account is eligible, an administrator can request preview access through the NetSuite Next start page. Oracle describes the preview environment as a copy of your production account in a separate environment, including data, workflows and customizations. Using it does not affect your production environment. A preview account is available for 30 days.

Do not use the preview as a demo environment where everyone clicks around without a clear purpose. Use it as a test environment for the processes and roles you selected earlier.

For each process, define what you want to learn. Can a user find the right customer, order or project information? Is a margin or inventory variance explained using the correct period and definition? Do approval controls and segregation of duties remain intact? Does UI-dependent customization work as expected? Are integrations and important saved searches still understandable in the new experience?

Preferably test with different roles. Have users ask the same question from their own role and compare the results. This shows not only whether Ask Oracle provides useful answers, but also whether roles, permissions and context align with real responsibilities.

Keep the test practical. Record the current way of working, the desired outcome, the source used for validation, the finding and the owner of any follow-up action. This turns the preview into evidence for your roadmap rather than a general impression.

Build a workable roadmap

After the assessment and preview test, you will probably have a mixed list. Some points require action before you start a pilot. Others are useful but not urgent. And some do not need to be changed at all.

Make three clear choices.

1. Before the pilot: improvements that directly affect reliability, access, controls or user trust. Think of critical master data, roles that are too broad, unclear approval routing, UI-dependent scripts in a selected process or custom fields whose meaning no one can explain anymore.
2. On the roadmap: improvements that create value but are not needed for the first controlled rollout. Think of broader data quality actions, rationalizing old saved searches, modernizing stable but difficult-to-maintain customizations or further refining integration documentation.
3. Keep deliberately: components that look old but still serve a clear purpose. Some customizations support unique processes. Some saved searches remain the best basis for control and reporting. Not every historical record needs to be cleaned up if it has no impact on current processes, decisions or AI use.

This three-way distinction keeps your preparation manageable. You avoid a large cleanup program without a clear return, while also preventing historical choices from quietly carrying over and weakening the AI experience, reporting or governance.

Finish with a readiness checklist

Use this readiness checklist to make your preparation concrete. For each selected process, record what needs attention in data, customizations, roles, governance, user experience and preview testing. This creates a practical list of actions, decisions and points you deliberately leave as they are. Use these six questions for each selected process:

1. Processes and roles

What do you want to use NetSuite Next for first, and which roles are involved?
Look at the questions users ask today, the decisions they make and the actions they perform in NetSuite.

2. Data and definitions

Is the information this process relies on reliable enough?
Think of master data, transaction data, classifications, reporting definitions and AI descriptions for custom records and fields.

NetSuite Next makes AI a more natural part of daily work. Learn how Ask Oracle uses your NetSuite data and permissions.

3. Customizations, workflows and integrations

Which custom components determine how this process works?
Review scripts, workflows, custom forms, portlets, custom records and integrations. Pay particular attention to components that depend on the user interface or are insufficiently documented.

4. Roles, permissions and governance

Does access match the user’s responsibilities?
Check whether roles still align with current tasks, whether temporary access has been removed and whether approval controls, segregation of duties and validation steps are clear.

5. User experience and adoption

Will users be able to ask good questions and assess answers?
Review Role Centers, navigation, saved searches and dashboards. Also define when an AI answer is sufficient and when validation against a trusted source remains necessary.

6. Preview and prioritization

What will you learn in the preview environment, and what will you do with those findings?
Determine which points need to be resolved before the pilot, which belong on the roadmap and which components you will deliberately keep.

Want to know where your organization stands? Use this NetSuite Next Readiness Checklist to assess your current environment against these questions. This gives you a quick view of what needs attention, what is already strong enough and where Cadran can help make the preparation practical.