Odoo Upgrade & Migration Guide: v14/v15/v16/v17/v18 to v19

Should You Upgrade?

Upgrade to Odoo 19 if: you need new features, your current version is end-of-life, third-party modules require it, or performance improvements benefit you. Do NOT upgrade just because a new version exists — the effort must be justified.

Version Support Lifecycle

Pre-Migration Checklist

1. Inventory all modules — List every installed module (standard + custom + third-party)
2. Check third-party compatibility — Are your community modules available for v19?
3. Audit customizations — List all custom models, views, reports, and workflows
4. Full backup — Database + filestore, tested restore
5. Test environment — Set up a separate server for migration testing
6. Stakeholder communication — Planned downtime, feature changes, training

Migration Paths

Path 1: Odoo.sh (Enterprise)

If you are on Odoo Enterprise with Odoo.sh:

1. Create a staging branch
2. Upgrade the branch to v19 via Odoo.sh interface
3. Odoo runs migration scripts automatically
4. Test thoroughly
5. Merge to production when ready

Path 2: OpenUpgrade (Community)

OpenUpgrade provides community-maintained migration scripts:

# 1. Clone OpenUpgrade for target version
git clone https://github.com/OCA/OpenUpgrade.git --branch 19.0

# 2. Restore your database backup to test server
pg_restore -U odoo -d test_upgrade /backups/production.dump

# 3. Run OpenUpgrade
python odoo-bin -d test_upgrade \
    --update all \
    --stop-after-init \
    --load=base,web,openupgrade_framework

# 4. Check the log for errors
grep -i error /var/log/odoo/upgrade.log

Path 3: Fresh Install + Data Migration

For major version jumps (v14 → v19), sometimes a fresh install with data migration is cleaner:

1. Install Odoo 19 fresh
2. Configure modules and settings
3. Export data from old instance (CSV/XML-RPC)
4. Import into new instance
5. Verify data integrity

Custom Module Adaptation

Common Changes v17/v18 → v19

# 1. _sql_constraints → models.Constraint
# Old:
_sql_constraints = [('name_uniq', 'unique(name)', 'Must be unique')]
# New:
_name_unique = models.Constraint('UNIQUE(name)', 'Must be unique')

# 2. <tree> → <list>
# Old: <tree>...</tree>
# New: <list>...</list>

# 3. attrs dict → direct attributes
# Old: attrs="{'invisible': [('state', '!=', 'draft')]}"
# New: invisible="state != 'draft'"

Common Changes v14/v15 → v19

# 1. name_get() → _compute_display_name()
# 2. fields_view_get() → get_views()
# 3. Module references changed (e.g., stock.group_stock_multi_locations)
# 4. Report template changes
# 5. OWL 2 replaces OWL 1 (complete JS rewrite)
# 6. Many UI framework changes

Testing Strategy

1. Automated tests — Run all existing test suites on upgraded database
2. Functional testing — Every business process end-to-end (quote → order → invoice → payment)
3. Data verification — Compare record counts, financial totals, inventory levels
4. Report testing — Every PDF report renders correctly
5. Integration testing — API endpoints, email, payment gateways
6. Performance testing — Compare response times pre/post upgrade

Rollback Plan

• Keep the pre-upgrade backup accessible
• Keep the old Odoo version installed (separate directory)
• Document the rollback procedure: stop v19, restore backup, start old version
• Set a go/no-go deadline (24-48 hours after upgrade)

DeployMonkey

DeployMonkey makes testing upgrades easy: deploy a test Odoo 19 instance, migrate your data, test thoroughly, and only then upgrade production. The AI agent helps identify migration issues and adapt custom modules to v19 syntax.