Skip to main content
Odoo // Migration

Move to the latest Odoo. Bring everything with you.

Version upgrades, legacy-to-Odoo moves, and hosting changes, handled without data loss, downtime surprises, or half-working custom modules on the other side.

Paths
Version · Legacy · Hosting
Before migrating
Full audit week
Safety net
Rollback window

Audit first, clean at the source, rehearse twice, keep the old system warm.

Why migrations deserve their own project

Odoo releases a major version every year, and each one changes data models, renames fields, and reworks parts of the interface. The standard modules are migrated by Odoo's upgrade process. Your custom modules, integrations, reports, and data quirks are not; they're yours to carry across.

That's why a migration that looks like "press upgrade" on paper usually turns into weeks of surprises in practice: a report that no longer prints, an integration that silently stops syncing, a custom field whose data vanished because its module wasn't ported.

We treat migration as a project with a clear inventory, rehearsals, and an exit plan. The goal is a cutover weekend so uneventful that your team barely notices anything changed, apart from the new features.

What a migration actually covers

Every one of these layers needs a decision and a test.

Data

Schema changes, renamed fields, and records that must survive with their history and links intact.

Custom modules

Porting to new APIs and OWL changes, and replacing modules whose features are now standard.

Integrations

External systems calling APIs whose behavior or authentication may have changed.

Reports & templates

QWeb reports, invoices, email templates, and website pages that depend on old fields.

Hosting

Server sizing, PostgreSQL version, backups, and workers for the new release.

People

Training on interface changes so day one isn't a support flood.

Which migration path applies to you?

ScenarioFrom → ToWhat to watch
Version upgradeOlder Odoo → current releaseCustom module porting and deprecated APIs
Multi-version jumpSeveral releases behind → currentData passes through each intermediate schema change
Edition changeCommunity ↔ EnterpriseModule availability, licensing, and data for Enterprise-only apps
Hosting moveOdoo Online → Odoo.sh or self-hostedCustom code allowances, backups, and access
Legacy ERPSpreadsheets, accounting packages, legacy ERP → OdooData quality, mapping rules, and open transactions

Five phases. No surprises.

  1. Step 01

    Audit

    ~1 week

    Inventory installed modules, custom code, integrations, reports, scheduled actions, and data volumes. Deliverable: a compatibility report rating every custom module as keep, port, replace with standard, or retire.

  2. Step 02

    Clean

    Fix duplicates, orphaned records, and broken references in the source system before moving anything. Clean data migrates predictably; dirty data multiplies problems.

  3. Step 03

    Port

    Update custom modules and integrations for the target version, with automated tests, in a staging environment that mirrors production.

  4. Step 04

    Rehearse

    Run the full migration on a recent copy of production at least twice. Reconcile record counts and financial totals, time the cutover window, and fix everything the rehearsal finds.

  5. Step 05

    Cut over

    Freeze changes, migrate, validate against the rehearsal checklist, train users on what changed, and keep the old system available read-only until sign-off.

How we validate a migration

"It looks fine" isn't a test. These checks run in every rehearsal and again at cutover.

CheckHowPass criteria
Record countsCompare counts per model before and afterEvery difference explained
Financial balancesTrial balance, receivables, and payables per periodTotals match to the cent
StockQuantities and valuation per locationMatch the source snapshot
Open documentsDraft quotes, open orders, unpaid invoicesAll present and actionable
Custom featuresAutomated tests plus scripted manual checksAll tests pass
IntegrationsSend and receive test transactionsRound trip succeeds

Why migrations fail, and what we do instead

Myth: We'll audit as we go.

Reality: We audit before writing a single migration script. Surprises found early are cheap; surprises found at cutover are expensive.

Myth: We'll clean the data after migration.

Reality: Dirty data migrated is dirty data with a new logo. We clean the source first.

Myth: Rollback won't be needed.

Reality: It's needed exactly when nobody planned it. The old system stays available until acceptance, and the rollback trigger is agreed in advance.

