Who this is for
IT managers, finance managers, and business owners running NetSuite who need help managing upgrades, customisations, or integrations.
Question this answers
How do we manage NetSuite's automatic upgrades, keep customisations working, and maintain integrations?
What you'll leave with
- How NetSuite's upgrade cycle works and what it means for your customisations
- Common support and configuration issues
- How to manage SuiteScript and integration maintenance
- Key risks and decisions for growing NetSuite environments
Platform overview
NetSuite is Oracle's cloud ERP platform, widely used by mid-market businesses in Australia for financials, inventory, e-commerce, and CRM. It's a true cloud system — everything runs in Oracle's data centres, and Oracle controls the release cycle.
That cloud-native architecture is both its strength and its challenge. You get automatic updates and no infrastructure to manage. But you also get upgrades you didn't ask for, at times you didn't choose, that can break customisations you depend on.
Common version & support issues
Forced upgrade cycle. NetSuite releases two major updates per year. Unlike on-premises ERP, you can't stay on an old version indefinitely. You get a sandbox preview period, then the update rolls to production whether you're ready or not.
SuiteScript deprecation. Customisations built with SuiteScript 1.0 are increasingly at risk. Oracle has been pushing migration to SuiteScript 2.x, and older APIs are gradually being removed. If your environment has significant 1.0 code, this is a growing risk.
Saved search fragility. Many NetSuite implementations rely heavily on saved searches for reporting, workflows, and dashboards. These can break when Oracle changes field names, adds new fields, or modifies search behaviour.
Support gaps. NetSuite's standard support can be frustrating for complex issues. Australian businesses often need local partners for responsive, knowledgeable support — especially around BAS, PAYG, and Australian compliance requirements.
Upgrade and migration paths
Release management process. The most important thing you can do is establish a testing process for each release. Use the sandbox preview to test all critical customisations, workflows, saved searches, and integrations before the production update.
SuiteScript migration. If you have SuiteScript 1.0 code, plan to migrate it to 2.x. This isn't just a syntax change — it's an architecture change. Budget for proper development and testing time.
Configuration optimisation. Many NetSuite environments have been configured ad-hoc over years. A configuration review can identify inefficiencies, unused features, and misconfigurations that cause ongoing headaches.
Platform extension. Rather than over-customising NetSuite, build external applications that connect via API. Customer portals, mobile apps, advanced reporting, and specialised workflows often work better as separate applications that integrate with NetSuite.
Customisation & integration challenges
SuiteScript maintenance. Every custom script needs an owner and a maintenance plan. Undocumented scripts from departed developers are a major risk. We recommend a full script inventory with owners, purposes, and test cases.
Workflow complexity. NetSuite workflows can become deeply nested and difficult to debug. As business processes change, workflows accumulate conditions and branches until nobody fully understands what they do.
Integration methods. NetSuite supports several integration methods:
- RESTlets: Custom API endpoints built in SuiteScript. Flexible but require development.
- SuiteTalk (SOAP): Traditional web service API. Robust but verbose.
- REST API: Modern REST interface. Growing in capability with each release.
- CSV imports: Still widely used. Simple but fragile and manual.
The biggest integration risk is sprawl — connections built by different people at different times using different methods, with no central documentation or monitoring.
Risks and decision points
Key risks
- SuiteScript 1.0 code base
Deprecation risk is real. Plan migration proactively.
- Integration sprawl
Document all integrations centrally. Test all of them during each release.
- Over-customisation
Heavy customisation means heavy upgrade cost. Evaluate whether standard features have caught up.
- Knowledge concentration
If one person built most of the customisations, that's a business risk.
- Testing gaps
Without a structured testing process, upgrade breakage goes undetected.
How HELLO PEOPLE can help
- Customisation audit: Inventory all SuiteScripts, workflows, and saved searches with risk assessments
- SuiteScript migration: Upgrade 1.0 scripts to 2.x with proper testing
- Integration modernisation: Replace CSV imports with API-based integrations
- External application development: Build customer portals, dashboards, and mobile apps that connect to NetSuite
- Release testing support: Pre-release testing of customisations and integrations in sandbox
Frequently asked questions
Does NetSuite automatically upgrade itself?
Yes — NetSuite pushes two major releases per year that you can't opt out of. But "automatic" doesn't mean "safe." Customisations, workflows, and integrations can break during these releases if they rely on features or behaviours that change. You need a testing process in place for every release cycle.
What happens to our SuiteScript customisations during upgrades?
SuiteScript 1.0 code is at particular risk — Oracle has been deprecating older APIs. SuiteScript 2.x code is more future-proof but still needs testing. We recommend auditing all customisations and migrating 1.0 scripts to 2.x before they break in a future release.
How much does NetSuite support and development cost in Australia?
NetSuite partner rates in Australia typically range from $200-$350 per hour. For ongoing support, expect $3K-$15K per month depending on complexity. Custom development projects range from $15K-$100K+ depending on scope.
Should we move off NetSuite?
Usually not — NetSuite is a strong platform. The pain is usually in how it's been configured and customised, not in the platform itself. Fix the configuration, modernise the customisations, and improve the integrations before considering a platform change.
Can you help with NetSuite integrations?
Yes. We build and maintain integrations between NetSuite and other systems using RESTlets, SuiteTalk (SOAP/REST APIs), and middleware. We can also replace fragile CSV import workflows with real-time API connections.
Key takeaways
- NetSuite upgrades are automatic — you can't defer them, so you need a testing process for every release
- SuiteScript 1.0 customisations are a ticking clock. Migrate to 2.x before Oracle deprecates them fully.
- Saved searches and workflows are the most common source of subtle upgrade breakage
- Integration sprawl is the biggest ongoing risk — each new connection adds maintenance overhead
- Don't over-customise. The more you diverge from standard NetSuite, the more every upgrade costs.