Data
Schema changes, renamed fields, and records that must survive with their history and links intact.
Version upgrades, legacy-to-Odoo moves, and hosting changes, handled without data loss, downtime surprises, or half-working custom modules on the other side.
Audit first, clean at the source, rehearse twice, keep the old system warm.
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.
Every one of these layers needs a decision and a test.
Schema changes, renamed fields, and records that must survive with their history and links intact.
Porting to new APIs and OWL changes, and replacing modules whose features are now standard.
External systems calling APIs whose behavior or authentication may have changed.
QWeb reports, invoices, email templates, and website pages that depend on old fields.
Server sizing, PostgreSQL version, backups, and workers for the new release.
Training on interface changes so day one isn't a support flood.
| Scenario | From → To | What to watch |
|---|---|---|
| Version upgrade | Older Odoo → current release | Custom module porting and deprecated APIs |
| Multi-version jump | Several releases behind → current | Data passes through each intermediate schema change |
| Edition change | Community ↔ Enterprise | Module availability, licensing, and data for Enterprise-only apps |
| Hosting move | Odoo Online → Odoo.sh or self-hosted | Custom code allowances, backups, and access |
| Legacy ERP | Spreadsheets, accounting packages, legacy ERP → Odoo | Data quality, mapping rules, and open transactions |
Step 01
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.
Step 02
Fix duplicates, orphaned records, and broken references in the source system before moving anything. Clean data migrates predictably; dirty data multiplies problems.
Step 03
Update custom modules and integrations for the target version, with automated tests, in a staging environment that mirrors production.
Step 04
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.
Step 05
Freeze changes, migrate, validate against the rehearsal checklist, train users on what changed, and keep the old system available read-only until sign-off.
"It looks fine" isn't a test. These checks run in every rehearsal and again at cutover.
| Check | How | Pass criteria |
|---|---|---|
| Record counts | Compare counts per model before and after | Every difference explained |
| Financial balances | Trial balance, receivables, and payables per period | Totals match to the cent |
| Stock | Quantities and valuation per location | Match the source snapshot |
| Open documents | Draft quotes, open orders, unpaid invoices | All present and actionable |
| Custom features | Automated tests plus scripted manual checks | All tests pass |
| Integrations | Send and receive test transactions | Round trip succeeds |
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.
Rehearsals turn the real cutover into a checklist. A typical runbook looks like this.
Step 01
Users stop working in the old system; final backups are taken and verified.
Step 02
Run the rehearsed scripts on the final production copy, timing each step against the rehearsal.
Step 03
Run the reconciliation checks: record counts, balances, stock, open documents, and integration round trips.
Step 04
The project owner decides against the agreed thresholds. A rollback restores the old system with no data lost.
Step 05
Users start in the new version with quick-reference guides, and the team is on hand for questions.
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.
Plan an ERP migration
A practical framework for inventorying customizations, validating data, rehearsing cutover, and communicating an ERP migration plan.
OdooCustom Odoo modules
Upgrade-safe custom Odoo modules in Python and OWL: inheritance only, tested, documented, and OCA-style. No core patches, ever.
OdooOdoo implementation
End-to-end Odoo implementation: process discovery, configuration, data migration, testing, training, and a phased go-live with hypercare.
Next step
Thirty minutes with an engineer, no slide deck required. You'll leave with a clearer picture, whether or not we work together.