NetSuite is one of the most widely used cloud ERP platforms in Australia, particularly among mid-market businesses running complex operations across finance, inventory, CRM, and e-commerce. But "cloud" doesn't mean maintenance-free. Oracle pushes mandatory upgrades twice a year, and if your instance is heavily customised, those upgrades need careful management.
This guide covers what you actually need to think about when it comes to NetSuite upgrades and ongoing support - whether you're running a vanilla instance or one loaded with SuiteScript customisations, custom records, and third-party integrations. We work with businesses across Perth, Melbourne, Sydney, and Brisbane on this stuff, and the same problems come up time and again.
Why NetSuite Upgrades Matter
Unlike on-premise ERP systems where you can sit on an old version for years, NetSuite upgrades are mandatory. Oracle rolls them out to every account on their schedule, not yours. Here's why that matters:
- API deprecations - Oracle regularly deprecates older APIs. If you're still running SuiteScript 1.0 code, each upgrade cycle brings a higher risk of breaking changes.
- New features - Each release adds functionality that could save your team time. But you only benefit if your customisations don't conflict with the new features.
- Security patches - Upgrades include security fixes. Since NetSuite holds financial data, employee records, and customer information, staying current matters for compliance.
- Integration compatibility - Third-party connectors (e-commerce platforms, payment gateways, logistics providers) update their NetSuite connectors to match the latest version. Falling behind creates compatibility gaps.
- SuiteAnalytics changes - Reporting tools and saved search capabilities evolve. Older saved searches might return different results or stop working entirely after an upgrade.
The bottom line: you can't skip NetSuite upgrades, so you need a process for handling them. Ignoring the preview window and hoping nothing breaks is a strategy - just not a good one.
The NetSuite Upgrade Process
Oracle gives you a preview environment (sandbox) before each major release hits production. Here's how to use that window properly:
1. Review the Release Notes
Oracle publishes detailed release notes for every upgrade. Don't just skim them. Focus on:
- Deprecated APIs and SuiteScript methods your customisations might use
- Changes to standard record behaviour (approvals, workflow triggers, field defaults)
- New modules or features that overlap with your existing customisations
- SuiteAnalytics and saved search changes that could affect your reports
2. Audit Your Customisations
Before testing anything, get a clear inventory of what's customised in your instance:
Customisation Inventory
- SuiteScript files - Client scripts, user event scripts, scheduled scripts, map/reduce scripts, Suitelets, RESTlets. Especially anything still on SuiteScript 1.0.
- Workflows - Custom workflows with script actions, condition builders, and email triggers.
- Custom records and fields - Any custom record types, fields, lists, and segments you've added to standard records.
- Saved searches - Searches used in dashboards, KPIs, scripts, and integrations. These are often the first things to break silently.
- SuiteBundle installations - Third-party bundles from the SuiteApp marketplace. Check vendor compatibility notes for each bundle.
- Integrations - RESTlet-based integrations, SuiteTalk (SOAP), token-based auth connections, and any middleware linking NetSuite to other systems.
3. Test in Sandbox
Once Oracle refreshes your sandbox with the new release:
- Run your critical business processes end-to-end: create sales orders, process invoices, run payroll, fulfil orders
- Execute every SuiteScript and check the execution log for errors
- Verify saved searches used in dashboards and reports return correct results
- Test integrations - push and pull data from connected systems
- Check PDF templates (Advanced PDF/HTML) for layout issues
- Run a parallel payroll or test pay run if you use SuitePeople
4. Fix What's Broken
This is where the real work happens. Common issues after a NetSuite upgrade:
- Script errors - Deprecated methods, changed object properties, or new mandatory fields that your scripts don't populate
- Workflow failures - Conditions that no longer evaluate correctly because of changes to underlying record behaviour
- Report discrepancies - Saved searches returning different counts, totals, or missing records due to formula or criteria changes
- Integration failures - Token-based connections that need reauthorisation, or RESTlets that receive differently structured payloads
- UI changes - Form layouts, sublists, or user interface elements that move or change, confusing your team
Tip: If you have SuiteScript 1.0 code, treat every upgrade as an opportunity to migrate critical scripts to 2.x. The longer you wait, the more expensive and risky the eventual migration becomes.
5. Communicate and Train
Don't let the upgrade surprise your team. After testing:
- Document any changes in behaviour they'll notice
- Update internal training materials if workflows have changed
- Brief finance, warehouse, and customer service teams on what's different
- Set up post-upgrade monitoring to catch issues in the first week
SuiteScript Maintenance and Migration
If your business has been on NetSuite for a while, you probably have a collection of SuiteScript customisations that were built over the years by different developers or consultants. Some of it's well-documented. A lot of it isn't.
Here's how to approach SuiteScript maintenance practically:
SuiteScript 1.0 to 2.x Migration
This is one of the most common support tasks. SS 1.0 has been around since 2009 and Oracle is gradually phasing it out. SS 2.0 (and 2.1, which supports modern JavaScript features like arrow functions and template literals) is the path forward.
What Changes in the Migration
- Module-based architecture - SS 2.x uses AMD-style modules (define/require) instead of global functions. Every script needs restructuring.
- Different API calls - nlapiLoadRecord becomes record.load(). nlapiSearchRecord becomes search.create(). Most 1.0 API methods have 2.x equivalents but the syntax is completely different.
- Error handling - SS 2.x has proper try/catch with typed errors instead of the generic error objects in 1.0.
- Governance - SS 2.x has different governance limits and a more sophisticated usage tracking system.
- Async capabilities - Map/reduce scripts in SS 2.x handle large data volumes much better than scheduled scripts in 1.0.
Ongoing Script Maintenance
- Code reviews - Review custom scripts at least quarterly. Remove unused ones, consolidate duplicates, and add proper logging.
- Performance - Monitor script execution times. Long-running client scripts slow down the UI for your entire team.
- Documentation - Maintain a living document of what each script does, when it runs, and what records it touches. Future developers (and future you) will be grateful.
- Version control - Use SuiteCloud Development Framework (SDF) and Git to manage SuiteScript code properly. Stop editing scripts directly in the NetSuite file cabinet.
Managing NetSuite Integrations
NetSuite rarely operates in isolation. Most Australian businesses connect it to other systems - and these integrations need ongoing attention:
Common NetSuite Integration Points
- E-commerce - Shopify, Magento, WooCommerce, BigCommerce. Order sync, inventory levels, and customer records flowing into NetSuite.
- Logistics & 3PL - StarTrack, Australia Post, DHL, Sendle. Fulfilment data, tracking numbers, and shipping costs.
- Payment gateways - Stripe, PayPal, Tyro, Square. Payment reconciliation and fee tracking.
- CRM - Salesforce, HubSpot. If you're using NetSuite CRM alongside an external CRM, contact and opportunity sync is critical.
- Banking - Bank feed imports, payment file generation (ABA files for Australian banks), and reconciliation.
- Payroll - If not using SuitePeople, external payroll systems like KeyPay, Employment Hero, or ADP need data exchange.
- Middleware - Celigo, Boomi, MuleSoft, or custom Node.js/Python integration layers that handle data transformation.
Each integration needs to be tested during every NetSuite upgrade cycle. The most common failure pattern is a RESTlet endpoint that silently starts returning different data structures or a SuiteTalk query that stops matching records due to changed field IDs.
NetSuite Support Models
When it comes to ongoing NetSuite support, you essentially have three options:
1. Oracle Standard Support
Included in your licence fee. Covers platform issues, bug reports, and access to SuiteAnswers documentation. It does not cover your customisations, integrations, or business-specific configuration. If something breaks after an upgrade and it's in your custom code, Oracle won't fix it.
2. NetSuite Partner (Managed Services)
An external NetSuite partner manages your instance on an ongoing basis. This typically includes:
- Pre-upgrade testing and remediation
- SuiteScript maintenance and bug fixes
- New feature development when you need changes
- Integration monitoring and troubleshooting
- User support and training
- Report building and saved search management
3. Internal Team
Larger organisations sometimes hire a NetSuite administrator or developer in-house. This works if you have enough ongoing work to justify a full-time role - but finding experienced NetSuite developers in Australia is difficult, and the cost is significant.
Most mid-market businesses end up with a hybrid: an internal admin who handles day-to-day operations, and an external partner for development, upgrades, and complex troubleshooting.
Common NetSuite Problems We See
After supporting dozens of NetSuite instances across Australia, these are the issues that come up most often:
- Customisation sprawl - Years of different consultants and developers adding scripts, workflows, and custom fields without a coherent plan. The instance becomes fragile and hard to maintain.
- Undocumented scripts - Nobody knows what half the SuiteScripts do, who wrote them, or whether they're still needed. When something breaks, troubleshooting takes days instead of hours.
- SuiteScript 1.0 technical debt - Legacy code that's increasingly at risk with every upgrade cycle. The migration to 2.x keeps getting deferred.
- Broken integrations after upgrades - Middleware or direct API connections that fail silently, causing data discrepancies between NetSuite and connected systems.
- Poor reporting - Saved searches built by different people with inconsistent logic. Dashboards that don't tell the full picture because the underlying searches are wrong.
- Slow performance - Client scripts that bog down page loads. Scheduled scripts that timeout. Search-heavy workflows that hammer the system.
- Licence creep - Paying for modules nobody uses because the original implementation partner turned everything on. Reviewing your licence periodically can save thousands per year.
How HELLO PEOPLE Can Help
We're a Perth-based software company with 18+ years of experience building, integrating, and supporting enterprise systems for Australian businesses - Perth, Melbourne, Sydney, Brisbane, Adelaide, and beyond.
Our NetSuite Services
- Upgrade management - We handle the full upgrade cycle: release note review, customisation audit, sandbox testing, remediation, and production verification.
- SuiteScript development & migration - New customisations in SS 2.x, and migration of legacy SS 1.0 code to modern standards.
- Integration development - RESTlets, SuiteTalk connections, middleware setup, and ongoing monitoring for your connected systems.
- Performance optimisation - Script profiling, governance analysis, saved search optimisation, and UI performance improvements.
- Data migration - Moving data in or out of NetSuite, including migrations from other ERPs.
- Ongoing managed support - Monthly support packages covering admin tasks, bug fixes, small enhancements, and user support.
Fixed-price quotes for defined work. For upgrade cycles, SuiteScript migration, and integration projects, we provide fixed-price quotes. For ongoing support, we offer monthly packages tailored to your usage. Get in touch for a free assessment of your NetSuite instance.
Frequently Asked Questions
How often does NetSuite get upgraded?
Oracle releases two major upgrades per year. These are mandatory - you get a preview window (typically 4-6 weeks) to test in your sandbox, and then the upgrade rolls to production on Oracle's schedule. Minor patches can happen more frequently.
Will my customisations break?
Possibly. Every upgrade carries risk for customised instances. The more SuiteScript you have (especially SS 1.0), the higher the risk. This is why upgrade testing is essential - not optional.
What if I'm still running SuiteScript 1.0?
Plan a migration to SS 2.x. Oracle hasn't announced a hard end-of-life date for SS 1.0, but support is declining and each upgrade brings more deprecations. A phased migration starting with your most critical scripts is the practical approach.
Can I migrate away from NetSuite?
Yes, but it's a major undertaking. NetSuite holds deeply structured data across many modules. Migration requires careful planning, data mapping, and extensive testing. We help businesses evaluate whether upgrading NetSuite or moving to a different platform makes more sense for their situation.
How much does NetSuite support cost?
It depends on your needs. Oracle's standard support is included in your licence. Third-party managed support varies based on hours and complexity. Contact us for a quote tailored to your NetSuite instance.
Summary
NetSuite is a powerful ERP, but it needs ongoing attention. Oracle's mandatory upgrades mean you can't just set and forget - especially if you have customisations and integrations. The key is having a reliable process for each upgrade cycle and a support arrangement that keeps your instance clean, fast, and well-documented.
If your NetSuite instance has become hard to manage - scripts nobody understands, integrations that break after upgrades, or performance issues your team works around - book a free 15-minute call and we'll assess where things stand.