Oracle’s message on NetSuite Next is simple: nothing breaks. No data migration, no reimplementation, your customizations and workflows carry forward as-is. That’s largely the truth. It’s also the kind of claim that can give you a false sense of security and lead someone to upgrade to NetSuite Next without seeing that there are a few caveats to that.
We went looking for what Oracle has actually confirmed changes or breaks when you turn on NetSuite Next — and we are going to add some of the insights from what we’ve seen in our own testing so that you can be prepared before you choose to upgrade. This is part of our ongoing NetSuite Next series, where we’re testing the platform against a real account rather than repeating vendor talking points.
What Actually Stays the Same
The good news is that turning on NetSuite Next isn’t a migration event. Your data doesn’t move. Your roles and permissions don’t change. Supported SuiteScript customizations, SuiteFlow workflows, and saved searches carry forward without modification just because you flipped the switch. If you’re picturing this like a version upgrade that quietly reshuffles your configuration, and requires you to spend months prepping for the change, that’s just not what you should expect.
From what we’ve seen in our testing, all of these claims by Oracle hold up pretty well. There are, however, a smaller group of things that don’t carry forward cleanly, and there will be some additional work needed to get real value out of it if you are utilizing some of those features. Fair warning, this part of the preparation gets a little technical.
What Actually Needs Testing
There are two main issues that seem like they will need some direct attention before migration.
Inline HTML fields on Form pages are getting deprecated. Oracle’s documentation states this directly, with one exception: Suitelet Forms. If you’ve got custom forms using inline HTML for branding, embedded content, or anything else, you are going to have some issues going forward. This also applies to portlets — if you regularly use inline HTML custom portlets for your dashboards, it’s a good idea to check them in a sandbox environment before migration.
Custom CSS and direct DOM manipulation. This one’s a little more nuanced than “NetSuite Next breaks it,” because direct DOM access was never officially supported in the first place. SuiteScript’s own documentation has said for years that you’re supposed to access the NetSuite UI only through SuiteScript APIs, not by reaching into the page’s DOM directly. What’s changing isn’t the rule — it’s that Redwood restructures the underlying DOM and CSS classes, so any client script or custom CSS that was quietly relying on the old structure (and a lot of accounts have some of this, whether anyone remembers writing it or not) is now more likely to actually visibly break instead of just being technically unsupported. If your account has custom client scripts doing document.querySelector type work, or CSS overrides targeting specific NetSuite-generated class names, that’s exactly the kind of thing to run through a NetSuite Next preview account before you turn this on.
Neither of these is a surprise if you’ve been paying attention to SuiteScript best practices. They’re a problem if your account accumulated this kind of customization years ago, before anyone thought Redwood or Next was coming, and nobody’s looked at it since.
The Part That Isn’t “Breaking,” But Is Real Work: AI Descriptions
Here’s the thing that doesn’t show up in most “is NetSuite Next going to break my stuff” conversations, because it’s not about breaking anything. It’s about whether Ask Oracle is actually useful once it’s on.
NetSuite added AI Description fields to custom records, custom fields, and custom transaction definitions, for every account. It’s a short text field, up to 280 characters, where you describe what the object or field is actually used for. AI features use that description to understand how that object fits into your custom process, which is what lets Ask Oracle give a relevant answer instead of a generic one when someone asks about it. As an example — if you have a custom field that is storing gross profit information on a transaction, filling that information in helps Ask Oracle know to reference that field when you are asking gross profit questions in the future.
This isn’t just an Ask Oracle thing either. It feeds the same data that powers the NetSuite AI Connector Service. If you’re already using an MCP connection to query your account, this is the same metadata and it will benefit you there as well.
What we see time and time again in accounts is that people tend not to fill information into the normal field help or description when creating fields. If that trend extends to this AI Description field, it will make Ask Oracle less effective in your account.
None of that stops NetSuite Next from turning on. It just means Ask Oracle either won’t know what a custom field is for, or will guess based on the field name and hope that’s enough. For anything genuinely core to how your business runs on NetSuite, this is worth doing deliberately rather than leaving to chance. It doesn’t have to be everything at once — start with the records and fields people will actually ask Ask Oracle about.
Where It’s on You, Not Oracle
Third-party SuiteApps aren’t something Oracle can promise compatibility for. Oracle’s guidance is to confirm with each vendor that their app supports 2026.2 and NetSuite Next specifically. That’s not a knock on Oracle — they don’t control someone else’s code — but it does mean “will my stuff still work” isn’t a single question with a single answer. It’s a list of vendors to check.
Takeaway
“Nothing breaks” holds up better than a lot of major-release marketing usually does. The core system, your data, and your standard customizations are all genuinely stable. What actually needs attention is narrower and more specific than either the vendor messaging or the internet FUD suggests: inline HTML on forms, anything leaning on unsupported DOM access, third-party app compatibility you have to chase down yourself, and a real but unglamorous cleanup task around AI Descriptions if you want Ask Oracle to be worth using on your custom objects. Test the first two in a preview account, budget time for the third, and check with your vendors on the fourth.
Want a second opinion before you flip the switch? If you’re weighing whether to activate NetSuite Next now or wait, or you want a second set of eyes on what in your account might be affected, we’re happy to talk through it. Book a free consultation to talk it through.