Case study · Manufacturing

SF Dyes: Odoo 13 to 18 migration with barcode integration and custom vendor reporting

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.

Published Updated

Outcome

13 → 18five major Odoo versions in one migration, with full data integrity
Client
SF Dyes
Industry
Dye manufacturing
Modules
Barcode, rewritten custom modules, custom QWeb vendor reports
Previous system
Odoo 13
Engagement
Version migration, Odoo 13 → Odoo 18

Before · several years on Odoo 13

The situation

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.

Odoo 13 out of active maintenance

Version 13 had left active maintenance, while version 18 offered improvements in performance, UI, and manufacturing features.

No room for extended downtime

The move could not disrupt a manufacturing operation that could not afford to stop for long.

Custom code built over several years

Custom modules and reporting workflows specific to SF Dyes' vendors sat on top of Odoo 13, and all of it had to keep working.

Years of records to carry across

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

What we found

Most of the risk sat in custom work, and the migration was also a chance to add what version 13 did poorly.

Every custom module needed rework

Each module had to be assessed, rewritten where necessary, and tested against Odoo 18 before any production cutover.

Vendor reports did not carry over

The existing reports did not translate directly and had to be rebuilt to the data formats SF Dyes' vendor relationships required.

A chance to add barcode scanning

SF Dyes wanted scanning in inventory and production. Odoo 18's barcode module supports it natively, and more fully than version 13 did.

Data integrity had to come first

So the database moved first, and every stage had defined exit criteria before the next one began.

Five stages · data first

What we did

Data first, then code, then the new features, then a parallel run against live Odoo 13 before cutover.

  1. Stage 1

    Database migration

    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.

  2. Stage 2

    Custom code rewrite

    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.

  3. Stage 3

    Barcode integration

    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.

  4. Stage 4

    Custom vendor reports

    Custom QWeb reports for purchase orders, delivery documents, and production batches. Each was checked against the vendor's expected format before deployment.

  5. Stage 5

    Parallel testing and go-live

    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.

Project at a glance

  • Five major versions, 13 to 18, in one migration
  • Every historical record verified against the source database
  • Parallel run against live Odoo 13 before cutover
  • Our team on hand through the first production week

Running an older Odoo version?

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 call

After cutover

Outcomes

v13→v18Clean migration, full data integrityEvery historical record verified against the Odoo 13 database after migration
ZeroOperational disruption at go-liveCutover in a planned low-activity window; vendor relationships were unaffected
Day 1Barcode scanning liveScanning at receiving, production, and dispatch from go-live
AreaBeforeWith Odoo, configured by us
Odoo versionOdoo 13, out of active maintenanceOdoo 18, with an upgrade path ahead
Custom modulesBuilt on the version 13 frameworkRewritten for 18, behavior checked
Stock entryManual data entryBarcode scans at receiving and dispatch
Vendor reportsWould not translate to version 18Rebuilt in QWeb to each vendor's format
Historical dataYears of records on Odoo 13Every record carried across and verified

Inventory accuracy improved and warehouse data entry fell from day one, though neither was measured.

Scope delivered

Modules deployed

Six workstreams, delivered as one migration.

  • Database migration (13 → 18)
  • Custom module rewrite
  • Barcode integration
  • Custom vendor reports (QWeb)
  • Parallel testing and UAT
  • Go-live support

Stuck on an older Odoo version?

The first call takes 30 minutes.

Or email sales@octagotech.com