NetSuite Next Preview Account: Copied Data, Access, and 30-Day Evaluation

A NetSuite Next Preview Account lets you evaluate a separate snapshot of production data, workflows, and customizations in the new NetSuite Next experience without affecting your production account. Roles, permissions, and access restrictions are copied too. Access lasts 30 days after setup, so administrators should organize reviewers and critical tasks around that window.

Key takeaways

The preview includes a production snapshot and copied user access.
Production users initially have the same access in the preview; access can be added or removed after setup.
Access lasts 30 days after setup. Another preview can be requested at any time through the Choose how to get started with NetSuite Next banner.
Do not assume continuous synchronization or continuity between successive previews.
Preview-account guidance may not apply to accounts already set up for NetSuite Next.

What does a NetSuite Next Preview Account copy from production?

The preview is a separate copy of your production account using the new NetSuite Next experience. It includes a snapshot of your data, workflows, and customizations, allowing reviewers to assess familiar work rather than evaluate an interface with unrelated sample data.

The copied scope also includes the access settings that shape what users can evaluate:

Copied component	What it contributes to the evaluation
Data	A production snapshot for assessing familiar work
Workflows	Production workflows to include in representative task reviews
Customizations	Existing customizations to assess in the NetSuite Next experience
Roles	The role context users initially bring from production
Permissions	The production permissions copied into the preview
Access restrictions	The production restrictions copied alongside roles and permissions

Select test cases that connect a business task, its workflow, and any relevant customization. Asking someone to “try NetSuite Next” leaves the scope unclear. A stronger assignment identifies a familiar task, the role used, and the expected business outcome.

For example, an administrator might ask a finance reviewer to evaluate a routine task that depends on a familiar workflow and customization. The reviewer should record what they attempted, what they observed, and any questions that need follow-up. This is an evaluation method, not a promise that every customization will behave identically in the new experience.

A snapshot is not a synchronization promise

Do not make a recently changed production record or workflow a prerequisite for testing until you have confirmed that it is represented in the copy. The available guidance does not establish snapshot timing or refresh behavior. A production change should therefore not be assumed to appear automatically in the preview.

Distinguish between two kinds of findings:

Missing test inputs: The expected example was not available in the snapshot.
Observed task behavior: The reviewer had the necessary inputs but encountered a different result or experience.

The first finding concerns whether the test was ready to run. The second concerns what happened during evaluation. Keeping them separate prevents an incomplete test from being presented as evidence about the new experience.

This article concerns the NetSuite Next preview, not standard sandbox or Release Preview procedures. If you are comparing environments, keep deployment to a NetSuite sandbox separate from this preview's purpose: evaluating a production snapshot in the NetSuite Next experience. Preview-account guidance may not apply to accounts already set up for NetSuite Next.

Who can access the preview initially?

Production access restrictions, roles, and permissions are copied into the preview. Production users therefore initially have the same access in the preview as they have in production. Do not plan participation on the assumption that only the administrator starts with access.

Instead, compare the copied access with the intended review group. Work with stakeholders to decide whether participation should happen all at once or be phased by role. Access can be added or removed after setup to support that decision.

Copied roles and permissions also provide context for interpreting feedback. Ask reviewers to identify the role used for each task. An administrator's observation and a business user's observation may reflect different access contexts; record those contexts rather than treating the reports as interchangeable.

A practical assignment should include:

The reviewer and the role they will use.
A familiar task available to that reviewer.
The workflow or customization being assessed.
The expected business outcome.
A place to record observations and questions.

Keep restrictions in view as well as permissions. If a reviewer cannot perform the intended task, first establish whether the assignment matches their copied access before interpreting the result as an issue with the NetSuite Next experience.

Administrators familiar with sandbox account access preferences should not assume those environment-specific procedures apply here. The supported preview rule is that production access is copied initially and can be adjusted after setup.

How should administrators plan access changes?

After setup, you can add or remove access as needed. That supports either a focused group of representative reviewers or broader participation. It does not change the initial-copy rule: copied production access is the starting point, while subsequent adjustments are a separate administrative decision.

Use the following planning checklist. It is not a sequence of NetSuite account screens or configuration steps:

Identify the review group. Choose stakeholders who can assess critical workflows and relevant customizations from their normal business perspective.
Compare intended participation with copied access. Establish which reviewers have the access needed for their assignments and which users should not participate in the planned evaluation.
Plan access additions or removals after setup. Base those decisions on the agreed review group rather than assuming a sandbox-specific setup process applies.
Check assignments with reviewers. Ask participants to confirm that they can access the preview and attempt their assigned tasks.
Record the access context. Note whether each review occurred under the initial copied access or after an adjustment.

The last step matters when participation changes during the assessment. A reviewer list alone does not explain the circumstances of every observation. Recording the access context helps distinguish a task finding from a mismatch between the assignment and the reviewer's access.

For phased participation, start with roles that cover the most important workflows, then expand once the first group has produced usable findings. For all-at-once participation, give users a consistent reporting structure so their observations are easier to compare. Plan either approach within the same 30-day evaluation window.

Choose the approach that fits reviewer availability and the work you need assessed, rather than maximizing the number of participants. A smaller group with clear assignments may provide more actionable evidence than a broad invitation without ownership or reporting expectations.

For broader product context, NetSuite Next features and setup options can help frame the assessment. Keep that broader setup discussion distinct from the preview-access rules described here.

How long can you use a NetSuite Next Preview Account?

You can use the preview account for 30 days after setup. Organize reviewer availability and critical test cases around setup rather than treating the preview as an open-ended testing environment.

You can request a new preview account again at any time through the Choose how to get started with NetSuite Next banner. That option does not remove the need to finish and document the current assessment. The available guidance does not establish whether another preview preserves earlier test changes. Keep findings separately rather than relying on continuity between accounts.

A suggested schedule—not a product requirement—can divide the evaluation into three phases:

Suggested phase	Administrative focus	Evidence to retain
Opening days	Confirm participants, copied access, and representative examples	Reviewer list, task assignments, and initial questions
Main evaluation period	Assess critical workflows and customizations using representative roles	Task results, access context, and reproducible observations
Closing days	Clarify ambiguous reports and consolidate findings before access ends	Assessment summary, unresolved questions, and follow-up priorities

Prioritize business-critical tasks before optional exploration. Assign an owner to each important workflow so that an incomplete review becomes visible while there is still time to address it. Check reviewer availability early: an assignment is not a completed assessment.

For each finding, retain the task, role, relevant workflow or customization, expected result, observed result, and remaining question outside the preview. Separate direct observations from assumptions. For example, a report should distinguish a task the reviewer could not attempt from a task they completed with an unexpected result.

Before the window closes, consolidate findings into three groups: completed assessments, unresolved questions, and tasks that still need evaluation. This provides a clearer basis for follow-up than a collection of unstructured comments. If you request another preview, your assessment record should explain the earlier work without depending on earlier test changes remaining available.

FAQ

Does evaluating the preview affect production?

No. The preview is a separate copy of production data, workflows, and customizations. Evaluation activity does not affect your production account.

Who has access, and can participation change?

Production users initially have the same access as in production because roles, permissions, and access restrictions are copied. After setup, access can be added or removed as needed.

How long does access last, and can you request another preview?

Access lasts 30 days after setup. You can request another preview at any time through the Choose how to get started with NetSuite Next banner. Keep findings separately rather than assuming test changes will carry into another preview.