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.
我们做什么
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 |
|---|---|---|
| v15 / v16 | v17 / v18 | Routine |
| v13 / v14 | v17 / v18 | Complex (intermediate hop usually) |
| v12 or older | v17 / v18 | Multi-step |
| Community | Enterprise | Handled as part of the upgrade |
Use the version compatibility matrix to explore specific pairs.
典型进度
三种参考合作规模
小
3–6 weeks — standard modules, minor customization, up to 1M records
中
6–10 weeks — heavy customization, multi-company, up to 5M records
大
10–16+ weeks — 5M+ records, deep customization, multiple integrations
每份报价都是定制。 定价如何运作 →
相关服务
与此互补的工作
Odoo Migration
Every kind of Odoo database migration — forward, backward, split, merge, currency. Including the rare capabilities most partners won't touch.
阅读更多Odoo Downgrade
Most Odoo partners refuse downgrades. We don't. Move a database and its code to an older Odoo version — safely, with a rehearsed rollback.
阅读更多Odoo Customization
Studio configurations, custom modules, QWeb reports, OWL components, and API integrations. Clean code, upgrade-safe, tested.
阅读更多常见问题
关于 odoo upgrade 的常见问题
Can you jump multiple versions in one step? +
Sometimes. For gaps of 1–2 major versions we usually go direct. For larger gaps (e.g. v13 → v18) we plan an intermediate hop so each transformation is bounded and testable.
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.