odoo-migration

Plan and execute Odoo migrations across versions 16 through 19.

1|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odoo-migration
Source: https://github.com/halim-23/odoo-dev-plugin/tree/main/skills/odoo-migration
Command: npx skills add https://github.com/halim-23/odoo-dev-plugin --skill odoo-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, end-to-end framework for planning, executing, and validating migrations across multiple Odoo major versions (16→17→18→19) for Community and Enterprise editions. It consolidates best practices from OpenUpgrade, odoo-migrate, and enterprise upgrade guides, reducing risk and downtime during version upgrades.

Core Features & Use Cases

  • Comprehensive migration strategies for v16 through v19, including pre- and post-migrate scripts, data transforms, and compatibility checks.
  • guidance for OpenUpgrade-based upgrades, vendor-provided upgrade paths, and on-premise or cloud deployments (odoo.sh, EE/CE).
  • Example migration workflows for database copy testing, backup strategies, and rollback planning in production environments.

Quick Start

Plan and execute a step-by-step Odoo migration from v16 to v19 using OpenUpgrade or odoo-migrate, including backup, test, and validation.

Frequently Asked Questions about odoo-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Odoo across multiple major versions from 16 to 19?

To upgrade Odoo across major versions, you execute a step-by-step plan using OpenUpgrade or odoo-migrate. This involves version-by-version upgrades, applying pre/post-migrate scripts, and performing data transformations to safely reach v19.

Does Odoo migration work for both Community and Enterprise editions on Odoo.sh?

Yes, Odoo migration strategies apply to both Community and Enterprise editions. The framework supports on-premise, Odoo.sh, and online environments, ensuring safe upgrades and rollback planning across these deployment platforms.

What is the best way to test an Odoo database upgrade safely?

The best way to test an Odoo database upgrade safely is to perform the migration on a database copy. This approach allows you to validate data transforms and pre/post-migrate scripts without risking your production environment.

How do pre-migrate and post-migrate scripts work during an OpenUpgrade?

Pre-migrate and post-migrate scripts execute data transformations and compatibility checks before and after the core OpenUpgrade process. They ensure database schema and records properly adapt to the new Odoo version structure.

Can I rollback an Odoo version upgrade if the migration fails?

Yes, you can rollback an Odoo version upgrade by implementing a backup and rollback strategy. Testing the migration process on a database copy first ensures you have a valid restore point if production validation fails.

What are the limitations of using openupgradelib for Odoo data transformations?

openupgradelib facilitates Odoo data transformations but requires version-by-version upgrades without skipping major releases. You must carefully script pre/post-migrate functions, as incomplete compatibility checks can cause data loss during the transition.