Odoo Migration & Modernization · Case study
Live Migration of a Heavily Customized Odoo 11 System to Odoo 18
Seven-month Odoo 11 to 18 migration for a 100+ user UK company, including custom module porting, repeated live-data cycles, accounting, BI and performance redesign.
Project context
UK multi-company enterprise operations
A UK-based company had used Odoo 11 since its original release. The ERP supported more than 100 users across several legal entities and covered CRM, sales, purchasing, inventory, manufacturing, accounting and employee management.
Years of development had produced a large customized codebase, with particularly heavy Accounting and BI reporting logic. Odoo 11 was unsupported, important calculations could not run during working hours, and the production system continued receiving new transactions and process changes throughout the migration.
- Delivery
- Odoo Migration & Modernization
- Industry
- UK multi-company enterprise operations
- Period
- 2025–2026 · 7 months
- Confidentiality
- Client identity is withheld unless publication is approved.
ERPixel solution
How the work was approached
ERPixel ran a controlled seven-month migration to Odoo 18. The team analyzed and ported custom modules, redesigned performance-sensitive logic, adapted business processes and completed repeated code, database and synchronization cycles against evolving production data. The live Odoo 11 environment remained the operating system until the target was ready.
Implementation details
Architecture, workflows and reporting scope
Unsupported legacy-version assessment
A direct version change was not sufficient for a system that had evolved since the first release of Odoo 11. The migration started by mapping business-critical behavior, custom code, data and integrations.
- Odoo 11 architecture review
- Custom module inventory
- Accounting and BI dependency analysis
- Business-process mapping
- Target behavior in Odoo 18
Custom module porting and redesign
Each customization was evaluated against the Odoo 18 architecture. Required behavior was adapted or rewritten rather than mechanically copying legacy implementation patterns.
- Full custom-code porting
- API and framework adaptation
- Accounting logic migration
- BI reporting adaptation
- Retirement of legacy architectural constraints
Repeated database migration cycles
A single database conversion could not keep pace with an actively used ERP. The team repeatedly refreshed and migrated production snapshots as the target environment matured.
- Current database snapshots
- Schema and data transformation
- Multiple migration rehearsals
- Validation on each iteration
- Preparation for final production transition
Synchronization of evolving live data
New transactions appeared every day while business processes and custom functionality continued to change. Migration work therefore coordinated source-system evolution with the target code and database.
- Daily operational transactions
- Updated production data
- Changing business logic
- Repeated code and data alignment
- Preservation of new records between cycles
Performance redesign
The legacy environment depended on intensive background calculations scheduled outside working hours. The migration provided an opportunity to redesign affected logic for the modern Odoo platform.
- Accounting-calculation review
- BI workload review
- Removal of legacy bottlenecks
- Use of modern Odoo architecture
- Validation under representative operational load
Enterprise module scope
The target retained the applications required by the client’s operating model without adding modules that were not part of the architecture.
- CRM and Sales
- Purchase and Inventory
- Manufacturing
- Accounting
- Employees
- Payroll and Marketing excluded from the target scope
Seven-month cross-functional delivery
The migration involved approximately twenty analysts, developers, QA specialists and client key users coordinating technical conversion with business acceptance.
- 20-person project team
- Analysis and development
- Quality assurance
- Key-user validation
- Seven-month delivery program
Transformation
Before and after
The operational change delivered through the project.
Before
- The company depended on an unsupported Odoo 11 environment for business-critical operations.
- Accounting and BI customizations contained calculations too heavy to execute during normal working hours.
- Maintenance effort and instability risk increased as the custom codebase continued to evolve.
- New features were increasingly difficult to introduce within the legacy architecture.
- More than 100 users and several legal entities continued creating operational data throughout the migration.
After
- CRM, Sales, Purchase, Inventory, Manufacturing, Accounting and Employees operate on Odoo 18.
- Custom functionality was ported or rewritten for the modern target architecture.
- Performance-sensitive logic was redesigned so operational workloads no longer depend on the former heavy overnight calculations.
- Modern Odoo modules provide a supported basis for subsequent features and integrations.
- The codebase and operating model are easier to maintain than the accumulated Odoo 11 implementation.
Confirmed outcomes
What the project delivered
- 01
100+ user multi-company ERP migrated from Odoo 11 to Odoo 18
- 02
Large custom codebase analyzed, ported and adapted to the target architecture
- 03
Multiple code, database and evolving production-data migration cycles completed
- 04
Accounting and BI performance constraints redesigned for the modern platform
- 05
Seven-month program delivered with a 20-person cross-functional team
- 06
Supported Odoo foundation established for continued features and integrations
Technology and scope
What the delivery covered
- Odoo 11
- Odoo 18
- Odoo CRM
- Odoo Sales
- Odoo Purchase
- Odoo Inventory
- Odoo Manufacturing
- Odoo Accounting
- Odoo Employees
- Multi-company ERP
- Database migration
- Production-data synchronization
- Custom module porting
- Custom module rewrite
- Accounting customization
- BI integrations
- Performance redesign
- Migration rehearsals
- Business acceptance testing
Explore next
Related ERPixel expertise
Your project
Planning a similar transformation?
Talk with ERPixel about your processes, systems and delivery constraints.