Upgrade Your Odoo Modules to Version 13: Key Considerations for a Smooth Transition

Odoo is one of the most popular and fastest-growing ERP platforms in the market. Each new release introduces powerful features, performance enhancements, and UI improvements. Notably, Odoo 13 comes with significant advancements, including a more intuitive user interface, improved efficiency, and enhanced reporting capabilities.

If you’re currently using an older version of Odoo and want to take full advantage of the new features, upgrading to the latest version is essential.

When planning an Odoo upgrade, there are two major areas to consider:

1. Code Migration

2. Database Migration

Before you migrate your data, you must first complete the code migration. In this blog, we’ll walk you through how we can assist you in upgrading your module code from earlier versions to Odoo 13.

Common Challenges During Odoo Code Upgrade

When you attempt to restart Odoo 13 with older version modules, you may encounter errors or tracebacks. To avoid these issues, make sure to address the following key changes during your code upgrade:

1. Python Files

Module Version Format

Update the module version format when migrating. For example, when upgrading from Odoo 12 to Odoo 13, use the format:13.0.1.0.0

• 13.0 → Odoo major version

• 1.0.0 → p.q.r where:

  • p = model or view changes

  • q = upgrades

  • r = bug fixes

Deprecated Decorators

Odoo 13 has removed several decorators such as:

• @api.multi

• @api.one

• @api.cr

• @api.model_cr

• @api.returns

Multi-record support is now handled by default. Using old decorators will trigger tracebacks like:

pgsql

AttributeError: module 'odoo.api' has no attribute 'multi'

Structural Changes in Models

Some models have been renamed, restructured, or merged. For example, major changes occurred in modules like accounting and stock. Analyze each module’s structure for compatibility and necessary adjustments.

2. Field-Level Changes

• Attributes like oldname, tracking, etc., are deprecated.

• Use OpenUpgradeLib methods to create migration scripts if required.

• Ensure that computed fields are correctly assigned in all conditions, even false ones.

• Avoid relying on default values for computed stored fields—they retain old values unless explicitly set during computation.
  

3. XML Files

View Adjustments

• With model changes, the corresponding views need updates.

• The view_type attribute is deprecated. It defaults to “form,” so you can safely remove it.

• Remove deprecated XML attributes from your view declarations.

  
  

Font Awesome Icon Updates

Odoo 13 uses Font Awesome V5, which comes with updated icon names. Update your UI code accordingly.

• Example: calendar-check-o → calendar-check
  

4. JavaScript Files

Odoo 13 also introduces changes in JavaScript syntax, DOM structure, and usage of specific elements. Review and refactor your JS code to align with the new version.

Final Step: Validate Functionality & Add Tests

After migrating your module:

• Thoroughly test the module's functional behavior to ensure parity with the previous version.

• Add automated test cases to improve code coverage and reduce regression issues.
  

Need Help with Your Odoo Migration?

Did you find this blog helpful? Explore more of our articles to learn about new features in Odoo 13.

Looking to upgrade to the latest version of Odoo? Whether it’s code migration, database migration, or complete version upgrades,

we’re here to help.📞 Contact us today via phone or email to discuss your requirements and get expert assistance.