Unlimited Sandbox Refreshes in NetSu...

TL;DR Opening

Starting in NetSuite 2026.1, sandbox refreshes are no longer subject to previous limits, allowing users to refresh their sandbox accounts an unlimited number of times. This change significantly improves testing and development flexibility for administrators and developers.

What's New

Effective March 6, 2026, NetSuite has lifted the restrictions on sandbox refresh requests. Users can now refresh a sandbox account as needed, without previously imposed limitations. This update is crucial for teams that rely on sandbox environments for testing new configurations, data, or customizations because it provides greater agility and less downtime.

Sandbox Refresh Explained

A sandbox refresh involves copying a snapshot of a production account into a sandbox account. This includes:

Configurations: All custom settings and features configured in the production account.
Data: Current records, which can include financial information, customer data, etc.
User Passwords: Ensuring that user access in the sandbox corresponds to the production settings.
Customizations: Any scripts or workflow customizations that have been implemented in the production environment.

How to Request a Sandbox Refresh

Administrators can request a sandbox refresh by navigating to Setup > Company > Sandbox Accounts in the NetSuite application. Here are the main steps:

Select the Sandbox: Choose which sandbox account you wish to refresh.
User Access: Specify user access for the sandbox post-refresh. Choose from:
- Only Administrators
- All Existing Production Users (excluding Customer Center users)
Select Source Account: Choose which production account will supply the data for the refresh.
- For Premium or higher service tiers, you can select different source accounts; Standard users will always use the production account.
Execute the Refresh: Click on the Refresh Sandbox button to initiate the process.

Important Considerations

Scheduled Upgrades: Avoid requesting a refresh during the scheduled upgrade period for new NetSuite releases. If a refresh does not complete before an upgrade begins, the request will fail.
Monitor Status: Check the Refresh Status and estimated completion time on the Sandbox Accounts page while the refresh is in progress.
Multiple Refreshes: With no limits now, users can request additional refreshes as needed without impacting productivity.

Who This Affects

The removal of sandbox refresh limits impacts:

Administrators: Who manage sandbox accounts and need frequent updates.
Developers: Testing new features or changes in a safe environment.
Project Managers: Overseeing rollouts and ensuring testing coverage.

Key Takeaways

Unlimited Refreshes: NetSuite allows unlimited sandbox refreshes starting with version 2026.1.
Request Process: Admins can request refreshes easily through the interface.
Stay Updated: Monitor scheduled upgrades to avoid timing issues with refresh requests.
Increased Flexibility: This update greatly benefits agile development and testing workflows.

Frequently Asked Questions (4)

Do I need special permissions to request a sandbox refresh in NetSuite 2026.1?

To request a sandbox refresh in NetSuite 2026.1, you need to have administrative access within the system.

Can I choose a different source account for a sandbox refresh if I have a Standard service tier?

No, users with a Standard service tier must use the production account as the source for a sandbox refresh. Only Premium or higher service tiers allow selecting different source accounts.

Are there any restrictions on refreshing sandboxes during NetSuite upgrades?

Yes, avoid requesting a sandbox refresh during scheduled upgrade periods, as requests not completed before the upgrade may fail.

How does the sandbox refresh process handle user access configurations?

During a sandbox refresh, you can specify user access by choosing between allowing only administrators or all existing production users (excluding Customer Center users) to access the sandbox account.

Unlimited Sandbox Refreshes in NetSuite 2026.1