Odoo Report Migration

Community

mart337i

odoo-report-migration

Migrates Odoo QWeb HTML and PDF reports between major versions while preserving data semantics, access behavior, paper geometry, and intended visual appearance. Use when porting reports across Odoo versions, adapting report templates or assets after an upgrade, or diagnosing visual regressions in migrated PDFs.

Overview

Publisher	mart337i
Repository	`odoo-skills`
Skill name	`odoo-report-migration`
Stars	61
Forks	15
Bundled files	3
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by mart337i on GitHub. Read the source before you install it.

Installation

Install the Odoo Report Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/mart337i/odoo-skills/tree/main/skills/odoo-report-migration
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/mart337i/odoo-skills.git /tmp/odoo-skills
mkdir -p .claude/skills
cp -r /tmp/odoo-skills/skills/odoo-report-migration .claude/skills/odoo-report-migration

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Odoo Report Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Odoo Report Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Odoo Report Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Odoo Report Migration

Use this skill for report-specific migration work. Compose it with odoo-migration for the module port, the source and target version skills for framework details, odoo-report-design for layout decisions, and odoo-web-testing when browser or asset behavior is involved.

First Move

Identify the source and target versions, module and report XML IDs, current rendering environment, report action, template chain, paper format, assets, custom value provider, and the visual requirements that must remain stable.

OCA Process Still Applies

Report work is not process-free. When a report migration is part of a module [MIG], the full OCA process in odoo-migration still applies end to end: announcing the module(s) on the Migration to version <target> issue, creating the <target>-mig-<module> branch, the [MIG] commit, pushing to the contributor's fork, and opening the pull request titled [<target>][MIG] <module>: Migration to <target>. Rendering equivalence is an acceptance criterion for the pull request, not a substitute for it. Do not post, push, or open the pull request without the same explicit confirmation required by odoo-migration.

Workflow

Freeze a baseline. Render HTML and PDF using deterministic records and record the version, commit, language, company, user, paper format, and renderer details.
Inventory dependencies: inherited templates, external layouts, report assets, SCSS/CSS, fonts, images, paper formats, translations, and report actions.
Apply every intermediate Odoo migration checklist for a multi-version jump. Separate API/data migration from presentation changes.
Inspect the target version's upstream report templates, asset bundles, CSS framework, renderer, and report action fields before porting XPath or CSS.
Port the smallest compatible change. Prefer stable inherited anchors over copying the old core template.
Re-render the same fixture set and classify every difference as intended, renderer noise, or a regression.
Verify access, data semantics, translations, pagination, paper geometry, assets, and multi-record behavior before declaring success.

Guardrails

Do not call a report visually preserved because it merely loads or produces a PDF.
Do not compare PDF bytes as the primary visual assertion.
Do not fix a layout regression with arbitrary CSS before checking target templates, asset bundles, paper format, fonts, and renderer behavior.
Do not broaden report access or expose data while changing presentation.
If the baseline cannot be rendered, record the missing evidence and use a clearly labeled reconstructed baseline instead of claiming equivalence.

References

REPORT-MIGRATION.md - end-to-end migration procedure.
VISUAL-REGRESSION.md - practical output comparison workflow.
REPORT-VERSION-MATRIX.md - version-sensitive audit points, 8.0 to 20.0.

The OCA version guides themselves are at https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-<version>. The wiki is authoritative over this pack.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Odoo Report Migration AI skill do?

Why use Odoo Report Migration on TypingMind?

Because you install it once and use it with any model. Odoo Report Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Odoo Report Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mart337i/odoo-skills/tree/main/skills/odoo-report-migration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Odoo Report Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Odoo Report Migration?

As many as you like. As long as a model supports skills, you can use Odoo Report Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Odoo Report Migration AI skill free?

It is published on GitHub by mart337i. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Discord Clawd

openclaw

OrganizationPopular

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Odoo Report Migration

First Move

OCA Process Still Applies

Workflow

Guardrails

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now