` | `` | | Required/Readonly | `attrs="{'required': [...]}"` | `required="condition"` | | Python minimum | 3.10 | 3.10+ | | JS modules | Legacy `define(['web.core'])` | ES module `import` syntax | ### Odoo 15 → 16 | Topic | Old (v15) | New (v16) | |---|---|---| | Website published flag | `website_published = True` | `is_published = True` | | Mail aliases | `alias_domain` on company | Moved to `mail.alias.domain` model | | Report render | `_render_qweb_pdf()` | `_render_qweb_pdf()` (same, but signature changed) | | Accounting move | `account.move.line` grouping | Line aggregation rules updated | | Email threading | `mail_thread_id` | Deprecated; use `message_ids` | ## Examples ### Example 1: Migrate `attrs` visibility to Odoo 17 ```xml ``` ### Example 2: Migrate Chatter block ```xml

``` ### Example 3: Migrate website_published flag (v15 → v16) ```python # v15 record.website_published = True # v16+ record.is_published = True ``` ## Best Practices - ✅ **Do:** Test with `--update=your_module` on each version before pushing to production. - ✅ **Do:** Use the official [Odoo Upgrade Guide](https://upgrade.odoo.com/) to get an automated pre-upgrade analysis report. - ✅ **Do:** Check OCA migration notes and the module's `HISTORY.rst` for community modules. - ✅ **Do:** Run `npm run validate` after migration to catch manifest or frontmatter issues early. - ❌ **Don't:** Skip intermediate versions — go v14→v15→v16→v17 sequentially; never jump. - ❌ **Don't:** Forget to update `version` in `__manifest__.py` (e.g., `17.0.1.0.0`). - ❌ **Don't:** Assume OCA modules are migration-ready; check their GitHub branch for the target version. ## Limitations - Covers **v14 through v17** only — does not address v13 or older (pre-manifest era has fundamentally different module structure). - The **Odoo.sh automated upgrade** path has additional steps not covered here; refer to Odoo.sh documentation. - **Enterprise-specific modules** (e.g., `account_accountant`, `sign`) may have undocumented breaking changes; test on a staging environment with Enterprise license. - JavaScript OWL component migration (v15 Legacy → v16 OWL) is a complex topic not fully covered by this skill. --- ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Retrieve prior design decisions (color palettes, typography, spacing scales) to maintain visual consistency across sessions. Cache generated design tokens. ```bash # Check for prior frontend/design context before starting python3 execution/memory_manager.py auto --query "design system decisions and component patterns for Odoo Migration Helper" ``` ### Storing Results After completing work, store frontend/design decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "Design system: adopted 8px grid, Inter font family, HSL color tokens with dark mode support" \ --type decision --project \ --tags odoo-migration-helper frontend ``` ### Multi-Agent Collaboration Share design decisions with backend agents (API contract changes) and QA agents (visual regression baselines). ```bash python3 execution/cross_agent_context.py store \ --agent "" \ --action "Implemented UI components — new design system with accessibility compliance (WCAG 2.1 AA)" \ --project ``` ### Design Memory Persistence Store design system tokens and component decisions in Qdrant so any agent on any platform (Claude, Gemini, Cursor) can retrieve and apply consistent styling.