NetSuite release update testing (bi-annual)
Be ready for NetSuite’s twice-yearly upgrade. By reviewing the preview, assessing impacts, running regression tests and briefing users every cycle, your account is ready on Oracle’s date without your team losing a fortnight to it.
NetSuite upgrades on Oracle’s date, whether or not your account has been tested
Twice a year NetSuite upgrades every account, with no opt-out and no deferral. What you can control is how prepared you are. Accounts that test the preview find broken scripts and changed behaviour before the upgrade, while accounts that don’t may only find them in production. Release testing as a service means your account is prepared for each NetSuite release.
How we test each NetSuite release update
Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.
- Preview-window testingWork in the release preview account starts on the day it opens, so testing keeps pace with Oracle’s schedule and finishes ahead of your next NetSuite release date.
- Impact assessmentRelease notes are read against your account’s actual setup, with customisations, scripts and processes mapped to what is changing.
- Regression executionYour critical-process test set is run in the preview account, with the scripts executed and evidenced every cycle.
- Fixes before the dateProblems found in testing are fixed before the date, with script updates and configuration adjustments made through the change process.
- Cutover weekend managementThe production upgrade is watched and verified, with the cutover checklist run live over the weekend.
- User communicationWhat is changing, and for whom, is briefed ahead of the date on a planned communication calendar.
Down to task level – each has its own page
Next release already on your mind?
We test each release in preview against your account before it lands. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.
What handing it over buys you
Problems are found before the upgrade
Each release is tested in preview, so breaking changes are found and fixed in advance.
Your team keeps its focus
We run the cycle, so your team is briefed on what’s changing without losing days to testing.
Evidence is kept for every cycle
Records of what was tested and passed give auditors a ready change-management answer.
New features get noticed
Impact assessment picks out useful new features as well as risks, so you know what’s worth turning on.
From critical processes to a regular testing cycle
Map the critical set – we identify the processes and customisations that must keep working after each release.
Build the regression pack – repeatable test scripts are built against that set as a standing asset.
Run the first cycle – preview through cutover is run alongside your team.
Repeat each cycle – every release thereafter is triaged, tested, fixed, briefed and verified.
What to know before you hand it over
- !The upgrade and its timing are Oracle’s. Releases cannot be deferred or delayed, so the service manages your readiness rather than the date.
- !Test coverage is agreed openly. The depth of regression testing affects cost, so the pack covers what would cause real problems if it broke. Testing every corner of the account isn’t practical, so we focus on what matters most.
- !SuiteApps and integrations depend on third parties. Bundled apps and connected platforms update on their vendors’ cycles, so compatibility is checked and any third-party dependency is stated plainly where it applies.
Release Update Testing (Bi-Annual) FAQs
When do the releases actually land?
What breaks most often?
Can we skip a cycle of testing?
Where does the NetSuite release testing happen – in our sandbox or a preview account?
Last reviewed: 21 October 2026 · Written by the Suite Generation team
Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.
