Odoo migration
Odoo Upgrade
Move your Odoo database and its customizations to a newer major version, with code migration, test runs, UAT gates, and a rehearsed cutover.
Was wir tun
From any version. To the one you need.
An Odoo upgrade is rarely “just the database.” It is the code you have added, the Studio fields your team depends on, the integrations that connect to the rest of your business. We handle all of it.
What we migrate
- The full production database, records and configuration included.
- Every custom module you have installed, updated for the target version’s APIs, ORM, and view conventions.
- Studio customizations (new fields, automated actions, reports, views).
- QWeb and PDF reports.
- OWL / JS components, web extensions, ACLs and record rules.
- All integrations that touch the database (XML-RPC, JSON-RPC, webhook subscribers).
How an upgrade runs
- Audit — we take stock of what you have. Data volume, custom code, Studio, integrations, licensing.
- Target environment — we stand up the new version in an isolated environment.
- Test migration — the first full run. You get a working replica of the target version with your data. Expect issues; this is the point.
- Iterate — we fix, re-run, re-validate, until the test migration is clean.
- UAT — your people use the test system against real scenarios. Sign-off per functional area.
- Cutover — scheduled downtime, final delta migration, validation, go/no-go, hypercare begins.
Upgrade paths we handle most
| From | To | Complexity (always one direct migration) |
|---|---|---|
| v15 / v16 | v17 / v18 | Routine |
| v13 / v14 | v17 / v18 | Complex — more data-model changes to map |
| v12 or older | v17 / v18 | Extensive mapping — still direct |
| Community | Enterprise | Handled as part of the upgrade |
Use the version compatibility matrix to explore specific pairs.
Typischer Zeitplan
Drei indikative Engagement-Größen
Klein
3–6 weeks — standard modules, minor customization, up to 1M records
Mittel
6–10 weeks — heavy customization, multi-company, up to 5M records
Groß
10–16+ weeks — 5M+ records, deep customization, multiple integrations
Jedes Angebot ist individuell. So funktioniert die Preisgestaltung →
Ähnliche Leistungen
Arbeiten, die diese ergänzen
Odoo Migration
Every kind of Odoo database migration — forward, backward, split, merge, currency. Including the rare capabilities most teams won't touch.
Mehr lesenOdoo Downgrade
Most teams avoid downgrades. We don't. Move a database and its code to an older Odoo version — safely, with a rehearsed rollback.
Mehr lesenOdoo Customization
Studio configurations, custom modules, QWeb reports, OWL components, and API integrations. Clean code, upgrade-safe, tested.
Mehr lesenFAQ
Häufige Fragen zu odoo upgrade
Can you jump multiple versions in one step? +
Yes — always. We migrate directly from your current version to the target (v13 → v18 is one migration, not five). We never route through intermediate versions; the safety comes from full test migrations and reconciliation against your original database.
What about custom modules written by other developers? +
We do this routinely. Part of our discovery is reading every custom module and identifying everything that breaks on the target version.
How long is the production downtime? +
Typically a few hours to a weekend depending on data size. We plan a detailed cutover window with you and give a realistic estimate after the test migration.
odoo upgrade-Projekt starten
Sagen Sie, woran Sie arbeiten. Wir antworten innerhalb eines Werktags.