Week 1 of 8
The release calendar you actually live with
Welcome to The Sign-Off Table. For the next 8 weeks you will get one practical move a week for testing NetSuite releases and changes, in the order you will need them. After that, a weekly roundup of new research, guides and templates.
We start with the calendar, because NetSuite sets it for you. Every account is upgraded to each scheduled version, 2026.2 now and 2027.1 next. Your date is in the New Release portlet, and you can move it within limits through Customer-Scheduled Maintenance. Oracle also says enhancements can now arrive in monthly minor releases between the two upgrades.
This week: put every date on one page
- Find your production upgrade date in the New Release portlet. The sandbox follows within 7 days after production.
- Work backwards: when you will request Release Preview (Oracle says about 5–7 days to create it), when testing starts, and when you need a decision.
- If the date clashes with month-end close, an audit or a go-live, move it with Customer-Scheduled Maintenance now, not the week before.
- Add SuiteApp vendor releases and your own deployment windows to the same calendar. They change your account too.
- Name one person who owns the upgrade decision and the evidence behind it.
Number of the week
2
scheduled NetSuite version upgrades a year, with monthly minor releases possible in between.
Source: Oracle NetSuite 2026.2 Release NotesUse this week
- NetSuite Release Preview Test Plan →
A calendar sheet that works out your test window, sandbox upgrade date and Release Preview purge date for you.
- ERP Release Calendar →
Upgrades, SuiteApp releases, freezes and close periods on one timeline.
- Guide: testing NetSuite upgrades in the Release Preview window →
The dates, the limits and a plan for a small team.
Next week: before you test anything, list everything in your account that a release can break.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.