What Leaving NetSuite Actually Costs: Migration, Data, and the Modules You Will Not Replace.
Updated: 3 days ago
Every NetSuite partner will quote you the way in. The implementation cost, the licence, the modules, the first-year services. Nobody quotes the way out, and yet the way out is a project with the same shape and, for a company that has been on NetSuite for five or more years, often a bigger one.
We work with companies leaving NetSuite, mostly for Zoho, sometimes for something else, and occasionally we tell them not to leave. This is the bill as we have seen it. It has four numbers in it. The licence saving is one of them, and it is the smallest.
Number one: the licence, which is the number you already know.
You know what NetSuite costs you, because the renewal letter tells you every year, and the letter has been getting more expensive. The saving from leaving is the difference between that and the destination's licence, and for a mid-market company it is real money: often a high five-figure or low six-figure sum a year.
Lead with it if you like, but do not decide on it, because it is the only one of the four numbers that is certain, and the other three are larger.
Number two: migration, which is a project, not a task.
A NetSuite exit is an ERP implementation in the other direction, with the added constraint that the old system is still running the business while the new one is being built. We wrote the general ledger of migration cost line items nobody budgets for and every line of it applies here. The NetSuite-specific parts are these.
The customisations you forgot you had. A five-year NetSuite instance carries SuiteScripts, workflows, saved searches and custom records that were built for a problem someone had in year two. Some run the business. Some run nothing. Nobody has the list. Producing the list is the first week of the exit and it is always longer than anyone expected.
The integrations that were built to NetSuite's shape. The shop connector, the 3PL feed, the bank feed, the expense tool, the payroll export. Each one talks to NetSuite's data model, and each one has to be rebuilt to the destination's. This is the line most often left off the estimate and most often the largest.
The people. Your finance team knows NetSuite. They have to learn the destination while closing the books in the old one. Plan for a slower close for two quarters, and plan for the person who built the saved searches to be unavailable for anything else.
The migration number is decided by the size of those three lists, and you can count them before you choose a destination. That is the point of an ERP Readiness Review: to count them first.
Number three: data, which is worse than migration.
Migration moves the business. Data moves the history, and history in NetSuite is stored the way NetSuite thinks, which is not the way anything else thinks.
The open balances are easy. The customers, vendors, items and chart of accounts are mostly easy. What is hard is everything that gives those records meaning: seven years of transactions, the subsidiaries and intercompany eliminations if you have them, the revenue recognition schedules, the inventory costing history, the closed periods that an auditor may one day ask to see.
There are three honest choices for the history, and the choice is a number.
Bring it all across. The most expensive option and the one that fails most often, because the destination's model will not hold NetSuite's history without a translation, and the translation is a project of its own.
Bring the open items and the balances, keep NetSuite read-only for a period. The most common choice, and it means paying a reduced NetSuite licence for a year or two while the history ages out of relevance. That licence is part of the exit cost and it is often forgotten.
Bring the balances, archive the history to a warehouse. The cheapest ongoing option, and it means building an archive that the finance team and the auditor can query. It is a small project, and it is one that outlives the exit.
Pick one before you pick a destination. The destination changes the price of each choice, but the choice itself is yours, and it is set by what your auditors, your lenders and your own reporting actually need from the history.
Number four: the modules you will not replace.
This is the number that stalls exits half way. NetSuite is a suite, and the reason you chose it was that it did everything in one place. The destination, whatever it is, does not do everything in one place in the same way, and there are usually two or three NetSuite modules for which the destination's answer is either a weaker module, a separate product or a build.
For the companies we see, the usual ones are these.
Multi-subsidiary consolidation. If you run several entities with intercompany transactions and consolidated reporting, NetSuite's OneWorld did this well, and the destination's answer is usually a consolidation tool alongside the accounting rather than inside it. That is a product and an integration.
Advanced revenue recognition. If your revenue is subscription, milestone or multi-element, and you use NetSuite's ARM module, the destination will need either its own module or a build. This is the one to check first, because it decides whether an exit is even sensible for a software or services business.
Demand planning and advanced inventory. If you use NetSuite for MRP, demand planning or multi-location inventory with landed cost, the destination's inventory may be enough or may not, and the way to know is to write down which of those features you actually use and test the destination against the list.
The reporting people built in saved searches. Not a module, but it behaves like one. Every department has reports that only exist as saved searches, and the destination's reporting will have to be rebuilt to match, or the departments will keep a NetSuite login for a year.
Number four is decided before the vendor is chosen, because it is a list of what you use, and you can make that list today. If we did nothing else in an ERP Readiness Review, we would make that list, because it tells you whether the exit is a clean move, a move with two builds alongside it, or not worth it.
Putting the four together.
Here is the honest shape of a NetSuite exit for a mid-market company with one or two entities, ordinary revenue and a handful of integrations. The licence saving pays for the move in year two or three. The migration and data numbers together are usually one to two years of the licence saving. The modules number is anywhere between nothing and a reason to stay, and you know which before you sign anything.
For a company with several entities, complex revenue and a decade of history, the exit can be a two-year project and the licence saving alone will not justify it. What justifies it, when it is justified, is what we wrote about in the honest NetSuite alternatives comparison: the operating cost of a suite that has become a tax on every change the business wants to make. That is a real cost and it belongs in the decision, but it is not one of the four numbers in the exit bill, and mixing the two is how exits get sold and how they stall.
What we do about it.
We run the exit as three projects, not one. The first is the review, which produces the four numbers and the list of modules, and ends with a written recommendation that can be to stay. The second is the build of the destination, run to a guaranteed estimate, with the integrations rebuilt first because they are the longest lead item. The third is the data move and the cutover, with a decision on the history made in the first project so nobody is deciding it in the last week.
We do not own the outcome of your decision to leave. We are accountable for the numbers being right before you make it, and for the estimate holding after you do. If the review says the modules number is a reason to stay, we say so, and the review has cost you a few days.
The short version.
Leaving NetSuite costs four things: the licence, which you save; the migration, which is a project; the data, which is a decision; and the modules you will not replace one for one, which is a list. Two of the four are yours to know before any vendor is in the room. Know them first, and the exit is a project with a price. Skip them, and it is a licence saving that turns into two suites running side by side.
Know whether your business is ready for an ERP before you sign for one.
The ERP Readiness Review is a 90-minute working session plus a written scorecard across master data quality, documented exceptions, integration scope and data ownership. Fixed scope, no obligation. Or see how we approach it.
More on the same problem:
Comments