Enterprise and ERP. NetSuite
Replacing NetSuite with an operations system built for your business
NetSuite is a real ERP. General ledger, receivables and payables, inventory, order management, and multi-subsidiary consolidation in one place, sold as a base platform with modules and user licenses stacked on top. We were never a NetSuite partner, so nothing rides for us on which way you go.
It's also the clearest example of the problem. The license is due before the system is usable. The implementation runs through an outside integrator over months, capability gets priced one module at a time, and when it's finally finished you've configured someone else's software to approximate your own operation. Meanwhile the work that actually runs the business is still happening in spreadsheets beside it.
For what a NetSuite implementation costs and how long it runs by company size, see our sourced research on NetSuite and Salesforce implementation.
Where it fits
Where does NetSuite fit?
We sell no NetSuite licenses and take no referral fees, so this is not a hit piece. These are the cases where keeping it is the honest advice, and if yours is one of them, we will say so on the call.
Multi-entity companies consolidating several sets of books, in more than one currency, closing on a statutory calendar. That's genuinely hard software to write. NetSuite does it.
Businesses whose auditors, lenders, or investors expect a recognized ERP as the book of record. The name on the platform is part of the answer there.
Complex inventory and supply chain work, with several warehouses, landed cost, demand planning, and manufacturing routings. When the modules cover a real need, they're worth what they cost.
A company already live whose finance team is happy with it. If the ledger is doing its job, keep it and fix what sits around it. That's a smaller project than a replacement, and it's usually the honest advice.
Where it breaks
Where does NetSuite break down?
The failure modes below are the ones that show up again and again as a company grows.
Everything is a module. Advanced revenue recognition, demand planning, work in progress and routings, advanced inventory, and the rest all get licensed separately. So the capability you need next arrives with a price you have to negotiate with the vendor.
Edition and user count both drive the license. Growth costs you on two axes at once. Renewal increases are the complaint we hear most often from companies on NetSuite, and by the time one lands the whole business is running on it.
The implementation isn't optional and it isn't short. It runs through an implementation firm, priced in professional-service hours, and published benchmarks put it in the months for a mid-sized company and longer for a multi-entity rollout. Nothing is usable until it's finished, and you're paying the license the whole time.
Customization lives in SuiteScript, SuiteFlow, and saved searches. The language is JavaScript, but the knowledge is specialist, and the platform releases twice a year, so your customizations get retested on the vendor's calendar.
Reporting is a saved search, and writing a good one is a skill. The questions a manager asks every day (what's late, who is overloaded, which job is losing money) get answered by exporting to a spreadsheet. That's how you end up running an ERP and a shadow system at once.
The operational layer is the weakest part of NetSuite and the largest part of the working day. Field work, projects, scheduling, quoting with real pricing rules, the customer-facing view of all of it. Every one of those arrives as another module, another integration, or another sheet.
The replacement
What does replacing NetSuite look like?
This splits two ways. If you bought NetSuite for multi-entity consolidation and a statutory close, keep the ledger and replace the operational layer around it. Quoting, jobs, projects, inventory movement, scheduling, approvals, and the customer portal move into the new system and post back into NetSuite through its API. If you bought it to run operations and the accounting is ordinary, the whole thing can go.
Either way, the system takes the shape of your operation. The records are your jobs, sites, assets, orders, and crews, with real relationships between them, and the pricing and approval rules live in tested, versioned code. Reporting reads live data, so a manager's daily question is a screen. No saved search, no export.
Migration reads NetSuite through its API and saved-search exports. Customers, vendors, items, orders, transactions, and history get mapped into the new structure in a document you approve before anyone writes a row. Both systems run in parallel until the numbers reconcile line for line. Nothing gets switched off until finance has signed off on a closed period that matches on both sides.
You own the result. Code in a repository in your name, database and hosting on accounts in your name, unlimited users including people outside your company, and no module list to negotiate at renewal. We're added as administrators so we can build it and support it, and you can remove us whenever you want.
The stakes
What does it cost to get this wrong?
More than the software. A replacement that goes badly costs you the one thing the old system was still doing, a single place your team agrees on. The failures below each turn a rebuild into a year of parallel systems, so they are the ones we plan around.
The general ledger is derived. You can't copy it out of a table. Transactions post by subsidiary, period and book, so an extract taken without deciding those three produces figures that won't tie to a closed period, and finance signs nothing off.
Custom records and custom fields carry internal ids, and the names on screen are only labels. Pull orders without the item, customer and subsidiary ids resolved and you've got a warehouse of rows nobody can reconcile against what NetSuite reported last quarter.
The operational half is where the working day happens. Replace the finance side, leave scheduling, jobs and quoting in spreadsheets, and the shadow system survives the whole project. That shadow system is the thing the ERP was bought to kill in the first place.
The order of work
What happens, in what order, when you leave NetSuite?
Each step exists because skipping it is how the previous attempt failed. The sequence is fixed. The runway is not, and it goes in your written scope once we know the shape of your data rather than on this page as a calendar promise.
- 01
Module and usage audit
We check which licensed modules carry real activity and which were bought for a plan that changed. Roles get mapped with their subsidiary, department and location restrictions, along with every SuiteScript, SuiteFlow and saved search still firing. Companies routinely find they're paying for capability their own team quietly worked around.
- 02
Extraction with ids resolved
NetSuite comes out through saved-search exports and its web services. Customers, vendors, items, orders and transaction lines get pulled with their internal ids so the relationships survive, and subsidiary, period and currency ride along on every transaction. We don't copy the saved searches. They're configuration, so what gets recorded is the question each one answers.
- 03
The two honest scopes
This one decision shapes everything after it. If the ledger is why you bought NetSuite, it stays and the operational layer moves around it, posting back through the API. If NetSuite was bought to run operations and the accounting is ordinary, the whole thing can go. We take a position on which one applies before we scope anything.
- 04
Build against a live ERP
The new system gets built while NetSuite keeps running, importing on a schedule and posting into it wherever the ledger is staying. Jobs, scheduling, quoting with real pricing rules and the customer-facing view come first. That's where the spreadsheets are, and where a manager's daily question currently needs an export.
- 05
Reconcile a closed period
Nothing gets switched off until finance has a closed period that matches line for line on both sides, including subsidiary consolidation and any currency translation. Operational counts get checked at the same time. Open orders, scheduled work, inventory movement. Then the cutover happens, and the module list comes off at renewal.
Limits
What we will not do
Saying this out loud is cheaper for both of us than finding out in month two. If one of these is what you actually want, we are the wrong firm and we will say so on the first call.
- We won't tell you to replace a general ledger that's doing its job. Multi-entity consolidation and a statutory close are serious software, and if that's why you bought NetSuite we'll build around it and say so plainly.
- We won't switch anything off before finance signs off on a period that reconciles on both sides. A cutover taken on assurances, without matched numbers, is how an audit trail ends up with a hole in it.
- We won't start by rebuilding whatever the integrator configured. The workarounds in your NetSuite are a record of where the model didn't fit your operation. Discovery defines the process you actually want before any of it becomes code.
Questions
What people ask about leaving NetSuite
Can you really replace an ERP?
The operational half of one, yes, and that's where most of the pain sits. A general ledger with multi-entity consolidation and statutory reporting is serious software. When that's why you bought NetSuite, we build around it and tell you so. When it was bought to run operations, a full replacement is realistic.
What about audit and compliance?
Access control by role, a change history nobody can quietly edit, approvals recorded with person and timestamp, and clean exports for your auditor. All of it gets designed in from the start. Auditors care about controls and evidence, and the logo on the login screen is neither of those.
We've got a lot of SuiteScript. Does it come with us?
The rules do. The scripts don't. We read each one for what it enforces and rebuild the rules that still matter as tested code, and the scripts that existed only to bend NetSuite around your business go away with the model.
Can we leave one piece at a time?
Yes, and that's usually how it goes. We build the operational area that hurts most first and connect it to NetSuite through the API, so nothing gets re-keyed while the rest stays put. Every piece after that is its own decision.
What does replacing NetSuite cost?
It depends on which modules are in real use, how many entities and users are involved, and what has to keep connecting, so we don't publish figures. We do publish sourced ranges for what a NetSuite implementation costs by company size. After a strategy call you get a written scope naming every deliverable and what it costs, measured against your renewal.
Who owns the system, the code and the accounts?
Your company does. The repository, the database, the hosting and the sending domain all get created in your name at the start of the build, and we're invited in as administrators so we can work. You can remove us at any point. No fee, no handover charge, no license reverting to us. That matters more with an ERP than anywhere else, because what makes a renewal negotiation uncomfortable is having nowhere else to go. Owning the system puts you back on the other side of that conversation.
What happens to our historical financial data?
It stays available and it stays reconcilable. Transactions, orders, customers, vendors and items migrate with their internal ids, subsidiary, period and currency intact, so historical figures still tie to the periods NetSuite reported. Where the ledger is staying, none of your financial history moves at all and the new system posts into it. Where it's being replaced, you keep the raw saved-search exports as an archive your auditor can read without a NetSuite login. And closed periods reconcile line for line before anything gets switched off.
What if we want to go back to NetSuite?
Nothing prevents it. We don't delete NetSuite at cutover. The account stays readable while confidence is being built, and where the ledger is staying it never leaves at all. Going back later would mean pushing from your own database into NetSuite's API, which is ordinary integration work, because your data sits in a standard SQL database anyone can query. The harder question is what you'd be giving back. Unlimited users including people outside your company, no module list at renewal, and rules that match your operation instead of an industry template.
From the knowledge base
Guides for people weighing up NetSuite
Reference pages, not sales pages. Each one is useful even if you decide to stay exactly where you are.
How to tell whether your business actually needs custom software
Seven tests you can run against your own operation this week. Most businesses that run them find a configuration problem, not a build.
Salesforce and NetSuite implementation cost and timeline, by company size
A sourced comparison table at 50, 100, 250, 500, and 1,000 employees. Every figure is cited and dated, and the thin-data cells say so.
Related
Coming from a different tool?
The same honest treatment for the other platforms we used to implement, and the pages that explain the custom model itself.
Tell us where NetSuite stopped fitting
Book a strategy call, or send a short note about the workarounds your team runs today. If keeping NetSuite is the right answer, you will hear that first.