How to Prepare for & Adopt NetSuite Next

NetSuite Next ships in waves, region by region. Get aligned on what arrives when before you plan anything — dates shift, so anchor to official sources.

1. Review the official NetSuite Next product page and the overview video for the three pillars and the vision.
2. Read Oracle’s SuiteWorld 2025 announcement for the official scope and direction.
3. Note the cadence: Redwood is opt-in now; Ask Oracle and AI Canvas roll out through 2026, North America first.

Redwood is a per-user toggle, so you can let a few power users live in it now and surface issues early — without changing anything for everyone else.

1. Have each pilot user enable the Redwood Experience theme on the Appearance tab of Set Preferences.
2. Walk the high-traffic pages — dashboards, lists, forms — and note the sticky header, smart search, and collapsible sections.
3. Collect friction points; users can toggle back to Classic at any time during the pilot.

The Redwood UI restructures forms and navigation. Most customizations carry over, but UI-dependent ones need a look before you switch everyone.

1. Inventory custom forms, client scripts, and any UI-dependent SuiteScript on your busiest record types.
2. Enable Redwood in a sandbox and walk those records, watching for layout, field-visibility, or scripting issues.
3. Log fixes and re-test — treat this as a UI-compatibility review, not a rebuild.

Ask Oracle is only as trustworthy as the data and permissions behind it. It runs under your existing roles, so clean data and tight roles directly shape answer quality.

1. Clean the data Ask Oracle will lean on — consistent customers, items, and accounts make answers accurate.
2. Confirm least-privilege roles; the assistant respects each user’s permissions, so over-broad roles over-expose.
3. Decide who gets the assistant first, and verify answers cite their source records as expected.

Resist “AI everywhere.” The teams that win pick one or two bounded use cases, prove value, then expand.

1. Choose an AI Canvas scenario your finance or ops team already does in spreadsheets (e.g. a what-if margin model).
2. Choose one agentic workflow with clear boundaries (e.g. reconciliation assistance or a payment proposal) to trial.
3. Define what “good” looks like and compare AI output against your existing process before relying on it.

“Agents propose, you approve” is the model — but you decide where the line sits. Set that policy before agents touch real processes.

1. For each agentic workflow, decide what runs autonomously versus what requires human approval.
2. Assign owners to review the audit trail of agent actions on a regular cadence.
3. Document the policy and revisit it as capabilities mature — start conservative, widen with evidence.

Adoption beats availability. Expand team by team, with light training, once pilots prove compatibility and value.

1. Use pilot feedback to write short, role-specific guidance (how to ask Ask Oracle good questions; what changed in Redwood).
2. Expand Redwood and AI features team by team, keeping the toggle available as a safety valve.
3. Track usage and value, and plan for Redwood becoming the default (expected around 2027).