If you're staring at a NetSuite renewal and trying to build a NetSuite-to-Odoo business case your CFO will sign, this is the template. It's built for the Controller or finance lead who has to make the case upward, not for the CFO reading it cold. del.ai builds and sells NetSuite-to-Odoo migrations, so read the numbers below with that in mind and check them against your own contract before you present anything. We were founded in 2026 and have not completed a customer migration yet, so where this memo describes how a migration runs, it is describing what we contract to, not a delivery history. What follows is a business case for ERP migration structured to survive the three questions every CFO asks: why now, where's the funding, and what happens if it breaks.
A verbal pitch dies in the room. A memo survives because your CFO can forward it, sit with it, and come back with real objections instead of a gut "no." This document is a structure, not a sales script: seven sections, each answering one question your CFO is going to ask whether you volunteer the answer or not.
The renewal clock is the forcing function here, and the reason is mechanical rather than psychological: the renewal check is the funding source, so a case that arrives before it is signed can be funded out of money already committed, and a case that arrives after it cannot. Every section below maps to a specific line of scrutiny: the problem, the cost of waiting, the funding source, the risk, and the timeline. Build it now, not the week the renewal notice lands.
Doing nothing has a cost, and the renewal clock imposes it whether or not you make an active decision. Oracle publishes no standard NetSuite uplift rate, so the only number that describes your renewal is the uplift clause in your own contract — read it before you model anything, and use del.ai's modeling assumption of 8% a year only as a placeholder until you have your own figure. The direction of travel is at least well documented at the market level: SaaStr's read of Gartner's 2026 software forecast attributes roughly nine of the fifteen points of forecast growth to price increases on software companies already own, rather than to new purchasing. If you are also carrying a board or CFO mandate to show AI ROI out of the existing software budget, with no new line available to fund it, that is the second pressure, and it lands on the same wallet every quarter you wait.
Source: SaaStr on Gartner's 2026 enterprise software forecast, 2026. ↗ | del.ai cost model, 2026
The NetSuite renewal business case problem statement comes down to one line: the escalator compounds whether you act or not, and the AI mandate isn't going away either. ERP systems tend to outlast the people who chose them, which means whatever you decide, or fail to decide, this renewal cycle probably sets your systems trajectory for years. We deliberately do not attach an average-tenure figure to that sentence: the number usually quoted for it does not appear in the report it is credited to. Your own contract term and your own history with the system are better evidence than an industry average anyway. That's the stake your CFO needs to see stated plainly, before the math and the risk section, not buried inside them.
Migrating from NetSuite to Odoo starts at a fixed ~$50k to build, plus hosting from ~$2k/mo to run, against a NetSuite renewal you would otherwise pay in full with nothing owned at the end of it. Both figures are del.ai's own published prices, not an industry average. There is no platform licence as a third line item, because del.ai deploys Odoo Community under the LGPLv3 licence, which carries no per-seat subscription meter — worth stating to a CFO who is used to seeing user counts drive the renewal. That is the headline shape, not the full five-year model — the complete TCO breakdown, covering license, partner, SuiteApp, and headcount layers, lives in del.ai's stack-cost analysis rather than being rebuilt here. This template is built for companies spending $120,000 or more a year on NetSuite, with $200,000+ the more typical qualifying range. Below that floor the shape of the math still holds, but the build is likelier to need a custom quote than the starting price above.
Source: Odoo Community licensing under LGPLv3, 2026. ↗ ; del.ai published pricing and cost model, 2026
If your CFO wants the complete TCO breakdown, hand them two links instead of rebuilding the table here: The Real Cost of NetSuite Nobody Publishes and Odoo vs NetSuite: Honest Comparison for Mid-Market CFOs. Both walk through the license, partner, SuiteApp, and headcount layers that make up the real NetSuite bill, and both do it with more room than this memo has. This section's job is narrower: establish the shape of the trade, then point to where the detail lives. The shape is the argument. What a CFO is comparing is not sticker price against sticker price — it is a recurring check that compounds every cycle against a fixed cost that stops compounding once it is paid.
This is how to justify a NetSuite replacement to your CFO without asking for new budget, and it's the section that decides whether this memo gets a yes.
The migration is funded by spend your CFO has already approved, not a new budget line: the same NetSuite renewal check you would otherwise write covers it. That is the funding structure del.ai designed the offer around, not an outcome measured across a customer base we do not yet have. A fixed migration fee starting ~$50k, plus hosting from ~$2k/mo, replaces the license, partner retainer, and SuiteApp fees already leaving the building every year — spend that is, at the market level, trending upward at renewal rather than at initial purchase, per SaaStr's read of Gartner's 2026 software forecast, regardless of what you decide here. Then run it on your own inputs: current annual NetSuite plus ecosystem spend, minus twelve months of hosting, against a one-time fee. At the $120,000 spend floor this template assumes, that arithmetic clears the fee inside year one. It is arithmetic on your numbers, not a result observed on anyone else's.
Source: SaaStr on Gartner's 2026 enterprise software forecast, 2026. ↗ ; del.ai published pricing and cost model, 2026
Fill in your own numbers before you present this: current annual NetSuite plus ecosystem spend, minus new hosting cost, minus the migration fee, equals your year-one net position. Show that line as arithmetic your CFO can redo in front of you, using your contract rather than our assumptions — a case that survives being recalculated in the room is worth more than one that quotes somebody else's payback period. This section and the fill-in-the-blank framing above are what to bring.
Here's how your CFO overcomes each objection on this list, because these two questions kill more migration business cases than the funding math ever does.
Three levers address migration risk, and the memo should name all three explicitly rather than gesture at "we've de-risked it": parallel-run, fixed-price, and per-step rollback. Each one is a contract term your CFO can read before signing, which is the point of listing them rather than asking anyone to trust a delivery record. NetSuite stays live and the books of record do not move until a scheduled cutover weekend, so nothing is bet on an unproven system. The migration fee is fixed for qualifying migrations within the signed scope document, meaning del.ai absorbs cost overruns against that scope rather than passing them back. Each migration step is scoped to be documented and rollback-tested before cutover, so a failed step does not force a forward leap. On audit, the existing trail and full transaction history are migrated intact and your auditor still signs off on NetSuite books in year one, with the Odoo mapping walked through before cutover rather than explained after.
Source: del.ai migration methodology, 2026
Two objections do most of the damage in the room. "Will this break the business?" gets answered by parallel-run, fixed-price, and rollback, in that order; if the bar isn't met at any checkpoint, you stay on NetSuite, there's no forced leap. "What about our audit cycle?" gets answered the same way: nothing about the migration asks your auditor to certify an unproven system mid-cycle. For the fuller risk narrative your IT and audit teams will want, see NetSuite to Odoo Migration: Timeline, Risk, and What CFOs Need to Know.
The real decision in front of your CFO isn't ERP shopping. It's whether to keep renting the system of record or start owning it. This memo compares exactly two paths: renew NetSuite as-is, or migrate to Odoo with del.ai running the migration. It is not a multi-vendor evaluation, and if your team is genuinely running a broader ERP bake-off, this template isn't the right document for that conversation.
Path one, renew: you keep the license, partner retainer, and SuiteApp stack you already know, at a price that increases every cycle, and the AI-ROI mandate stays unresolved on the same closed system. Path two, migrate: the fixed migration fee and hosting cost replace that stack, and what you land on is Odoo Community under the LGPLv3 licence, running on infrastructure you can move off if you ever fire del.ai. That "own it" claim is checkable rather than rhetorical — the licence is public, and it is the reason there is no per-seat meter on the destination. The AI agents scoped into the migration are designed to run against a cleaned-up data model rather than NetSuite's accumulated customizations; they are at demo stage today, and the scope document, not this page, is where you should read what ships. Neither path is free of tradeoffs. Renewing is the lower-effort choice this quarter; migrating is the lower-cost choice over the renewal cycles ahead.
Your CFO is choosing a multi-year cost trajectory, not a single line item, and this section should say that in exactly those words. If the answer this cycle is genuinely "not yet," that's a legitimate outcome. Nothing about this template requires signing before you're ready; it requires that the decision, whichever way it goes, be made with the real numbers on the table instead of by default because the renewal notice arrived and nobody built the case in time.
"Approved" shouldn't feel like a leap into the unknown, so give your CFO the operational shape, not only the funding math, in this NetSuite renewal business case.
A NetSuite-to-Odoo migration is scoped at 90 days from kickoff to cutover for qualifying migrations within the signed scope document. Weeks one and two cover discovery, sandbox setup, and a feature-gap audit against current SuiteScript customizations and workflows. Weeks three and four build the sandbox out and map every NetSuite field to its Odoo equivalent. Weeks five through nine run the parallel-run window itself, where NetSuite and Odoo process the same transactions side by side so any discrepancy surfaces and is resolved before cutover rather than after it, with the auditor walkthrough folded into weeks seven and eight. Weeks ten to twelve cover cutover weekend and go-live, gated on the reconciliation result rather than on the date. NetSuite stays the system of record until that point, so nothing is bet on an unproven system before it has run against real production transactions.
Source: del.ai migration methodology, 2026
For the full week-by-week breakdown, see A 90-Day NetSuite to Odoo Migration, Week by Week.
One more thing worth noting to your CFO: negotiating or exiting the NetSuite renewal itself is a separate, parallel track from building this internal business case, and it's worth starting that conversation with your NetSuite rep before you've finished this memo, not after. The two tracks run side by side, not sequentially, so you're not stuck holding an approved memo with no negotiating power left on the contract you're trying to exit.
This is the NetSuite-to-Odoo business case in miniature: one page, seven sections, nothing else. Copy this structure directly into your own memo or slide.
A NetSuite-to-Odoo business case needs seven sections, in this order, and the structure is del.ai's own recommendation rather than a format measured against a body of approved memos: Problem, Cost of Inaction, Recommendation, Investment and Funding, Risk, Timeline, and The Ask. Problem states what is broken today in one paragraph your CFO already agrees with. Cost of Inaction quantifies what the renewal escalator and the unresolved AI mandate cost if nothing changes. Recommendation names the specific move: migrate to Odoo through a fixed-price partner. Investment and Funding shows the migration fee and hosting cost offset against NetSuite spend already being paid, so it reads as reallocation, not new spend. Risk names parallel-run, fixed-price, and rollback as the three mitigations. Timeline gives the 90-day phase breakdown for qualifying migrations within the signed scope document. The Ask states the specific decision and date needed.
Source: del.ai product scope definition, 2026
Copy this template:
PROBLEM
[One paragraph: what's broken today. NetSuite spend, consultant dependency, AI mandate with no funded path.]
COST OF INACTION
[One paragraph: renewal escalator over the next contract term, plus the cost of the AI mandate staying unresolved.]
RECOMMENDATION
[One sentence: migrate to Odoo via a fixed-price NetSuite-to-Odoo migration partner.]
INVESTMENT & FUNDING
[One paragraph: migration fee + hosting cost, offset against current NetSuite + ecosystem spend. State the net position.]
RISK
[One paragraph: parallel-run, fixed-price, per-step rollback. Name the audit-continuity answer if relevant.]
TIMELINE
[One paragraph: 90-day phase breakdown, cutover date, what stays live until then.]
THE ASK
[One sentence: the specific decision needed, and the date you need it by.]
Share the one-pager 24 hours before the conversation. Don't ambush a CFO with a seven-section memo in the meeting itself; give them time to sit with it and come back with real questions instead of a reflexive no.
Anticipate the three questions this article already answered: why now, where the funding comes from, and what happens if it breaks. If your CFO asks something this document doesn't cover, that's a signal to add a section, not to improvise an answer on the spot. Bring the two TCO articles linked in Section 2 as backup material if the conversation goes deep on the numbers, but don't lead with them. The one-pager from Section 7 is the leave-behind. Everything else is reference material for the follow-up questions.
If the answer is "not yet," ask what would need to be true for it to be "yes" next cycle: a lower spend threshold, a cleaner risk story, a specific budget event. Write that answer down. It's the input for the next version of this memo, and it turns a rejection into a defined path back to the table instead of a dead end.
Built for mid-market companies on NetSuite spending $120k+/yr with a renewal in the next 12 months. If you're not there yet, save this template. It'll still be right when you are.
30 minutes. We'll pressure-test the numbers in your version of this business case before you present it, line by line. No pitch. You walk out with a memo that survives CFO scrutiny, not a sales deck.