Myth: Custom modules just need a version bump.

Reality: APIs, views, and frontend frameworks change between releases. Each module needs porting and testing, and some can be replaced by standard features.

Planning your own migration?

Our article on planning an ERP migration without guesswork covers the inventory, data profiling, and rehearsal steps in more depth. It's useful whether or not you work with us.

The cutover weekend, step by step

Rehearsals turn the real cutover into a checklist. A typical runbook looks like this.

  1. Step 01

    Freeze

    Friday evening

    Users stop working in the old system; final backups are taken and verified.

  2. Step 02

    Migrate

    Run the rehearsed scripts on the final production copy, timing each step against the rehearsal.

  3. Step 03

    Validate

    Run the reconciliation checks: record counts, balances, stock, open documents, and integration round trips.

  4. Step 04

    Go or roll back

    The project owner decides against the agreed thresholds. A rollback restores the old system with no data lost.

  5. Step 05

    Open the doors

    Monday morning

    Users start in the new version with quick-reference guides, and the team is on hand for questions.

Is your instance ready to migrate?

  • A list of every installed and custom module
  • Source code for all custom modules, in version control
  • Documentation or owners for each integration
  • A recent backup that has been restored successfully
  • Agreement on which history to migrate or archive
  • A cutover window that avoids month-end and peak season

Odoo's own upgrade process, in plain terms

Odoo's documentation sets the rhythm: each major version is supported for three years, and on Odoo Online a major upgrade is mandatory every two yearsSource [1]. It strongly recommends requesting an upgraded test database first and spending time testing it, and notes that the production upgrade makes the database unavailable while it runsSource [1].

For customized databases, Odoo lists six steps, starting with stopping new development and challenging existing customizations, then making each module installable on an empty and then an upgraded database, testing extensively, and rehearsing before the production upgradeSource [2]. Our migration process follows the same sequence, with reconciliation scripts added so the go or no-go decision rests on numbers.

Frequently asked questions

Can we change hosting during the migration?
Yes, and it's often a good moment to do it, for example moving from Odoo Online to Odoo.sh or your own servers. The hosting move is planned and rehearsed as part of the same cutover.
What affects the cost of a migration?
Mainly the number and complexity of custom modules, how many versions you're jumping, data volume and quality, and the integrations that need retesting. The audit week turns those into an estimate.
Do we need to freeze changes before migrating?
Only for the cutover window itself. Before that, normal work continues; we re-run the migration on a fresh copy just before cutover.
Can we skip several Odoo versions at once?
Often yes, but data still passes through each version's schema changes. The audit tells you the safest route for your instance and whether intermediate steps are needed.
How much downtime should we expect?
It depends on data volume and validation steps. Rehearsals measure the real cutover window so you can schedule it, often over a weekend.
Do our custom modules need rewriting?
Usually porting, sometimes partial rewrites. Modules that patched core code or skipped tests take the most work, and some can be retired because the feature is now standard.
Will we lose historical data?
Not if it's mapped. We agree which history migrates in full and which is archived, then reconcile the result with your team.
Can you migrate from a non-Odoo ERP?
Yes. We extract, transform, and load data from spreadsheets, accounting packages, and legacy ERPs, including open transactions and opening balances.
What if something goes wrong during cutover?
The rollback trigger and procedure are agreed before cutover. If a validation fails beyond an agreed threshold, the old system resumes and we fix the issue before retrying.
Do you migrate integrations too?
Yes. Every integration is inventoried in the audit, updated for any API changes, and tested end to end during rehearsals.
How often should we upgrade?
Staying within a version or two of current keeps each upgrade smaller and safer. Long gaps make every module port and data transformation bigger.
How long is an Odoo version supported?
Odoo states that each major version is supported for three yearsSource [1]. Plan upgrades as regular projects rather than waiting for end of support.
Do we have to freeze development during a migration?
Odoo recommends a complete code freeze during the upgrade, with bug fixes as the exceptionSource [2]. It keeps the target from moving while modules are ported and tested.