Odoo versions · Odoo 16
Odoo 16: new features, end of support and migration
Released in October 2022, Odoo 16 is the version of speed and new applications: Knowledge, dashboards, unified loyalty. Its support ended in September 2025.
This page presents what Odoo 16 brought, domain by domain, based on the publisher's release notes and the source code. It then reviews the support of Odoo 16 today and the migration to Odoo 19 or Odoo 20. If you searched for "Odoo 16 new features" or "Odoo 16 end of support", everything is here.
Odoo 16 at a glance: dates, editions and performance
Short answer: Odoo 16 was released in October 2022 and its support ended in September 2025. It comes in a Community edition (LGPL) and an Enterprise edition; the spreadsheet engine became open source under LGPL with this version.
Where Odoo 15 laid the technical foundations, Odoo 16 mainly launched new applications and sped everything up: the publisher reports noticeably faster pages in the back office and in the online store alike, thanks to the rewrite of list, kanban and form views with the OWL framework.
- New applications: Knowledge, spreadsheet-based dashboards, a unified loyalty programme and an onboarding assistant for new companies.
- Hosting: Odoo Online, Odoo.sh and dedicated server. Odoo Online and Odoo.sh no longer accept this version today.
- Enterprise edition: Knowledge, Appointments, Sign, Documents, full Accounting and Planning remain reserved for the paid edition.
What Odoo 16 brought, application by application
Every feature listed appears in the official Odoo 16 release notes or in a module of its source code.
Accounting
Bank reconciliation rewritten with a new matching screen. Multiple analytic plans instead of analytic tags. Credit limit per customer, cash discounts compliant with local legislation, Storno accounting and fully redesigned financial reports.
Sales and subscriptions
A single loyalty programme for coupons, promotions, gift cards and eWallets, shared between Sales, Point of Sale and eCommerce. Delivery status visible on the order. The subscription becomes a recurring sales order.
CRM and marketing
Closing comment on a lost opportunity, duplicate detection by phone number, recurring revenue totals at the top of kanban columns. Chatbots in the website live chat.
Inventory and logistics
Transfers batched automatically by contact, carrier or country. Mandatory backorders per operation type, richer reception report, repair created straight from a return. Sendcloud connector for European carriers.
Purchasing
Redesigned calls for tenders: alternative requests for quotation and comparison of supplier offers on a single screen. Difference between invoiced price and ordered price taken into account in valuation.
Manufacturing
Splitting and merging manufacturing orders, overview of bills of materials and orders with lead times and availability, dependencies between operations, import and export of the master production schedule.
Human resources
Skills carried over from recruitment, automatic CV reading, interviewer access limited to the applications of their job position. Hourly cost of employees and onboarding plans per department.
Website and eCommerce
Grid layout, dedicated editing of the mobile version, Plausible audience statistics. In-store pickup with on-site payment, Apple Pay and Google Pay express checkout, automatic abandoned cart reminders.
Point of Sale
Loyalty, coupons and eWallets at the till. Invoices issued on closed sessions and requested from the customer portal. Margins and costs hidden from sales staff when needed.
Project and services
Project milestones linked to tasks, invoicing when a milestone is reached, resource allocation progress bar in the Gantt, recurring tasks scheduled automatically.
Knowledge
New documentation application: nested articles, real-time collaborative editing, clickable table of contents, trash with a grace period. It feeds the Helpdesk help centre.
Dashboards
Dashboards built on the spreadsheet engine: gauges, KPIs, global filters, accounting and financial functions and XLSX file conversion.
Interface, technology and personal data
- Views rewritten in OWL: list, kanban, form, graph and pivot share a new browser-side data model. This is where the speed gain comes from.
- Collaborative editor: rich text fields can be edited by several people at once, in Knowledge as in project tasks.
- Command palette: enriched with new actions and a broader search.
- Gantt dependencies: available on every Gantt view, not only in Project.
- GDPR: lookup of personal data by email or phone across the whole database and rules to clean or merge duplicates.
- Email: OAuth authentication for Outlook and Gmail servers, several languages installed at once.
Odoo 16 end of support: where do things stand today?
Short answer: Odoo 16 has received no security fixes since September 2025. The publisher maintains the three latest major versions: Odoo 20, Odoo 19 and Odoo 18.
On Odoo Online and Odoo.sh, the platform requires a supported version: an Odoo 16 database has to migrate and the timeline is agreed with the host. On a dedicated server, the database keeps running and you keep control of the date.
On a dedicated server, the risk is measured by the exposure of the database and the sensitivity of the data: an online store, a customer portal, payroll or health data call for a short-term migration. An internal database behind a VPN leaves more time. In every case, it is better to plan the migration than to endure it: bank connectors, carriers and third-party modules are no longer published for Odoo 16 and e-invoicing is carried by the supported versions.
Migrating Odoo 16 to Odoo 19 or Odoo 20: the method
1
Mapping
Installed modules, custom developments, third-party modules and interfaces. The volume of custom code dictates the duration of the project.
2
Decisions
Three jumps to Odoo 19 (17, 18, 19), four to Odoo 20. For each custom module we decide: port it, replace it with the standard or drop it.
3
Dry run
Each jump is run on a copy and checked: accounting, stock, open documents, then validation by your key users.
4
Go-live
During a quiet period, with teams trained on the target version's screens. The full method is described on the Odoo migration page.
Points to watch when migrating from Odoo 16
- Odoo 17 interface: the first jump changes the look of every screen. Plan a short hands-on session for users, even though processes stay the same.
- Project tasks: Odoo 17 adds states to tasks (in progress, changes requested, approved, done, cancelled). Custom kanban stages need a review.
- Notes: the Notes application becomes To-do in Odoo 17; personal notes are converted.
- Website: from Odoo 18 onwards, the /odoo prefix is used by the back office. Public pages under that path must be moved.
- Custom developments: native views, fields and methods evolve with every jump. A module written for Odoo 16 is reviewed in full.
- Arriving in Odoo 20: access rights, document printing and field service need checking, as detailed on the Odoo 20 page.
The Odoo 19 changes, artificial intelligence, guided accounting closing and ESG tracking, are presented on the Odoo 19 page.
Frequently asked questions about Odoo 16
No. Its support ended in September 2025. Only Odoo 20, Odoo 19 and Odoo 18 receive fixes from the publisher.
The Knowledge application, spreadsheet-based dashboards, the unified loyalty programme, the new bank reconciliation, analytic plans, redesigned calls for tenders and an overall speed gain from the rewrite of the views.
On Odoo Online and Odoo.sh, the platform requires a supported version: the migration is planned with the host.
On a dedicated server, yes: the database keeps running. The publisher no longer issues security fixes, so the risk depends on the exposure of the database and the sensitivity of the data. We advise planning the migration rather than enduring it.
Three to Odoo 19 (17, 18, 19), four to Odoo 20. Data is migrated version after version; your users only discover the target version.
Many are no longer published for Odoo 16. We check each one for availability on the target version or whether the standard now covers the need, which often lightens the database.
With a review of the database and the custom developments. It starts with a thirty-minute conversation, then continues with an audit.
Which path from Odoo 16?
Thirty minutes to assess the volume of custom developments to port from Odoo 16 and set the right time to migrate.