NetSuite Next Switching and Customization Review

NetSuite Next changes the user experience while using the same underlying account, data, roles, permissions, workflows, and customizations. Saved transactions and records are visible in both experiences. Most custom scripts do not require changes, but some HTML-dependent customizations may need review. This guidance applies only to accounts with Exit NetSuite Next in the profile menu.

Who This Affects

These switching questions apply only to accounts whose profile menu includes Exit NetSuite Next. Before using this guidance to plan testing, confirm that the option is present. For related access and exit guidance, see the NetSuite Next switching and role access guide.

Within that scope, administrators can focus validation on existing roles, permissions, and workflows. Developers can prioritize customizations that depend on page structure. Transaction users can check saved records across the two experiences. These are testing recommendations, not additional access requirements.

What Changes—and What Stays the Same?

NetSuite Next is an evolution of the existing NetSuite experience, built on the same cloud ERP. It brings together Ask Oracle, embedded AI capabilities, agents, and a redesigned user experience.

Users continue to use the same data, roles, permissions, workflows, and customizations. The practical distinction is between a changed interaction experience and a shared underlying account. For administrators, representative users checking everyday tasks offers a useful validation approach without treating the switch as a data migration. Consult the NetSuite Next role and company switching guide for related navigation guidance.

Which Customizations May Need Review?

Scripts, custom records, workflows, and other customizations are expected to continue working. Most custom scripts do not require changes. Preserve that qualification: an expectation of continuity is not a guarantee that every customization behaves identically.

Prioritize review of customizations that directly manipulate HTML or page structure, including:

• Client scripts
• Form customizations
• Portlet scripts

The review boundary is the customization's dependency on interface details—not simply whether it is custom. As a testing recommendation, exercise affected forms and portlets in both experiences and document differences before deciding whether changes are necessary. Do not infer that every client script, form customization, or portlet script needs modification.

Are Transactions Shared Between Experiences?

Yes. Transactions and all other data are stored in the same underlying account, so saved transactions and records are visible in both NetSuite and NetSuite Next.

A practical verification test is to save a representative transaction in one experience and check its visibility in the other. Keep that test focused on saved records; the source's visibility assurance does not establish behavior for unsaved changes.

Key Takeaways

• Apply this guidance only to accounts with Exit NetSuite Next in the profile menu.
• NetSuite Next combines AI capabilities and a redesigned experience with the same underlying account.
• Most custom scripts do not require changes; HTML- or page-structure-dependent customizations may need review.
• Saved transactions and records are visible in both experiences.