Odoo 13 out of active maintenance
Version 13 had left active maintenance, while version 18 offered improvements in performance, UI, and manufacturing features.
Case study · Manufacturing
SF Dyes, a dye manufacturer, had run Odoo 13 for several years with its own custom code and vendor reporting. We moved it to Odoo 18 in five stages and added barcode scanning on the way.
Outcome
Before · several years on Odoo 13
SF Dyes had run Odoo 13 long enough to build custom code and vendor-specific reporting on top of it. With version 13 out of active maintenance, moving was the clear call.
Version 13 had left active maintenance, while version 18 offered improvements in performance, UI, and manufacturing features.
The move could not disrupt a manufacturing operation that could not afford to stop for long.
Custom modules and reporting workflows specific to SF Dyes' vendors sat on top of Odoo 13, and all of it had to keep working.
Purchase orders, manufacturing orders, inventory movements, and accounting entries all had to arrive intact.
Python API patterns, ORM behavior, view definitions, and module structures all changed across the five versions from 13 to 18.
Discovery
Most of the risk sat in custom work, and the migration was also a chance to add what version 13 did poorly.
Each module had to be assessed, rewritten where necessary, and tested against Odoo 18 before any production cutover.
The existing reports did not translate directly and had to be rebuilt to the data formats SF Dyes' vendor relationships required.
SF Dyes wanted scanning in inventory and production. Odoo 18's barcode module supports it natively, and more fully than version 13 did.
So the database moved first, and every stage had defined exit criteria before the next one began.
Five stages · data first
Data first, then code, then the new features, then a parallel run against live Odoo 13 before cutover.
The full database moved from 13 to 18 with data model mapping, field transformations, and integrity checks. Every historical record was verified against the source database before custom work began.
We audited every custom module and rewrote each one for Odoo 18: updated Python API calls, revised ORM patterns, and views rebuilt on the new frontend framework. Each was checked against its original behavior before sign-off.
Staff now scan product and lot barcodes at receiving, during production order steps, and at dispatch. Scanner hardware was tested and configured as part of go-live.
Custom QWeb reports for purchase orders, delivery documents, and production batches. Each was checked against the vendor's expected format before deployment.
The migrated system ran alongside live Odoo 13 for a defined period, with outputs compared and user acceptance testing by role. Cutover ran in a planned low-activity window, and our team stayed on hand through the first production week.
We migrate from any Odoo version with full data integrity. Tell us what you run, and we will scope it in a 30-minute call.
Book a discovery callAfter cutover
| Area | Before | With Odoo, configured by us |
|---|---|---|
| Odoo version | Odoo 13, out of active maintenance | Odoo 18, with an upgrade path ahead |
| Custom modules | Built on the version 13 framework | Rewritten for 18, behavior checked |
| Stock entry | Manual data entry | Barcode scans at receiving and dispatch |
| Vendor reports | Would not translate to version 18 | Rebuilt in QWeb to each vendor's format |
| Historical data | Years of records on Odoo 13 | Every record carried across and verified |
Inventory accuracy improved and warehouse data entry fell from day one, though neither was measured.
Scope delivered
Six workstreams, delivered as one migration.
Keep going
Multi-level BOMs, routings, work centers, make-to-order and make-to-stock, and real-time costing.
Odoo for manufacturing ServiceVersion upgrades with custom modules reworked and every record checked before cutover.
Odoo upgrade services ArticleThe drivers behind the price of an upgrade, what Odoo's own upgrade service covers, why waiting makes it bigger, and how to make it smaller.
Odoo upgrade cost
The first call takes 30 minutes.
Or email sales@octagotech.com