Odoo services · Odoo Upgrade Services
Odoo upgrades rehearsed on a copy, cut over with a way back.
Every Odoo release moves the platform forward and leaves somebody's customisations behind. An upgrade is routine when custom code lives in separate, tested modules — and a rescue job when it was patched into core. We start by finding out which of those you have, then run the entire upgrade on a copy before your production database is ever touched. The version changes; the way your team works does not have to.
Your implementation partner
A partner, not a licence reseller.
We are not chasing licence volume — we design, build and stay accountable for systems that companies run their operations on. The consultant who scopes your project stays through go-live and the support that follows, and everything we commit to is written into a fixed scope per phase.
—— How we work
What the engagement looks like.
Upgrade assessment
We inventory every custom module and scan it against the target version's deprecated APIs. You get a written list of what ports cleanly and what needs rework — before anything is quoted.
Staged upgrade on a copy
The full upgrade runs first on a copy of your database. Broken views, failed data scripts, misbehaving reports — all surface where they cost nothing.
Porting and parallel validation
We port custom modules with tests, then run your key flows — quote-to-cash, month-end close — on old and new side by side until the numbers match.
Cutover with a rollback point
Go-live is scheduled around your business, with a snapshot taken at the moment of cutover. If anything unexpected appears, you can be back on the old version the same day.
—— Why us
What you get that you would not elsewhere.
We fix what made it hard
Upgrades are routine when custom code sits in separate, tested modules. Where yours does not, we rebuild it that way during the port — so the next upgrade costs less than this one.
One consultant, assessment to cutover
The person who scans your modules is the person on call at go-live. Nothing is lost in a handover between a sales team and a delivery team.
Proven on your data first
Sign-off comes from your team comparing real documents on both versions — the same invoices, the same stock moves — not from our test checklist.
—— Risks
What usually goes wrong — and how we prevent it.
The in-place upgrade gamble
Running upgrade scripts straight on production means discovering breakage with no way back. Every upgrade we deliver is rehearsed on a copy and cut over with a snapshot to return to.
Custom code pinned to an old version
Modules patched into core, or written without tests, fail quietly on the new API — often in ways nobody notices until month-end. The assessment finds them first, and the port rebuilds them as separate, tested modules.
Testing that skips the close
Most upgrade testing checks that pages load, then declares victory; the real failures appear at the first month-end. We run a full close on the upgraded copy before cutover is even scheduled.
—— Pricing
What this costs.
The assessment is a fixed fee and produces your module inventory; the upgrade itself is then quoted as a fixed price from that inventory — a number based on your code, not a market average.
—— Editions & hosting
Community, Enterprise, and where it runs.
The licence and the hosting are separate decisions, and both are yours — we implement either edition and hand over whichever infrastructure you choose.
$0 licence
Odoo Community
Open source and free to license. Covers sales, purchasing, inventory, invoicing, manufacturing and more. You pay for implementation, not rent.
Per user, billed by Odoo
Odoo Enterprise
Adds studio, advanced accounting and localisations, mobile apps and official support. Billed by Odoo directly — never marked up by us.
Odoo.sh · VPS · on-premise
Your server or the cloud
Odoo.sh, a VPS we manage, or your own hardware. We recommend based on your compliance and budget, then document the choice so it stays portable.
—— FAQ
Questions teams ask about this service.
We are on Odoo 14 or older. Can we jump straight to the latest version?
Yes. Odoo's migration scripts run version by version internally, but that is our problem to manage — you test the start point and the end point. Older versions mostly mean more deprecated APIs in custom code, and the assessment prices that before you commit to anything.
How much downtime should we expect at cutover?
Production runs untouched through all the rehearsals — the copies do the suffering. The final cutover is usually scheduled overnight or over a weekend, and the snapshot taken at that moment keeps the old system available if anything forces a rollback.
We run Odoo Community. Can you still upgrade us?
Yes. Odoo's own upgrade service covers Enterprise databases; Community upgrades go through the open-source OpenUpgrade path, which we handle. Either way, porting your custom modules is our work, and on Community the licence stays at $0.
Do we actually have to upgrade?
Odoo supports its three most recent versions, so staying put eventually means running without security fixes — and every version you skip makes the eventual jump bigger. That said, if your system is stable and lightly connected, waiting one cycle can be a defensible choice. The assessment tells you what the jump costs, so the decision is made on numbers rather than nerves.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.