Version and edition
The exact release, whether it is Community or Enterprise, and whether it is an Odoo Online intermediate release. Read from the same endpoint the Odoo mobile app uses to introduce itself.
Free Odoo Health Check
Know exactly where your Odoo stands.
Paste your Odoo address. In about ten seconds you see the version and edition, the apps and custom modules installed, whether it still gets security fixes, and what an upgrade would cost.
- 13+ years of Odoo work
- 150+ ERP projects delivered
- 40+ Odoo specialists
- Read-only never logs in, never writes
Health Check
Check Your Odoo Instance
Works for Odoo Online, Odoo.sh and self-hosted instances that are reachable from the internet. If yours sits behind a VPN or a login wall, switch to manual entry and type what you know.
Odoo health check
Read-onlyPaste your Odoo address
Version, edition, hosting, modules, security and upgrade cost in one report.
- Read-only: never logs in, never writes
- Works for Online, Odoo.sh and self-hosted
- No email needed to see the report
Planning a new rollout rather than checking one? Estimate a project instead
erp.example.com
Needs attention
Odoo 16.0EnterpriseOut of support
Modules
187
Custom
7
Upgrade
from $3.4k
- Odoo 16 no longer receives security fixes
- Session cookie is missing the Secure flag
- Served over HTTPS, HSTS on
What We Check
Eight Things the Check Reads From Your Instance
Support status
Odoo supports three major versions at a time. The report says when your version leaves standard support, or when it already did, which is the date security fixes stop.
Hosting
Odoo Online, Odoo.sh or self-hosted, inferred from the host name, the release type and the web server that answers. This decides which upgrade path applies.
Installed apps and modules
The full list of installed modules on Odoo 16 and later, split into standard, Enterprise, community-published (OCA), App Store and custom. Earlier versions show the apps from the Website information page.
Custom modules
Every module we cannot match to Odoo's own source or to a published community module is listed as custom or third-party. That count drives most of the upgrade effort.
Security hygiene
HTTPS and HSTS, session cookie flags, whether the database manager is open to the internet, whether Odoo's built-in web server is exposed, and clickjacking headers on the login page.
Availability
Whether the instance answers, how fast the login page arrives, and whether the liveness endpoint Odoo added in version 15 reports healthy.
TLS certificate
Who issued the certificate, whether browsers trust it, and how many days are left before it expires and blocks every login.
What the check cannot see
Stated up front, so the report is never read as more than it is.
- Anything behind the login: users, data volume, record counts, database size.
- Studio customisations on Odoo Online (we only see whether Studio is installed).
- The size of each custom module. We assume a medium module until you tell us otherwise.
- Integrations with other systems, unless you enter them.
- Instances behind a VPN, IP allow-list or basic-auth wall.
Everything on this list can be entered by hand under Adjust, and the report recalculates.
How It Works
How the Odoo Health Check Works
You paste the address
Any form works: mycompany.odoo.com, https://erp.example.com/web/login, or a host name with a port. We resolve it, refuse anything that points at a private network, and follow the redirect to the real login page.
Our server asks Odoo the public questions
Eight requests, all without credentials: the version endpoint, the module list Odoo publishes to every visitor, the Website information page, the health endpoint, the database manager, the login page headers and a TLS handshake. Nothing is written, nothing is logged in.
The analyser classifies and prices
Each module name is looked up in the Odoo Community source, a live Enterprise module list and the community index OCA publishes to. Version dates, the support policy and the hour ranges in our estimator turn that into a status, a plan and a cost range.
You correct what we could not see
If a probe is blocked, or you know a module is bigger than average, change it in the adjust panel and the report recalculates. Instances we cannot reach at all get the same report from a short manual form.
Module classification is checked against the Odoo Community source (branches 12.0 to 20.0), a live Odoo Enterprise module list and the PyPI index OCA publishes to. Support dates follow Odoo's three-version policy. Costs are hours at our standard rate; the assumptions are printed under every figure.
Reading the Score
What the Health Score Means
The score is a weighted sum of five checks, computed only over the checks that could run, so a blocked probe lowers the confidence, not the score. Every point is listed under the score on your report.
- Version currency30 pointsFull points inside support and at most one version behind. Fewer when two or more behind, when support is ending within three months, and almost none once security fixes have stopped.
- Security hygiene30 pointsHTTPS, HSTS, Secure and HttpOnly session cookie, database manager hidden, web server not advertising a version. Scaled to the checks that could run.
- Customisation load20 pointsNo custom modules scores full. Each band of custom modules costs points because every one of them has to be migrated on every upgrade.
- Availability10 pointsThe instance answers, the login page arrives quickly from our server, and the health endpoint passes where the version has one.
- TLS certificate10 pointsTrusted and more than 30 days from expiry. Half points inside 30 days, none inside a week or when browsers do not trust it.
Healthy
80 to 100Supported version, sane hygiene, manageable customisation. Keep it patched and plan the next upgrade inside the support window.
Needs attention
55 to 79One or two things to fix: usually an ageing version, an exposed database manager or a growing custom code base.
At risk
Below 55Out of support, exposed, or carrying more custom code than one upgrade should. Worth a call this month, not next quarter.
Upgrade Paths
The Upgrade Path Depends on Where Odoo Runs
The report picks one of these for you. They differ in who runs the database upgrade and how custom code travels.
Odoo Online
Odoo upgrades the database itself and will not keep an unsupported version running. You request a test upgrade, validate the copy, fix what changed, then schedule production. There is no custom code to migrate; Studio customisations need a re-check.
Lowest effort: testing and configuration only.
Odoo.sh
An upgrade branch pulls an upgraded copy of the database automatically. Custom modules are ported in git, tested on the branch, and the merge to production runs the real upgrade. Enterprise subscription required, so the upgrade service is included.
Effort scales with the number of custom modules.
Self-hosted Enterprise
The database goes through upgrade.odoo.com (included in the subscription) and can jump several versions in one run. Custom modules are ported alongside, and a new server or container image is prepared for the target version.
Custom modules plus infrastructure.
Self-hosted Community
Odoo's upgrade service is not available for Community databases. OCA OpenUpgrade migrates one major version at a time, with custom and OCA modules at each hop. Alternatively, move to Enterprise and use the service.
Highest effort per version jumped; the report applies a Community factor.
Support Timeline
Odoo Version Support Dates
Odoo releases one major version a year and supports the three most recent. Standard support brings bug and security fixes; the paid extended support after it does not include security fixes. Months, not days: Odoo publishes the policy, not a calendar.
| Version | Released | Standard support ends | Status |
|---|---|---|---|
| Odoo 20.0Newest | September 2026 | September 2029 (planned) | Supported |
| Odoo 19.0Recommended target | September 2025 | September 2028 (planned) | Supported |
| Odoo 18.0 | October 2024 | September 2027 (planned) | Supported |
| Odoo 17.0 | November 2023 | September 2026 | Out of support |
| Odoo 16.0 | October 2022 | September 2025 | Out of support |
| Odoo 15.0 | October 2021 | October 2024 | Out of support |
| Odoo 14.0 | October 2020 | November 2023 | Out of support |
| Odoo 13.0 | October 2019 | October 2022 | Out of support |
Odoo Online intermediate releases (saas~17.4, saas~18.2 and so on) are upgraded by Odoo automatically and inherit the support window of their major version.
Why iVentureTeam
Why Have iVentureTeam Read Your Report
The team that built this check runs Odoo upgrades and migrations for clients. Ask for the written report and a Senior Odoo Consultant reads your findings, not a sales rep.
- 13+ Years
- 150+ ERP Projects
- 40+ Odoo Specialists
- 01
Read-only by design
The check never logs in and never writes to your database. What happens next is your call.
- 02
A consultant reads every request
Ask for the written report and a Senior Odoo Consultant reviews your findings and replies within 12 business hours.
- 03
Upgrade figures in writing
The range on screen is indicative. The figure we send after a short call is the one we work to.
Results
Odoo Upgrades We Have Delivered
Version jumps, module ports and re-platforming from the team that reads your report.
- Odoo · Enterprise Migration
Odoo 12 to 15 Enterprise With Minimal Downtime for EvoLogics
EvoLogics GmbH, a Berlin-based maker of underwater acoustic modems, positioning systems, and marine robotics founded in 2000, needed to move from Odoo 12 Enterprise to Odoo 15 Enterprise without disrupting operations. iVentureTeam migrated the database and custom business-flow code, tested end to end, and cut over with minimal downtime.
- major versions upgraded in one project (v12 → v15)
- 3
- data integrity preserved through migration
- 100%
- workstreams migrated: database + custom code
- 2
- cutover downtime at go-live
- <1 day
- Odoo 12 Enterprise
- Odoo 15 Enterprise
- Custom Module Migration
- Database Migration & Testing
- Odoo · Version Migration
Legacy Odoo Modules Moved to the Latest Version, Intact
Codequarters, an IT consultancy specializing in ERP, CRM, and MRP applications, needed its custom Odoo modules moved to the latest Odoo version. iVentureTeam ran a two-track Odoo migration — refactoring module code for the new framework APIs and migrating the database to the updated schema — so the system runs current, supported, and unbroken.
- Migration tracks delivered — module code and database
- 2
- Unified codebase running on the latest Odoo version
- 1
- Custom module functionality preserved post-upgrade
- 100%
- Records lost during schema migration
- 0
- Odoo
- Odoo Code Migration
- PostgreSQL Database Migration
- Odoo Migration · Retail
Migrating from Odoo 14 to Odoo 19 — and unifying 6 sales channels along the way
Migrated a heavily-customized Odoo 14 deployment to Odoo 19 while consolidating Shopify, Amazon and 4 retail POS terminals into a single source of truth.
- Stock accuracy
- 99.7%
- Recovered revenue
- $2.1M
- Channels synced live
- 6
- Lost SKUs in migration
- 0
- Odoo 14 → 19
- Shopify
- Amazon Seller
- POS
- Odoo · Migration & eCommerce
Two version jumps and a faster storefront for a sign-supply wholesaler
SF Plastic & Sign Supply, a wholesale distributor serving the sign manufacturing market, needed its aging Odoo 9 stack modernized. iVentureTeam migrated the business from Odoo 9 to 10, then to Odoo 12 with a redesigned storefront theme, integrated Braintree payments, implemented SEO modules, and took over Odoo.sh deployment and server management.
- major version migrations (v9→v10, v10→v12)
- 2
- Odoo versions spanned on one continuous dataset
- 3
- payment gateway (Braintree) live on the storefront
- 1
- hosting and deployments handled on Odoo.sh
- 100%
- Odoo 9
- Odoo 10
- Odoo 12
- Odoo Website / eCommerce
Common Questions
Odoo Health Check FAQs
How do I check which Odoo version I am running?
Paste your instance address into the tool above. Odoo answers a public version request with the exact release and edition. Inside Odoo you can also open Settings and scroll to the bottom, where the version is printed, or look at the About dialog from the user menu.
Is it safe to run this on my live instance?
Yes. The check only sends the requests any browser sends when it opens your login page, plus two read-only version calls and a TLS handshake. It never logs in, never posts data and never touches the database manager beyond asking whether the page exists. The whole scan is about eight requests.
How can you see my installed modules without logging in?
Odoo publishes the names of installed modules to every visitor so the web client can load translations. That is by design, not a leak, and it is complete from Odoo 16 onwards. Odoo 13 to 15 only list modules that ship translations, so the report marks those lists as partial. Odoo 12 and older do not list modules at all.
What counts as a custom module?
A module name that is not in the Odoo Community source for any version, not in Odoo's Enterprise module list, and not published to PyPI under the naming convention OCA uses. App Store vendors with a recognisable prefix are listed separately as third-party. Anything left is treated as custom, because it will need a code migration on every upgrade.
Why does the report say my database manager is exposed?
Because /web/database/manager answered. That page lets anyone try master passwords and, with the right one, back up, duplicate or drop your database. On a production server set list_db = False in odoo.conf and block /web/database/ at the reverse proxy for everyone except your own IPs.
How accurate is the upgrade cost?
It is an hour range at our standard rate, built from the number of majors jumped, the installed apps, the custom module count and size, community and App Store modules, Studio and integrations. Every line and every assumption is printed under the figure. The exact figure comes after a scoping call, in writing, and it usually lands inside the range.
My instance is on a VPN or an allow-list. Can I still use this?
Yes. Switch to manual entry and type the version, edition, hosting, apps and custom module count. You get the same support status, plan and cost range; only the security and availability checks need a reachable instance.
Should I upgrade to Odoo 20 now that it is out?
Rarely on release day. Odoo 20 needs a few months for its upgrade service, OCA ports and App Store modules to settle. Businesses on 17 or older should move to Odoo 19 now, which is supported until 2028; businesses on 19 can plan Odoo 20 for its first year. The report says which applies to you.
Do you keep the results?
Yes. We keep every address checked here with its result (host name, version, module counts, findings) so a Senior Odoo Consultant can prepare before a call, and we link it to your enquiry if you ask for the report. Where a check shows an instance is out of support or exposed, we may get in touch with the company that runs it. Results are never published or shared with anyone else.
Straight answers on safety, accuracy and what happens to your results. Anything else, ask a consultant directly.
Know Where Your Odoo Stands Before You Plan the Next Year
Run the check, read the report, and if the version, the findings or the cost raise questions, have a Senior Odoo Consultant walk through them with you.