Every NetSuite customer I've ever met has the same look when the renewal comes up. It's the look of someone reading a ransom note. The price goes up, the negotiation gets worse, and somewhere in Oracle's pricing department, someone is smiling.
So when a 60-person industrial distributor called me last year — $95,000 a year in NetSuite licenses, renewal jumping to $118,000 — and asked "is Odoo real?", I said yes. Then we did it. Here's the honest math, including the parts that hurt.
The Before Numbers
Let's be precise about what they were paying, because NetSuite pricing is a fog machine:
- Licenses: $95,000/year for 60 users (a mix of full and employee-center licenses), renewal quoted at $118,000 — a 24% jump with 30 days to decide. Classic.
- The hidden tax: $18,000/year in SuiteScript developer retainer, because every customization needed a specialist. Their "simple" approval workflow had 400 lines of SuiteScript that nobody fully understood.
- Real annual cost: ~$113,000, heading to ~$136,000.
The company did $28M in revenue. That's not a rounding error — it's a full-time employee's salary evaporating into license fees every year.
The Migration: What It Actually Cost
Odoo licenses: Odoo Enterprise, 60 users, all apps: approximately $1,900/month, so ~$23,000/year. That's not a typo. It's roughly one-fifth the NetSuite license cost.
Implementation services: $85,000 over 5 months. This covered process mapping, configuration, data migration, customizations (two — a commission module and an EDI connector), training, and go-live support. Could it have been cheaper? Sure, with a smaller scope. Could it have been more expensive? Easily, if we'd tried to replicate every NetSuite customization 1:1. We didn't. We asked "what's the business need" for each one, and half of them evaporated.
Internal cost: They assigned a project lead at 50% for 5 months. Call it $35,000 in loaded labor. Most companies forget to count this. Don't.
Year-one all-in: ~$143,000 ($23k licenses + $85k services + $35k internal). Versus the $136,000 NetSuite would have cost that year. Yes — year one cost MORE. Anyone who tells you migrations save money in year one is selling something.
Year two onward: ~$35,000/year ($23k licenses + ~$12k light support). Versus $125,000+ for NetSuite (assuming single-digit annual increases, which is generous — Oracle's track record suggests otherwise).
Break-even: month 14. Five-year savings: roughly $450,000. That's the math that matters.
What Broke (The Honest Part)
NetSuite's data export is deliberately miserable. Saved searches export fine for lists, but transactional history? We spent three weeks extracting clean open-item data. Oracle has zero incentive to make leaving easy, and it shows. Budget real time for this — it's the longest pole in the tent.
SuiteScript doesn't translate. Those 400 lines of approval workflow? We didn't port them. We rebuilt the business logic in Odoo's automated actions in a day. It turned out the complexity was accidental — years of patches on patches. The rebuild was better than the original. But the two genuinely complex customizations (commission calculations, EDI) took real development time. Custom code is custom code, whatever the platform.
The team needed 6 weeks to stop reaching for NetSuite. Muscle memory is real. For the first month, every question was "how do I do the NetSuite thing in Odoo?" The answer was usually "you don't — here's the Odoo way, and it's two clicks instead of six." By week six, the loudest skeptic told me the old system "felt clunky" when she had to log in for historical data. That's when I knew we'd won.
Reporting was the gap. NetSuite's saved searches are genuinely good, and power users missed them. Odoo's reporting is fine but different — we built five custom reports in the first month to close the gap. Budget for this explicitly. Don't let anyone tell you "the standard reports are enough." They're enough for standard businesses. You're not standard.
What I'd Do Differently
Start data cleansing on day one. We started in month two. Mistake. The dirty item master (duplicate vendors, dead SKUs, 2019 pricing) slowed every downstream step. Day one, parallel track, no exceptions.
Negotiate the NetSuite exit earlier. We gave notice late and paid two months of overlap. That's $20,000 for the privilege of running two systems. Start the exit conversation the day you decide to migrate.
Train on the client's real data sooner. We trained on demo data for the first sessions. Retention was poor. The moment we switched to their actual customers and products, everything clicked. Real data or it didn't happen.
Who Should (and Shouldn't) Do This
Do it if: your NetSuite renewal makes you angry, your customizations are mostly workarounds for things Odoo does natively, and you have an internal champion with real authority.
Don't do it if: you're deeply embedded in Oracle's ecosystem (PBCS, Oracle DB, the whole stack), your SuiteScript customizations encode genuine competitive advantage, or your team will mutiny at change. A migration the team sabotages costs more than any license.
The distributor? Eighteen months in, they're saving $90k a year, their team prefers Odoo, and the owner bought a boat. Okay, I made up the boat. But the $90k is real, and that's better than a boat — it's permanent.
David Strausser, Dead Brands LLC / Quaint Business Solutions
Want help with your ERP? Book a call — I'll run the honest math on YOUR NetSuite renewal before you sign it.
Deadbrands.co merch: "I survived a NetSuite renewal" shirts. Barely.
