A NetSuite partner in Australia takes a business from a signed licence to a live system. The partner scopes the modules and configures the chart of accounts and subsidiaries; it migrates the data; it builds the integrations and reports; it trains the team and supports go-live. The partner is accountable for the implementation. Oracle sells and hosts the software.
Most of the questions we hear from businesses looking at NetSuite come down to one: what does the implementation involve, and where does it go wrong? This article walks through the phases in the order they happen, and at each one says what the partner owns and what the business has to bring.
What a NetSuite partner does, and what Oracle does
Oracle NetSuite licenses and hosts the platform and releases the twice-yearly upgrades. A NetSuite Solutions Partner such as Ascend Solutions does the rest, from the licence to a working business: discovery, configuration, data migration, customisation, integrations, training and ongoing administration. Oracle bills the licence. The partner quotes the implementation and support on their own, scoped in a written proposal before any work starts.
The distinction matters when something breaks after go-live. Platform faults go to Oracle support. Problems with configuration, process or reporting belong to the partner, and businesses that bought the software first and found a partner second tend to confuse the two.
Phase one: discovery and scoping
Before any configuration starts, the partner needs to understand how the business runs: which entities and currencies, how it recognises revenue, how stock moves. Month-end today matters too, and so does the list of systems that have to keep talking to the ledger. The output is a scope document: modules, integrations, reports, the data to migrate, the people on each side.
This is the phase that decides the budget. A scope that says “financials, two subsidiaries, inventory, Shopify integration, three custom reports” has a price. A scope that says “everything we do now, but better” does not, and projects that start on that basis are the ones that run long. Our view is that a business which cannot describe its month-end close on one page is not ready to sign a licence, whatever the sales cycle says.
Phase two: configuration
Configuration turns the business design into settings: the chart of accounts; subsidiaries and intercompany rules; tax codes for Australian GST; departments and classes for reporting; approval workflows; and the roles that control who sees and does what. Done well it is the least visible phase and the most important one, because each report and each integration sits on top of it.
A partner that is also an accounting practice has an advantage here. The chart of accounts and the reporting segments are an accounting design problem as much as a software one. If a BAS or a year-end does not come out clean, we trace the cause to this phase more often than to any other. Small decisions here turn into large ones later.
Phase three: data migration
Migration moves the master data (customers, suppliers, items) and the open position (open invoices, bills, opening balances) from the old system into NetSuite. The partner summarises historical transactions rather than loading them line by line, and the old system stays read-only for lookups. Most of the work is cleaning. Budget for it. Duplicate contacts and inactive items in the source system become errors in the new one, and so do unreconciled balances, unless someone deals with them first.
Expect the partner to run the migration at least twice: once into a sandbox to find the problems, and once for real at cutover. The business’s job is to reconcile the opening balances and sign them off. Once trading starts in NetSuite, the opening position is the foundation of everything that follows.
Phase four: customisation and integrations
Customisation in NetSuite happens through SuiteScript and SuiteFlow rather than by changing the core. Typical work includes custom fields and records. Approval workflows and automated journals come next. The bigger items are the integrations that keep the ledger current: the eCommerce platform, the point of sale, the payment gateway, payroll, the warehouse system. The partner builds and documents these; the business owns the decision about which manual processes are worth automating and which can stay as they are.
Integrations are where scope creep lives. Each one needs four things defined: what moves, which direction it moves in, how often, what happens when it fails. That definition belongs in the scope document, not in a conversation two weeks before go-live.
Phase five: testing, training and go-live
User acceptance testing means the business’s own people run their real processes in the sandbox: raising a sales order, receiving stock, running a payroll journal, closing a month. The partner fixes what breaks and trains the team on the processes as configured, not on NetSuite in general. Go-live follows as a scheduled cutover, at a month end in most cases, with the partner on hand for the first close.
Phase six: after go-live
The first three months decide whether the system sticks. Reports get refined, workflows get adjusted to the way people work, and the team stops reaching for spreadsheets. Spreadsheets are the tell. A partner that offers ongoing administration takes this on, so the business does not depend on one internal expert. That is the reason to choose a partner that intends to stay rather than hand over and leave.
If you already run NetSuite and the partner who implemented it has gone, that is a common starting point too. We review the configuration and finish the reports and dashboards still on the list, then take on the administration from here. The NetSuite page describes both kinds of engagement, and software conversions covers the migration side in more depth.
Frequently asked questions
How long does a NetSuite implementation take?
It depends on four things: the modules, the number of entities, the volume of data to migrate, the integrations. A scoped project has a timeline in the proposal. An unscoped one has no reliable timeline at all, which is why discovery comes first.
What does a NetSuite implementation cost?
Oracle bills the NetSuite licence according to your modules and users. The partner quotes implementation and support from the scope, as a fixed fee in a written proposal. We do not publish a figure because an honest one depends on the scope.
Is NetSuite right for a business on Xero or MYOB?
Only once the business has outgrown them: several entities, multiple currencies, inventory plus eCommerce that need one system, or reporting the smaller platforms cannot produce. If you are not there yet we will say so, and recommend the platform that fits.
Do you work with businesses outside Canberra and Brisbane?
Yes. Implementation is remote by default, with on-site workshops and go-live support by arrangement anywhere in Australia.
If you are weighing up NetSuite (or you have it and need it finished), book a discovery call at ascendsolutions.com.au/contact or phone (02) 6189 2248.
