Upgrade Recommendations

ERPWeb Test Client — Test Odoo 16 to 19 Upgrade — Odoo 16 to Odoo 19

Back to Project Action Plan Dependency Summary Risk Summary Upgrade Report Projects Dashboard
517 Source modules discovered
646 Target modules discovered
85 Source-only modules
214 Target-only modules
2 Dependency recommendations
0 Dependency manual review
14 Scanner recommendations
10 Scanner manual review

Workspace / Source Context

Workspace: ERPWeb Test Client 16.0 to 19.0 Module Upgrade Workspace

Status: Prepared

Source repository: Odoo 16.0 Community

Target repository: Odoo 19.0 Community

Generated at: 2026-05-14T11:17:09+00:00

Latest JSON Report

File: workspace_1_upgrade_rule_map_20260514_100203.json

module_upgrade_workspaces/project_1/erpweb-test-client-test-odoo-16-to-19-upgrade/reports/workspace_1_upgrade_rule_map_20260514_100203.json

Modified: 2026-05-14 12:02:03 · Size: 10860 bytes

Dependency Action Categories

Action categoryCount
keep_dependency 2

Scanner Action Categories

Action categoryCount
convert_old_api_signature 1
dependency_review 4
validate_manifest_metadata 3
update_manifest_version_for_target 1
migrate_legacy_javascript_module 1
migrate_legacy_web_js_imports 1
modernize_recordset_api 1
review_convert_attrs_modifiers 1
review_convert_states_modifiers 1

Next Upgrade Actions

Info

Dependency recommendations are currently auto-safe

No dependency recommendations currently require manual review.

High

Convert scanner findings into upgrade work packages

10 scanner recommendation(s) require developer review or migration work.

Medium

Prioritise action categories by count

Use the scanner action category counts to group Python API, XML view, JavaScript, manifest, and dependency-review work.

Info

Keep the latest generated JSON report for audit traceability

Latest report: module_upgrade_workspaces/project_1/erpweb-test-client-test-odoo-16-to-19-upgrade/reports/workspace_1_upgrade_rule_map_20260514_100203.json

Dependency Upgrade Recommendations

Dependency Requesting module Action category Status Recommendation Source / Target
base
odoo_available
erpweb_phase3_risky_test_module keep_dependency
Confidence: high
auto-safe Keep this dependency. It exists in both the validated source and target Odoo source registries.
Dependency is available in the validated target Odoo source registry. Source edition: community; target edition: community.
Source: community ✓
Target: community ✓
sale
odoo_available
erpweb_phase3_risky_test_module keep_dependency
Confidence: high
auto-safe Keep this dependency. It exists in both the validated source and target Odoo source registries.
Dependency is available in the validated target Odoo source registry. Source edition: community; target edition: community.
Source: community ✓
Target: community ✓

Scanner Finding Upgrade Recommendations

Finding Location Action category Status Recommendation
high python_api
Old Odoo API method signature detected
erpweb_phase3_risky_test_module/models/risky_model.py:10 convert_old_api_signature
Confidence: high
manual-review Convert old cr/uid/ids/context method signatures to modern self.env recordset-based API.
Convert old API methods to modern Odoo environment API using self.env and recordsets.
info dependencies
Dependencies captured
custom_addons/qr_delivery/__manifest__.py dependency_review
Confidence: high
auto-safe Use the source-aware dependency graph to validate dependency availability before code migration.
In the dependency graph phase, split and validate these dependencies against target Odoo version availability.
info dependencies
Dependencies detected
erpweb_phase3_risky_test_module/__manifest__.py dependency_review
Confidence: high
auto-safe Use the source-aware dependency graph to validate dependency availability before code migration.
Later phases should validate these dependencies against the target Odoo version and installed app set.
info dependencies
Dependencies detected
erpweb_phase3_test_module/__manifest__.py dependency_review
Confidence: high
auto-safe Use the source-aware dependency graph to validate dependency availability before code migration.
Later phases should validate these dependencies against target Odoo version and installed app set.
info dependencies
Structured dependency records rebuilt
erpweb_phase3_risky_test_module/__manifest__.py dependency_review
Confidence: high
auto-safe Use the source-aware dependency graph to validate dependency availability before code migration.
Review the dependency summary report for missing custom dependencies before starting code migration.
info manifest
Manifest metadata captured
custom_addons/qr_delivery/__manifest__.py validate_manifest_metadata
Confidence: medium
manual-review Validate manifest metadata, dependencies, assets, license, and version format for the target Odoo version.
In the real scanner phase, parse this manifest and validate depends, assets, license and version format.
info manifest
Manifest parsed successfully
erpweb_phase3_risky_test_module/__manifest__.py validate_manifest_metadata
Confidence: medium
manual-review Validate manifest metadata, dependencies, assets, license, and version format for the target Odoo version.
Continue with dependency and code-pattern scanning.
info manifest
Manifest parsed successfully
erpweb_phase3_test_module/__manifest__.py validate_manifest_metadata
Confidence: medium
manual-review Validate manifest metadata, dependencies, assets, license, and version format for the target Odoo version.
Continue with dependency and code-pattern scanning.
low version_risk
Manifest version does not start with source Odoo major version
erpweb_phase3_risky_test_module/__manifest__.py update_manifest_version_for_target
Confidence: medium
manual-review Review and update the manifest version so it aligns with the source and target upgrade path.
Confirm whether the manifest version is correct for the source branch being upgraded.
medium javascript
Legacy Odoo JavaScript module pattern detected
erpweb_phase3_risky_test_module/static/src/js/risky.js:1 migrate_legacy_javascript_module
Confidence: medium
manual-review Review legacy odoo.define JavaScript and migrate it where required for the target Odoo frontend architecture.
Review whether this should be converted to the modern Odoo JavaScript module format.
medium javascript
Legacy web.* JavaScript require detected
erpweb_phase3_risky_test_module/static/src/js/risky.js:3 migrate_legacy_web_js_imports
Confidence: medium
manual-review Review legacy web.* JavaScript imports and migrate them to the target Odoo frontend service/module patterns.
Review frontend imports and services against the target Odoo version.
medium python_api
Deprecated @api.multi usage
erpweb_phase3_risky_test_module/models/risky_model.py:6 modernize_recordset_api
Confidence: high
manual-review Remove/replace @api.multi usage and verify the method behaves correctly with modern Odoo recordsets.
Review and convert the method to modern recordset-style API for the target Odoo version.
medium xml_views
Legacy attrs usage detected
erpweb_phase3_risky_test_module/views/risky_views.xml:5 review_convert_attrs_modifiers
Confidence: medium
manual-review Review attrs-based view modifiers and convert where required for the target Odoo view syntax.
Review this view against the target Odoo version's XML/view modifier requirements.
medium xml_views
Legacy states usage detected
erpweb_phase3_risky_test_module/views/risky_views.xml:5 review_convert_states_modifiers
Confidence: medium
manual-review Review states-based visibility/read-only logic and convert where required for the target Odoo version.
Review state-based visibility/read-only logic for compatibility with the target Odoo version.