To prepare for NetSuite Next, name one owner, ask Oracle for a preview account, and test your real customizations, reports, and roles there before anyone switches over. Next runs on the same platform and the same data, so this is a testing and adoption project, not a migration. Pilot with one team, train by role, and set rules for AI use before turning on Ask Oracle for everyone.
Key Takeaways
Part of the NetSuite Next, Without the Nerves series.
Last reviewed October 5, 2026 against Oracle's published NetSuite Next documentation. NetSuite Next is changing often, so check Oracle's pages for the current state.
Most of the worry around NetSuite Next comes from treating it like an upgrade you have to survive. It is closer to a renovation of the front of the house. The foundation, the data, the records, and the workflows stay where they are. What moves around is how people get to them and what they can ask for along the way.
Oracle describes NetSuite Next as the same platform with a unified data model, now carrying Ask Oracle, embedded AI, agents, and a redesigned experience. It is not a new product, and it does not require reimplementation. Oracle's NetSuite Next FAQ also notes that transactions created in one experience show up in the other, because both read from the same account.
TVG's own NetSuite Next guide sorts the change the same way. Data, records, workflows, and business logic stay. Navigation, search, list views, and AI assistance change. That split tells you where to spend your attention.
| Area | Stays the same | Changes |
|---|---|---|
| Data and records | Customers, vendors, items, transactions, custom records | How you navigate to and search them |
| Business logic | Workflows, scripts, and customizations (expected to keep working) | Customizations that manipulate the page directly may need review |
| Access | Roles and permissions, copied from production | Access to Next can be granted by role |
| Daily experience | The account and its data | Navigation, search, list views, and Ask Oracle for AI help |
Access is phased. When your account is eligible, administrators see a banner that reads "Choose how to get started with NetSuite Next." If you have not seen it, that does not mean you missed something.
Oracle's rollout announcement said the rollout would begin with release 2026.2 in the United States and Canada, with more countries to follow, and that administrators can grant access by role. That was the picture in July, and it may have moved since. Check Oracle's current page for your country before you plan dates around it.
Pick one person, and make it someone who can say yes or no to a change. In most mid-market companies that is the NetSuite administrator, with a finance lead and an IT lead as named reviewers. The failure pattern to avoid is a project everybody is watching and nobody owns, where the preview account expires because each person assumed someone else was testing.
The owner does not need to test everything personally. They need to decide what gets tested, by whom, and by when.
Use the options administrators see when the account becomes eligible. A preview account is a snapshot copy of production, including data, workflows, and customizations. Oracle says it does not affect production, and that roles and permissions are copied across.
It lasts 30 days, and you can request a new one afterward. Thirty days sounds generous until you remember that month end close, an audit, or a holiday week can eat half of it. Schedule the testing before you request the account, not after.
Oracle expects scripts, custom records, workflows, and other customizations to keep working, and says most custom scripts will not need changes. The exception worth your time is anything that reaches into the page itself. Oracle flags client scripts, form customizations, and portlet scripts that directly manipulate HTML or page structure as candidates for review.
TVG's guide lists the same suspects: custom windows, popups, client scripts, and anything that manipulates the page structure. Make a short list of every customization your users touch daily, then rank it by how badly a broken screen would hurt. A pop-up that lets a warehouse team pick lots matters more than a dashboard portlet nobody has opened since last year.
If you do not have an inventory of what is deployed, that is the first finding, and it is useful whatever you decide about Next. A NetSuite Health Check produces exactly that snapshot of custom fields, records, scripts, workflows, and bundles.
Because roles decide what each person sees in Next, and because Ask Oracle works within a user's roles and permissions. If a role is too broad today, the AI inherits that breadth. Nothing about Next fixes a sloppy permission set; it just puts a faster tool in front of it.
While you are in the preview account, pick three or four real users across finance, operations, and sales and walk their roles. Ask what each can see, what each can change, and whether that still makes sense when anyone can type a question in plain language. Roles also feed the later question of who gets access first, since administrators can grant Next by role.
Choose one role or team to go first, ideally one that is curious and not in the middle of a deadline. Give them a short list of real tasks to complete in the new experience, such as finding a customer, entering a vendor bill, running the report they use every Monday, and asking Ask Oracle one question they already know the answer to.
That last test matters. Oracle describes a "Show explanation" button on Ask Oracle answers and says it does not browse the public internet. Checking an answer you can verify teaches people how far to trust the ones you cannot.
The mechanics of who goes first are simple. On the Manage access to NetSuite Next page, which only administrators can open, each eligible role can be set to NetSuite Next only, Optional (users can switch between the current version and Next), or No access, according to Oracle's documentation. Optional is the natural setting for a pilot, because nobody is stuck if something misbehaves.
The honest version: your data and your processes are the same, the screens look and behave differently, and here is where to report anything that feels broken. Training should follow roles rather than features. Someone in accounts payable does not need a tour of everything Next can do; they need to know where bills, approvals, and their saved searches went.
Keep the first training short and task-based, then collect questions from the pilot team to shape the broader version.
Decide, in writing, what Ask Oracle is for and who may use it. Oracle says Ask Oracle is included with your NetSuite license, and that the NetSuite AI Connector for outside assistants works alongside it. Those are two different doors into the same data, and each deserves its own decision.
A short starting policy covers three things: which roles may use Ask Oracle, whether any outside AI tool may connect, and who reviews answers that feed financial or operational decisions. The longer governance questions, including how outside AI tools connect, are worth their own read. TVG covers the controls in detail on the AI services page.
Oracle notes that accounts with an "Exit NetSuite Next" option in the profile menu can switch back, though availability varies by account. Since both experiences read the same data, nothing needs to be moved either way. Confirm whether your account shows that option during your preview, so the answer is known before the pilot starts, not during it.
I would start with how the customer actually uses NetSuite, not with NetSuite Next itself. Which roles are heavily used? Which processes are business critical? Which customizations are users dependent on, and which scripts interact with the UI? Which custom records, transaction types, fields, workflows, dashboards, saved searches, and integrations are part of everyday work?
Then I would use the preview account to run the important business processes before anyone gets broad production access. I would also use it as a chance to question old customization that should not be carried forward unquestioned: legacy workflows, overlapping automation, rarely used custom fields, and scripts that may need modernization. Established accounts pile up technical debt simply because the business changed faster than the system got cleaned up. That exercise is worth doing whether or not you ever turn Next on.
For the rollout itself, I would not start with the largest group of users. I would start with people who know their processes well enough to notice when something is not behaving as expected. That could be the NetSuite administrator and a small group of experienced users from finance or operations, with optional access first. Then I would expand by business function based on what we learned.
Training should vary by role. An occasional user needs to know how to navigate, find records, complete normal transactions, and understand what Ask Oracle can and cannot do. A finance power user needs more depth on reports, searches, analysis, close processes, and how existing workflows behave. Administrators need the deeper material on access, customizations, troubleshooting, AI capabilities, permissions, and governance. I would spend less time giving everyone a tour of every new feature and more time showing each group how the work they already do changes in Next.
No. Oracle describes NetSuite Next as the same platform with a unified data model, and says your data, roles, permissions, customizations, and workflows stay in place. Preparing is about testing the new experience and training users, not migrating or rebuilding anything.
Oracle says a preview account lasts 30 days, and you can request a new one afterward. It is a snapshot copy of production, so testing there does not affect your live data. Plan your test scenarios before you request it so the 30 days go to testing.
Oracle expects scripts, custom records, and workflows to keep working, and says most custom scripts need no changes. Client scripts, form customizations, or portlet scripts that directly manipulate HTML or page structure may need review, so test those first in a preview account.
Oracle's July announcement said the rollout begins with release 2026.2 in the United States and Canada, with more countries to follow. That may have changed, so check Oracle's current NetSuite Next pages or ask your account team before planning around a date.
Oracle says accounts with an Exit NetSuite Next option in the profile menu can switch back, though availability varies by account. Because both experiences use the same data, transactions created in one appear in the other. Check whether your account shows the option during your preview.
Oracle says Ask Oracle is included with your NetSuite license. Questions about usage limits or add on AI capacity are a different matter, and Oracle does not publish those details in the FAQ, so ask your NetSuite account team for current terms.
One accountable owner, usually the NetSuite administrator, with a finance lead and an IT lead as reviewers. The owner decides what gets tested, by whom, and by when. Without a named owner, preview accounts tend to expire before anyone finishes testing.
You can do all seven steps yourself. Where teams usually lose time is in step 3, because nobody has a clean list of what is deployed, and in step 4, because nobody has looked at roles in a while.
If you would rather start from a clear picture of your environment, TVG can review your customizations and roles before your preview window opens. Start with the NetSuite Next guide or talk to our team.
Ready to Get More From NetSuite?
Whether you are optimizing your current environment, planning your next project, or looking for a partner who does more than close tickets, our NetSuite team is ready to help.
Joseph Lang is the Director of inVESTED PRO at The Vested Group. With more than 13 years of NetSuite experience, he helps organizations maximize the value of their ERP investment through strategic guidance, operational improvements, and ongoing managed services. Joseph specializes in NetSuite optimization, manufacturing, warehouse management, inventory management, procurement, and SuiteCommerce, helping clients continuously improve their business processes and long-term ERP performance.