Business overview
What does it do?
Map business capabilities to source-level Views, fields, buttons, menus, and model relationships. Distinguish observed source structure from proposed business meaning.
01 / The Odoo 20 change
Security is not just a file conversion.
Odoo 20 brings access rights and record-level restrictions together. A mechanically converted file does not by itself demonstrate that the intended business permissions are preserved.
Odoo 18 / 19
Two security layers
ir.model.access — model-level permissions
ir.rule — record-level domain restrictions
Permissions and record restrictions were maintained as separate definitions.
Odoo 20
Unified access model
ir.access — operation and optional domain
Permissions and restrictions are expressed through one access framework. Group and domain semantics still matter.
2,420Odoo 18 access CSV records in our source inventory
2,588Odoo 20 access CSV records in our source inventory
18 → 20Community source baselines compared in the example assessment
Important: These CSV totals come from a bounded internal source inventory. Odoo 20 uses a different security schema: the totals cannot be directly compared as added or removed permissions, nor do they measure security risk. The essential task is to check the meaning of access rights, restrictions, user groups, and business behavior.
Technical reference: Odoo 20 Security in Odoo · Odoo migration source. These observations are source-based and do not establish runtime compatibility.
02 / Why the architecture matters
Understand the customization in business terms.
A custom module is not only a collection of Python methods. It changes screens, navigation, workflows, linked records, and what different users are allowed to do.
Migration priority
What should be reviewed?
Organize source-derived differences and unresolved checks by business area rather than treating every file as an isolated change.
Engineering evidence
What supports the finding?
Examine XPath, Python methods, dependencies, and security definitions with traceable source evidence.
03 / See the analysis
Real three-part sample report.
Advanced Project Management System · Odoo Community 18 → 20 · source-level assessment, not runtime verification.
Reproducible source evidence
Download the analyzed Odoo 18 module ZIP
Original developer: Cybrosys Techno Solutions. Module: advanced_project_management_system. Publisher-listed license: LGPL-3.
Download analyzed ZIP Official publisher listing
SHA-256 (exact downloadable ZIP): 8fcf4a004989a3b8f7c76e17818520d6959cd0983c6103b57334e3fdcf8d2d84
The ZIP is provided for independent review of this example. Its presence does not imply that Odoo 20 runtime compatibility has been verified.
Example interpretation and findings are based on static evidence. Views identified in XML are not confirmed to function in a running Odoo 20 environment. The sample should contain no confidential source data before publication.
04 / How to request
Send us a custom module ZIP. We will analyze it for free — for now.
Currently available at no charge for scoped requests. Odoo Community Edition source baselines are used for comparison. This is a static diagnostic report, not an automated code conversion, installation test, or guarantee of permission equivalence.
Submit the request
Tell us your current version, target version, and which custom modules you want assessed using Google Forms. No ZIP attachment is needed yet.
Receive secure upload instructions
RAQQA reviews the request and emails instructions for sending the ZIP to a private Cloudflare R2 upload destination. Do not email source code or credentials.
Review your findings
Receive the available Business Overview, Migration Priority, and Engineering Evidence reports, with explicit limitations and source-level findings.
The free offering is subject to request scope and capacity. Only upload code you are authorized to share. Enterprise-only functionality, third-party dependencies, installation, and operational correctness are not certified by this Community-based source review.
05 / Beyond reports
A foundation for more reliable migration automation.
These reports demonstrate a deeper capability: understanding how Odoo architecture, business functions, and permissions relate across versions. Our longer-term work aims to use that understanding to support more reliable migration and modernization — beyond producing reports.