When is Odoo 20 coming out?
Odoo 20 is expected to launch at Odoo Experience 2026, scheduled for September 24-26, 2026, in Brussels. General availability typically follows 2-4 weeks after the conference. The first stable production-ready patch usually arrives in October or November 2026.
Odoo 20 launches at Odoo Experience 2026 this September. It includes agentic AI, read-replica database scaling, built-in financial forecasting, and deeper automation across the platform. This is not a point release.
But here is what most Odoo partners won’t tell you: the upgrade itself is the easy part. The hard part is making sure your current system, your data, your workflows, and your team are actually ready for what Odoo 20 changes. In our experience across 50+ implementations, businesses that start preparing months ahead have far fewer problems at cutover than those who wait until release day.
This checklist covers everything from technical prerequisites to team training to go-live timing. Whether you are running Odoo 17, 18, or 19, use it to figure out where you stand and what needs to happen before September.
What’s expected in Odoo 20
Odoo SA hasn’t published official release notes yet. These predictions are based on Odoo Experience 2025 roadmap talks, beta partner previews, and community discussion on the Odoo forums.
Agentic AI
Odoo 19 introduced chatbot-style AI. Odoo 20 is expected to go further with autonomous AI agents that actually do things: generating purchase orders when stock runs low, scoring and routing leads without manual rules, reordering inventory based on sales velocity. Less “suggest” and more “just handle it.”
Read-replica database scaling
This one matters for larger organizations. Read-replica support means you can split database read traffic across multiple instances, so your 10,000-user deployment doesn’t grind to a halt when someone runs a big report. Most mid-market businesses won’t need this on day one, but it’s good to know it’s coming.
Built-in financial forecasting
Odoo 19 improved the accounting module significantly. Odoo 20 is expected to add predictive budgeting, scenario modeling, and direct government reporting. If you’ve been using third-party add-ons for financial planning, those might become redundant.
Smarter automation engine
The current automation system is rule-based: if X happens, do Y. Odoo 20’s automation is expected to learn from patterns. Instead of writing every trigger manually, the system adapts based on what actually happens in your workflows over time.
The checklist: 5 phases to get ready
Work through these between now and September 2026. You don’t need to do everything at once, but start with Phase 1 this month.
Phase 1: Figure out where you stand
You can’t plan an upgrade without knowing what you’re working with. This phase is about getting an honest picture of your current setup, including the parts nobody documented.
- Check your Odoo version. Are you on 17, 18, or 19? Each has a different upgrade path. Jumping multiple versions (say, 17 to 20) is doable but needs more planning and testing than a single-version hop.
- List every installed module. All of them: core, OCA, marketplace, and custom. Third-party modules are the number one cause of upgrade failures because they might not have Odoo 20 compatibility at launch.
- Document your custom code. Python overrides, JS widgets, QWeb report templates, API integrations. If it was customized, it needs review. This is usually the part that takes longest because nobody wrote it down the first time.
- Map every integration. Payment gateways, shipping carriers, eCommerce platforms, banking feeds, EDI connections, custom APIs. Each one needs a compatibility check against Odoo 20.
- Check your database size. Run
SELECT pg_size_pretty(pg_database_size('your_db'))in PostgreSQL. If you’re over 50GB, you need to plan for longer migration windows. - Review your server specs. Odoo 20’s read-replica and AI features may need more resources than your current setup provides. Write down your CPU, RAM, storage, and PostgreSQL version now so you have a baseline.
Phase 2: Get your tech stack ready
This is where upgrades succeed or fail. Most problems we see come from skipping this phase or rushing it.
- Get to Odoo 19 first. Odoo’s upgrade tooling works best for single-version jumps. If you’re on 17 or 18, plan an intermediate upgrade to 19 before September. Bonus: you get access to Odoo 19’s AI features while you wait.
- Update PostgreSQL to 16+. Odoo 20 will likely require PostgreSQL 15 or 16 minimum. Run
psql --versionto check. Plan this upgrade separately from the Odoo upgrade itself. - Update Python to 3.12+. Every Odoo version raises the minimum. Odoo 20 will drop support for older Python versions, so make sure your server can run 3.12 or later.
- Contact your third-party module vendors now. Don’t wait. Ask every OCA module maintainer and marketplace app vendor about their Odoo 20 timeline. If something critical won’t be ready at launch, you need to know that months ahead, not days.
- Build a staging environment. Clone your production system completely: same version, same modules, same data volume, same integrations. This is your test bed for everything that follows.
- Run the upgrade script on staging. When the Odoo 20 beta becomes available (probably August 2026), use Odoo’s official upgrade platform to test-migrate your staging database. Write down every error and warning.
- Port your custom modules. Expect changes in ORM methods, the web framework, QWeb templates, and JavaScript Owl components. Budget 2 to 4 weeks depending on how much custom code you have.
- Test every integration. Run each API connection against your Odoo 20 staging instance. Watch for authentication changes, deprecated endpoints, and new rate limits.
Phase 3: Clean your data
Odoo 20’s AI features only work well with clean data. Garbage in, garbage out applies doubly when the system is making decisions on its own.
- Merge duplicate records. Duplicate contacts, products, and vendors confuse AI agents because the system can’t tell which record is the real one. Clean these up before the upgrade, not after.
- Standardize your naming. Product names, customer categories, warehouse locations, chart of accounts. If your team has been naming things inconsistently for years, now is the time to fix it. AI pattern recognition breaks when “Widget A” and “widget-a” and “Widget Type A” are all the same product.
- Archive old records. Products you stopped selling two years ago, contacts who never responded, completed projects from 2023. Archiving reduces your database size (faster upgrades) and keeps the AI focused on current data.
- Verify your financials. Run a trial balance. Make sure open invoices match bank statements. Check your chart of accounts for orphaned entries. Odoo 20’s forecasting is only as accurate as the historical data behind it.
- Back everything up. Full database backup including filestore, stored offsite. Test restoring it. This is non-negotiable before any upgrade work starts.
- Document custom fields and relations. Every custom field, computed field, and relational override needs to be checked against Odoo 20’s updated data model. If you don’t have a list, make one now.
Phase 4: Prepare your team
Odoo 20’s biggest changes (agentic AI, smarter automation) mean your team needs to work differently. It’s not about learning where the new buttons are. It’s about trusting the system to do things that used to require manual intervention.
- Pick one upgrade champion. One person who owns the project from start to finish. They coordinate between departments, track progress on this checklist, and are the main contact for your Odoo partner.
- Document how people actually use Odoo today. Not the process documentation from your original implementation. How your team actually works. This becomes your baseline for measuring what Odoo 20’s AI can take off their plates.
- Identify what the AI should handle. Go through your workflows and flag the repetitive stuff: PO generation, lead assignment, inventory reordering, invoice matching, customer follow-ups. These are candidates for Odoo 20’s agentic AI.
- Schedule training time. Budget 2 to 3 days for power users and a day for everyone else. The training focus should be on when to trust the AI and when to override it, not just feature walkthroughs.
- Tell everyone what’s happening. Share the upgrade timeline with every department head. Include expected downtime, feature changes that affect daily work, and who to call if something breaks in the first two weeks.
- Write a rollback plan. Define what would trigger a rollback to the previous version. Include the procedure, who’s responsible, and how you’d communicate it. You probably won’t need it, but having it written down means you won’t panic if something goes sideways.
Phase 5: Plan the actual go-live
Everything above is preparation. This is the part where you pick a date and commit. Don’t rush it. A delayed upgrade beats a botched one every time.
- Aim for Q4 2026 or Q1 2027. Don’t upgrade on release day. Wait for the first stable patch, which usually lands 4 to 6 weeks after release. November 2026 is the earliest reasonable window. January 2027 is safer if you can wait.
- Pick a quiet weekend. Avoid month-end closes, year-end, tax filing deadlines, and peak sales periods. A Saturday cutover with Monday as a buffer day works well for most businesses.
- Keep the old system accessible for two weeks. Set it to read-only so your team can cross-reference data and catch anything that migrated incorrectly. This is cheap insurance.
- Define what “success” looks like before you start. All users can log in. Core workflows complete without errors. Financial reports match the old system. Integrations sync. No data loss. Test all of this on staging before touching production.
- Budget time for feature adoption after go-live. The upgrade is step one. Getting value from agentic AI, financial forecasting, and the new automation engine is step two. Plan 4 to 8 weeks post-upgrade specifically for configuring and learning the new features.
Upgrade or start fresh?
Not every business should upgrade their existing system. Sometimes starting over delivers more value.
Upgrade if
You’re on Odoo 18 or 19. Your custom modules are documented and maintained. Your data is reasonably clean. Your team knows the system. You want to keep your existing configurations, reports, and permissions. Budget or timeline is tight.
Start fresh if
You’re three or more versions behind (Odoo 14, 15, or 16). Your system has accumulated years of abandoned customizations. Your business model has changed fundamentally since the original implementation. You want to redesign workflows around Odoo 20’s AI from scratch.
Timeline at a glance
Now through June
Assess your current system. Clean your data. Get to Odoo 19 if you’re behind. Contact third-party module vendors about their Odoo 20 plans.
July and August
Set up staging. Start testing with the Odoo 20 beta or RC when it drops. Port custom modules. Verify all integrations still work.
September
Odoo 20 drops at Odoo Experience (Sept 24-26, Brussels). Review the final release notes. Finalize your upgrade plan and schedule the production cutover.
November onward
Production upgrade after the first stable patch. Parallel operations for two weeks. Train your team on the new AI features. Then start optimizing.
How Solvync runs upgrade projects
We use the same SYNC Framework for upgrades that we use for fresh implementations
Scope
We audit your Odoo environment, map every module and customization, flag the risks, and give you a report with a realistic timeline and cost estimate. No surprises later.
Yield
We design the upgrade path: what to migrate, what to rebuild, which custom modules to port. Then we set up staging and start testing before anything touches production.
Navigate
We run the production upgrade during your scheduled window, validate the data, train your team on what changed, and stay on call for the first two weeks.
Cultivate
After you’re stable, we help you actually use Odoo 20’s new capabilities: configuring AI workflows, setting up forecasting, building the automation that makes the upgrade worth it.
Common questions about Odoo 20
What is the Odoo 20 release date?
Odoo 20 is expected to launch at Odoo Experience 2026, which runs September 24-26 in Brussels. General availability usually follows 2 to 4 weeks after the conference. The first stable patch that’s safe for production typically arrives in October or November.
Can I skip from Odoo 17 straight to 20?
You can, but we don’t recommend it. Multi-version jumps have a much higher risk of data migration problems and module breakage. We tell clients to upgrade to 19 first, then go from 19 to 20 once it’s stable. Two smaller upgrades are less risky than one big one.
What does an Odoo 20 upgrade cost?
It depends on where you’re starting from. A single-version upgrade (19 to 20) for a mid-sized business with moderate customization typically runs $5,000 to $25,000 CAD. Multi-version jumps or heavily customized systems cost more. Get in touch for an estimate based on your actual setup.
Will my third-party modules work?
Not automatically. Every third-party module needs to be updated by its developer for each new Odoo version. Well-maintained OCA modules usually get Odoo 20 ports within 2 to 3 months of release. Less active modules might take longer, or never get updated. This is why we tell everyone to contact their vendors early.
What does “agentic AI” actually mean?
Regular AI suggests things. Agentic AI does things. In Odoo 20, that means AI agents that can create purchase orders when inventory is low, route leads to the right salesperson, draft customer emails, and trigger workflows without waiting for someone to click a button. It’s the difference between an assistant that says “you should reorder” and one that just places the order.
How long does the upgrade take?
For a single-version upgrade, plan on 4 to 8 weeks total: a week or two for assessment, 2 to 3 weeks for staging testing and porting custom code, then a week or two for production cutover and stabilization. The actual downtime during cutover is usually 4 to 12 hours depending on database size.
Should I wait for Odoo 20 or just implement 19 now?
If you don’t have Odoo yet, implement 19 now. Six months without an ERP costs more than upgrading from 19 to 20 later. Your team gets trained, your processes get documented, and when Odoo 20 arrives, upgrading from 19 is straightforward.
Can Solvync handle this in Calgary or Edmonton?
Yes. We’re based in Calgary and work with businesses across Calgary, Edmonton, and the rest of Alberta. We do the full upgrade: readiness assessment, staging testing, custom module migration, production cutover, training, and post-upgrade optimization. Book a free assessment if you want to get started.
Get started
We’ve done 50+ Odoo implementations and we’ve seen what happens when businesses prepare early vs. scramble at the last minute. The difference is real. If you want help figuring out where your system stands and what needs to happen before September, book a free readiness assessment. We’ll look at your setup and build an upgrade plan that actually fits your timeline.