Skip to content

Project Overview: CNF Odoo 13 to 18 Upgrade

Executive Summary

Community Natural Foods (CNF) is upgrading their Odoo ERP system from version 13 to version 18. This is a major upgrade spanning multiple versions that requires careful planning, module compatibility assessment, and systematic testing.

Project Scope

Current State

  • Current Version: Odoo 13 (production)
  • Custom Modules: 98+ custom modules developed over time
  • Key Systems: POS, Inventory, Accounting, eCommerce, Warehouse Management

Target State

  • Target Version: Odoo 18
  • Intermediate Step: Originally planned for Odoo 17, now targeting 18 directly
  • Timeline: Multi-phase approach with staging validation

Technical Architecture

Repository Structure

/Users/greg/projects/
├── CNFOdooCustomModules/     # Custom module repository
├── odoo_17/                  # Odoo 17 codebase (reference)
└── cnf_odoo_docs/           # Documentation repository

Module Categories

  1. Point of Sale (POS)
  2. pos_utils - Core POS utilities
  3. pos_promotions - Promotion management
  4. pos_returns - Return/refund handling

  5. pos_rest_api - REST API for POS integration

  6. Inventory & Warehouse

  7. cnf_stock_scheduler - Parallel scheduler optimization
  8. stock_planner - Stock planning for PFS team

  9. merp_* modules - VentorTech warehouse management suite

  10. Accounting & Finance

  11. account_3_way_update - Enhanced 3-way matching
  12. cnf_account_loc_costcenters - Cost center management

  13. account_payment_cpa005 - Canadian EFT payments

  14. eCommerce & Website

  15. theme_clarico_vega - Main theme (currently unused)
  16. emipro_theme_* modules - Theme components
  17. website_sale_uom - Unit of measure for web sales

Upgrade Challenges

Technical Debt

  • Modules developed across multiple Odoo versions
  • Mixed coding standards and patterns
  • Complex interdependencies between modules

Module Dependencies

  • 44 modules serve as dependencies for others
  • Circular dependencies in some cases
  • Third-party modules requiring vendor updates

Version Gap

  • Jumping from v13 to v18 (5 major versions)
  • API changes and deprecations
  • Database schema evolution

Success Criteria

  1. All critical business processes continue functioning
  2. Data integrity maintained throughout migration
  3. Performance equal or better than current system
  4. Zero downtime during cutover
  5. All customizations properly ported or replaced

Risk Mitigation

  • Staging Environment: Full testing before production
  • Module Analysis: Systematic review of each module
  • Dependency Mapping: Clear understanding of relationships
  • Phased Approach: Incremental validation and testing
  • Rollback Plan: Ability to revert if issues arise