Migrations & Upgrades
Community to Enterprise Migration
Community to Enterprise isn’t a version migration; it’s an edition change on the same version: new licensing, a set of Enterprise-only apps, and access to Odoo.sh hosting and the official upgrade service. Businesses typically make this move for full accounting localisation, specific Enterprise apps, or the managed platform.
We implement both editions with no licensing commission bias, so the recommendation you get is the honest one.
What moves, and how
- What Enterprise actually adds. Enterprise-only apps and features: the full accounting experience with localisations and reporting packs, Studio, advanced planning tools, mobile apps, VoIP, and the Odoo.sh hosting platform with its staging workflow.
- The mechanics of switching. Same database, same version: the move installs Enterprise code and licensing, then enables the apps you’re paying for. Downtime is minimal; the work is in configuring the newly available features properly.
- Cost model change. Community is free software (you pay for hosting and services); Enterprise is per-user subscription. The honest comparison is subscription cost versus the Enterprise features you’ll genuinely use plus any custom code they let you retire.
- Custom code compatibility. Community-built custom modules run on Enterprise. Occasionally an Enterprise app supersedes a custom module, which is a happy retirement, not a conflict.
- Odoo.sh as part of the move. Many Community-to-Enterprise moves pair with a hosting move to Odoo.sh; see on-premise to Odoo.sh for that half.
How an edition change runs
- Decide what Enterprise is actually for. We map the Enterprise-only apps or localisations you need against what the subscription costs, so it’s a decision rather than a default. No licensing commission on our side to cloud the recommendation.
- Custom code compatibility check. Your Community-built modules are reviewed against Enterprise, flagging the rare cases where an Enterprise app supersedes something custom you’d retire rather than port.
- Enable and validate on staging. The switch installs Enterprise code and licensing on a staging copy of the same database, and the new apps get configured and tested before anything touches production. No data migration is involved, which makes this lower-risk than a version jump.
- Retraining where it’s needed. Enterprise changes some workflows and adds apps, so the affected users get briefed rather than left to discover the differences in week one.
- Cutover and subscription live. A short planned switch on production, then the ongoing subscription and any paired hosting move. Reversible in principle, though rarely worth reversing once the localisations are in daily use.
Common questions
Is Enterprise worth it for us?
Count the features you'd actually use, price the user subscription honestly, and compare against Community plus targeted custom work. Sometimes Enterprise wins clearly (accounting localisation alone can justify it), sometimes Community remains right. We'll do that sheet with you.
Can we go back to Community later?
Practically it's awkward once you depend on Enterprise apps and data structures. Treat the move as one-way for planning purposes and decide accordingly.
Do our users need retraining?
No, the interface is the same. Training applies only to newly enabled Enterprise apps, delivered as part of the switch.
What does Enterprise actually cost per user?
Enterprise is a per-user subscription, and all apps are included in that per-user price rather than billed per app. The rate varies by region and plan and changes over time, so we price it against your real user count rather than quote a number that dates. The point is checking whether Enterprise's added value justifies the per-user cost.
Will our custom modules keep working on Enterprise?
Almost always yes: Community-built custom code runs on Enterprise unchanged. The exception is where an Enterprise app now does natively what your custom module did, in which case retiring the custom code is usually the better outcome, not a cost.
Not sure where to start? Book a free discovery call and we’ll map your current setup, or request a free Odoo health check if you’re already running Odoo.