Upgrade Odoo Community, test-drive the result before you pay.
v12 through v19, one or many engine hops, delivered with an audited integrity report and a hosted preview of your migrated database. Free readiness analyzer runs on your module list. No backup upload, free account.
Independent service. Not affiliated with Odoo SA. Operated by OpenEduCat Inc. (Delaware, USA); jobs processed on ephemeral VMs in EU data centers.
- From
- v12
- To
- v19
- Engine
- Purpose-built for CE
- Data centers
- Hetzner DE/FI
Three deadlines stack this year. Plan now, not under pressure.
v15 follows a year later. Enterprise customers on v14–16 already pay a 25% legacy surcharge (April 2026).
v17 dropped out of Odoo's rolling 3-major support window with that release. Migration coverage for v20 will not be production-ready until Q1–Q2 2027.
Roughly 11M of the 13M user base. None of whom have access to Odoo's official upgrade service, which is Enterprise-only.
Four steps. Every step is honest about what it can and cannot verify.
Start with a free analyzer. Only pay after you have driven the migrated database.
Free readiness report
Paste the output of a 30-line SQL query against ir_module_module. Instant verdict, hop chain, per-module coverage, credit estimate, price quote. Zero backup upload; a free OEC.sh account gates the analyzer.
Book a test migration
Upload your backup. Job runs on an ephemeral VM in the EU. Our engine executes the hop chain end-to-end; custom modules are quarantined per the report.
Test-drive the result
The migrated database is neutralized (no outbound email, external endpoints stubbed) and booted at a private URL with your credentials. Walk through your data in the target version.
Approve, receive production dump
Approve the report. Only then do the production credits deduct and the un-neutralized dump + filestore + Migration Report get released via signed URL. If the run cannot complete on your data, we cancel before the production charge fires.
Every hop chain from v12 to v19.
Mature paths run self-serve. Long-tail chains (v12–v15) run human-reviewed at launch. Coverage of newly-released Odoo versions typically lags the release by 6 to 11 months as migration scripts stabilize. Odoo 20 shipped on September 24, 2026, and v19 to v20 coverage will not be production-ready before Q1–Q2 2027.
| From | To | Hops | Maturity | Notes |
|---|---|---|---|---|
| v18 | v19 | 1 | supported | 96% complete, gaps only in peripheral hr/livechat modules |
| v17 | v18 | 1 | mature | Fully supported |
| v17 | v19 | 2 | supported | Two-hop chain via v18 |
| v16 | v18 | 2 | supported | Two-hop chain via v17 |
| v16 | v19 | 3 | supported | Three-hop chain |
| v15 | v19 | 4 | long-tail | Human-reviewed at launch |
| v14 | v19 | 5 | long-tail | v14 removed from Odoo.sh Oct 31, 2026 |
| v12–v13 | v19 | 6 | long-tail | Multi-hop; v13→v14 is the 'accounting apocalypse' hop |
v8 → v11 databases: quoted case-by-case.
The pre-v12 lane crosses Python 2→3 at v8→v9, a PostgreSQL 9.x jump, and several accounting/inventory rewrites. Enough moving parts that we don't publish self-serve pricing. Send us your version, DB size, and rough module list and we'll come back with a fixed quote and a realistic timeline. No obligation.
Four tiers. The analyzer places you.
Most Community Edition databases with light customization land in Tier 1. Databases with heavy custom code arrive at Tier 2 or 3.
Free Readiness Report
Paste your module list (30-line SQL query), get an instant verdict, hop chain, per-module coverage, credit estimate, and price quote. Email gates only the PDF export.
- Zero-upload: no backup required
- Per-module coverage against our engine's matrix
- Multi-hop chain recommendation
- Credit estimate + fixed price quote
Standard Migration
Self-serve for DBs where preflight shows ≥95% modules covered and no custom modules. Includes one free neutralized test migration, the verdict-level report, and a hosted test-drive of the migrated database.
- One free neutralized test run
- Hosted test-drive before you commit credits
- Full Migration Report (HTML/PDF)
- Production dump released only on your approval
Data Migration + Compatibility Report
For databases with custom or uncovered modules. Custom modules are quarantined: inheriting views/actions/crons/mail templates stripped, custom tables snapshotted separately. The report enumerates exactly what each quarantined module needs.
- Quarantine procedure documented per module
- Compatibility notes for the port work
- Same integrity report + test-drive
- Human review before delivery
Assisted Migration
Custom module code porting and pre-v12 legacy chains (v8–v11): the manual work no automated engine can do reliably. Fixed quote from the analyzer or a scoping call, confirmed by a human, with a published delivery slot. Invite-only until 10 automated jobs have shipped clean.
- Fixed quote from analyzer or scoping call
- Pre-v12 legacy chains (v8–v11) supported
- Published lead time (4–6 weeks)
- Handoff after test-drive acceptance
Credit packs, no subscription.
Credits track compute cost, so pricing tracks what a run actually consumes. Every new account gets 10 trial credits on signup, test runs only. Packs stack: buy another one anytime and the credits combine on the same account.
Valid 12 months from purchase. Already-consumed credits never expire.
Buy 30 creditsValid 12 months from purchase. Already-consumed credits never expire.
Buy 65 creditsValid 12 months from purchase. Already-consumed credits never expire.
Buy 120 creditsValid 12 months from purchase. Already-consumed credits never expire.
Buy 200 creditsA convenience premium for closing a shortfall of 1–2 credits, priced ~1.5× the smallest pack's per-credit rate on purpose. If you need 30+ more credits, buy another Trial pack ($299 · $9.97/cr). All packs stack on the same account.
Which pack fits your workload?
Run the estimator below for an exact credit count on your specific chain and DB size.
| Pack | Credits | Price | $/credit | Fits | Buy |
|---|---|---|---|---|---|
Trial pack | 30 | $299 | $9.97 | One small upgrade | Buy → |
Standard pack | 65 | $599 | $9.22 | A migration with retries | Buy → |
Team packBest value | 120 | $999 | $8.32 | A migration or two, with room to spare | Buy → |
Agency pack | 200 | $1,499 | $7.50 | Several migrations across projects | Buy → |
Top-up bundleAd-hoc | 5 | $75 | $15.00 | Closing a small shortfall on an existing pack | Top up → |
Which pack should you buy?
Tell us about your migration; we'll pick the cheapest pack that covers it.
Set your chain, DB size, and how many test runs you plan.
Size multiplier applies above 20 GB (×1.5) and 50 GB (×2).
Most jobs need 1-2 test runs before production.
30 credits · covers your job with 0 credits left over for future work (valid 12 months).
Buy 30 creditsEstimate only. The free analyzer produces a fixed price quote from your actual module list. This calculator uses the published rate card as a self-serve preview. Pre-v12 databases (v8–v11) are quoted case-by-case via the contact form.
Custom modules? Quoted case-by-case.
The credit packs cover data migration: registry loads, row counts, foreign keys, integrity checks. Porting the code of your custom or heavily-modified modules to the target Odoo version is separate manual work.
Send us your module list (or drop the Readiness Report into the message) and we'll come back with a fixed quote and a realistic delivery slot. No obligation, no automated pricing, because there isn't honest automated pricing for this kind of work.
- Fixed quote before we start
- Handoff after test-drive acceptance
- Published lead time on every quote
- Pre-v12 legacy chains too (v8–v11)
Share your source version, target version, DB size, and the shape of your customization. We'll reply with a fixed quote and a delivery slot.
Request a quoteReply within one business day.
We automate data. We never silently promise code.
Our engine covers Odoo's core modules and the most common community addons. Custom modules and Enterprise-only modules are outside its scope. The report tells you exactly what worked, what got quarantined, and what a human still needs to do.
Automated: core modules + covered community modules
Registry loads, row counts, foreign keys, constraints. Green/amber/red verdicts per section.
Automated: quarantine procedure for custom modules
Inheriting views/actions/crons/mail templates stripped; custom tables snapshotted separately; report enumerates what each needs.
Not automated: custom module code porting
That's Tier 3 (Assisted Migration) or your own developer/partner. We publish the exact scope so the handoff starts with a real report, not a blank slate.
Not verifiable by any tool: semantic checks
Tax report grids, stock valuation across the v13 SVL rewrite, analytic distributions across the v16 rewrite, community payroll modules. Report lists these up front under 'what we could not verify.'
You approve, then credits deduct.
Production credits deduct on acceptance, not before. If the job cannot complete, we cancel before the production charge fires and no credits leave your balance. Your original backup stays on your own storage throughout.
No post-acceptance refunds because approval is entirely in your hands.
Common questions about Odoo upgrades
Everything customers ask before running the analyzer, with straight answers.
Start with the free report.
Paste your module list. Get the verdict, the hop chain, the credit estimate, and the fixed price, in under a minute. No signup for the verdict itself.