Odoo Migration

Community

mart337i

odoo-migration

End-to-end OCA module migration workflow for porting addons between Odoo major versions and preparing [MIG] pull requests. Use when migrating OCA modules, porting addons between Odoo versions, applying OCA migration checklists, resolving migration patch conflicts, or preparing versioned OCA migration PRs.

Overview

Publisher	mart337i
Repository	`odoo-skills`
Skill name	`odoo-migration`
Stars	61
Forks	15
Bundled files	1
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.
1 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 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-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-migration .claude/skills/odoo-migration

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

Use it in TypingMind

Enable Odoo 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 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 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 Migration

Use this skill for OCA module migration between Odoo major versions. Compose with odoo-report-migration when the module contains QWeb/PDF reports whose visual output must be preserved.

This is not an OpenUpgrade skill. Do not adopt the OpenUpgrade operating model, its commands, or its workflow for a normal OCA [MIG] port. Consulting OpenUpgrade's upgrade_analysis.txt for core-module data-model changes IS part of the OCA protocol, because the version guides deliberately cover framework changes only and point there for data-model deltas. If a migration requires project-specific data handling, inspect the addon and repo conventions directly.

First Move

Identify:

source Odoo version
target Odoo version, including Odoo 20.0 when the target branch is available
OCA repository name
module path/name
current branch and remotes
whether the corresponding OCA migration issue or PR context is known

If the Odoo framework source or local development setup is needed and not inside the workspace, ask the user to set ODOO_SOURCE=/path/to/odoo, ODOO_BASE_COMMAND="...", and ODOO_TOOL_README=/path/to/README.md as needed.

Workflow

Use OCA-MODULE-MIGRATION.md as the end-to-end guide.

Always apply every intermediate version checklist for jumps across more than one major version. Examples: migrating 15.0 to 18.0 requires the 16.0, 17.0, and 18.0 sections; migrating 18.0 to 20.0 requires the 19.0 and 20.0 sections.

Before creating a migration branch, verify that the OCA repository exposes the target branch and that the related migration issue or PR context is known. Odoo 20 support in this skill remains the normal OCA migration workflow, not OpenUpgrade.

The OCA protocol opens with a preamble: refresh the OCA conventions, subscribe to the project's mailing list, announce the module(s) on the Migration to version <target> issue, and install pre-commit. The issue announcement is the documented OCA step.

The migration is not done at the final commit. It reaches OCA when the branch is pushed to the contributor's fork and the pull request is opened with the [<target>][MIG] <module>: Migration to <target> title. See OCA-MODULE-MIGRATION.md for the fork, push, and pull request mechanics.

Guardrails

Keep migration compatibility changes separate from behavior changes where possible.
Do not change copyright years.
Do not change original authors.
Do not invent migration script style without repo precedent.
Do not run Odoo install/update/test commands until likely commands are discovered from repo docs, $ODOO_TOOL_README, or $ODOO_BASE_COMMAND, and confirmed by the user.
Do not run git filter-branch or git filter-repo without explicit user approval, even when the module rename makes them the correct move.
Do not add remotes, push branches, post migration-issue comments, or open pull requests without explicit user confirmation.
Do not use --no-verify except for the OCA-documented first mechanical-formatting commit, and only after confirming that exception with the user.
Prefer OCA PR title format: [<target>][MIG] <module>: Migration to <target>.

Bundled files

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

OCA-MODULE-MIGRATION.md33 KB

Frequently asked questions

What does the Odoo Migration AI skill do?

Why use Odoo Migration on TypingMind?

Because you install it once and use it with any model. Odoo 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 Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mart337i/odoo-skills/tree/main/skills/odoo-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 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 Migration?

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

Is the Odoo 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

Clawsweeper

openclaw

OrganizationPopular

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

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

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Odoo Migration

First Move

Workflow

Guardrails

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now