Replacing NetSuite: The Five Modules You'll Have to Build
A realistic scope for ERP replacement at sub-$200M companies — what to build, what to buy, and what to keep.
A realistic scope for ERP replacement at sub-$200M companies — what to build, what to buy, and what to keep.
Who actually leaves NetSuite
Almost always companies between $30M and $200M revenue with a discrete-manufacturing or distribution model and an unhappy NetSuite seat count. The complaint is consistent: "we pay seven figures a year and 70% of what we use is a glorified database." Below $30M the pain is real but the build economics rarely work. Above $200M the audit and statutory burden makes a managed ERP defensible again.
1. General ledger + AR/AP
Double-entry GL, multi-entity, multi-currency, period close. Most teams replace this with a focused tool like ERPNext or a custom service backed by Postgres + a clean chart-of-accounts model. AR and AP follow naturally. Statutory tax filings stay with a focused SaaS (Avalara, TaxJar) — do not build that yourself.
2. Inventory + lot tracking
For most distributors and manufacturers this is the module they actually need. Lot/serial tracking, multi-location stock, costing methods (FIFO, average), reservation logic, cycle counts. Custom builds win here because the workflows are specific and NetSuite's SuiteScript layer is where teams already write custom logic — moving that logic into TypeScript is a net simplification.
3. Order-to-cash
Quote → SO → fulfilment → invoice → cash application. The win versus NetSuite is integration depth: tight coupling with your shipping carrier API, your e-commerce store, and your CRM. The replacement is rarely a UI rewrite; it is a workflow rewrite that ships faster on a custom stack than via SuiteFlow.
4. Procurement + vendor management
PO creation, three-way match, vendor onboarding, certificate of insurance tracking. This is one of the smallest modules and one of the easiest to ship — a focused service plus a thin admin UI handles 80% of the workflow most companies need. Keep DocuSign or similar for signatures.
5. Reporting + close
Saved searches and SuiteAnalytics are the features customers most miss. Replacement: a Postgres replica, dbt for transformations, Metabase or Lightdash for self-serve. The accountants who spent two days a month wrangling NetSuite saved searches will spend two hours a month writing SQL after one training session.
What to NOT replace
Statutory tax filings. Payroll. ASC 606 revenue recognition for complex SaaS billing. International compliance modules. The logic in those areas is genuinely worth subscribing to and changes every quarter; building them yourself is a five-year project that pays back never.