Odoo Updates · Editions
Moving from Odoo Community to Enterprise: how the switch works
The switch itself is a short, documented procedure. The planning goes into everything around it: hosting, version upgrades, the modules that filled Enterprise's gaps, and how Odoo counts your users.
Key takeaways
- Enterprise is extra add-ons on the Community server. Your data stays where it is.
- On-premise: back up, stop, add the Enterprise code, install web_enterprise, register.
- An edition switch and a version upgrade are separate operations. Plan the order.
- Check every OCA and custom module against the Enterprise apps that now cover the same ground.
- Odoo documents no way back, so rehearse the switch on a copy first.
Most Community databases that move to Enterprise do it for a reason that has been building for a while: an Enterprise app that would replace a spreadsheet, a custom module that has become expensive to maintain, or a wish to stop hosting Odoo in-house. The switch itself is one of the better-documented operations in Odoo. The work around it, checking modules, users, hosting and version, is where the planning goes.
This guide follows Odoo's own documentation for each step and links to it, so you can check the source. It assumes you know your way around an Odoo server.
When the move is worth it
We have compared the editions in detail in Odoo Community vs Enterprise, so we will not repeat the feature list here. The short version: the move pays off when an Enterprise app replaces work you do by hand or pay a developer to maintain, and when you want Odoo, rather than your own team, to carry the standard code through each upgrade. If you only need one or two missing features and a well-maintained OCA module covers them, staying on Community can still be the right call.
Timing matters too. If your Community database runs 17 or older, it is already past the end of its three years of standard support, and the edition switch and the version upgrade should be planned together. Our post on Odoo 17 end of support covers what that means.
What the switch actually changes
Enterprise is not a separate program. Odoo's source installation guide describes the Enterprise repository as a collection of extra add-ons. The server code is the Community edition, and running Enterprise means adding the Enterprise folder to the addons path, ahead of the other paths. Both repositories are checked out on the same version branch.
That is why the switch keeps your data where it is. Partners, products, invoices and stock moves stay in the same tables, and the Enterprise modules install on top. It is also why the switch does not change your version: a 17 Community database becomes a 17 Enterprise database, and moving to a newer version is a separate operation. The documented procedure installs one module, web_enterprise, which brings the Enterprise interface. The Enterprise apps you want come afterwards, installed one at a time, which lets you test each against your existing modules.
The documented on-premise switch
Odoo's page Switch from Community to Enterprise gives five basic guidelines: back up your Community database, shut down the server, install the web_enterprise module, restart the server, and enter your Enterprise subscription code. The detail depends on how Odoo was installed, and the page covers the Linux package installer, a source install and Windows.
| Step | What Odoo's documentation says to do | What we watch for |
|---|---|---|
| 1. Back up | Back up the Community database. | Include the filestore, and prove the backup restores before you touch anything. |
| 2. Stop Odoo | Stop the service (sudo service odoo stop for a package install) or your usual launch command. | The database is offline for the switch, so book a quiet window. |
| 3. Add the Enterprise code | Install the Enterprise .deb over the Community package, or add the Enterprise folder to --addons-path. On Windows, uninstall Community (PostgreSQL stays) and run the Enterprise installer into the same folder. | The Enterprise code must be the same major version as the database. |
| 4. Install web_enterprise | Update the database with -i web_enterprise --stop-after-init. | On a large database this takes time, which the documentation warns about too. |
| 5. Restart and register | Restart, log in as usual, and enter the subscription code you received by email. | The server must be able to reach Odoo's subscription servers. |
Step 4, Linux package install
sudo -u odoo /usr/bin/odoo -c /etc/odoo/odoo.conf -d <database_name> -i web_enterprise --stop-after-initOdoo's page prints the command as /usr/bin/odoo-bin; the Debian package installs it as /usr/bin/odoo, and running it as the odoo user with the service's config file gives it the database credentials and the addons path.
Registration is where on-premise switches most often stall. Odoo's on-premise documentation says you enter the code in the banner on the app dashboard, which turns green and shows the expiration date when it works. The database checks in with Odoo once a week, so the server needs outgoing access to services.odoo.com on port 80 for Odoo 18 and later, or services.openerp.com for 17 and earlier, with a documented port 443 alternative if your policy blocks port 80. Only one database can be linked to a subscription.
Rehearse on a duplicate. Run the whole switch on a copy of production first, install the Enterprise apps you plan to use, and test the flows that touch your OCA and custom modules. Because only one database can be linked to a subscription, make test copies with the database manager's duplicate function and register production when you cut over.
Moving to Odoo.sh or Odoo Online instead
Switching edition is also the moment many teams stop hosting Odoo themselves. Both of Odoo's hosted platforms run Enterprise, and both have conditions.
Odoo.sh needs an Enterprise subscription that includes Odoo.sh, and you enter that code when you deploy the platform. You can import an existing database as long as it runs a supported version of Odoo. Custom and community modules go into the project's GitHub repository, where Odoo.sh detects them. Plan storage for the import: the documentation asks for four times the size of the dump in free space. After the import, the database counts as a duplicate and is unlinked from the subscription, so you unlink the old database and register the new one. The import instructions do not describe a separate path for Community databases, so we switch a copy to Enterprise first, check it, and import that.
Odoo Online is stricter. Odoo's hosting documentation says Odoo Online is not compatible with non-standard apps and that the database's current version must be supported. The transfer means duplicating the database, uninstalling every non-standard app in the duplicate, taking a dump with the filestore, and opening a support ticket with your subscription number and the details Odoo asks for. Odoo strongly recommends a test deployment first. For a Community database that runs OCA or custom modules, that is a real decision: each one is replaced by a standard feature or given up.
Combining the switch with a version upgrade
Many Community databases reach this decision on an older version, and it is tempting to do everything at once. Odoo's documentation keeps the two apart. Its upgrade page lists switching editions, for example from Community to Enterprise, among the things an upgrade does not cover, and the upgrade platform's upload form asks for an Enterprise subscription code. Once you are on Enterprise, the upgrade service is part of the subscription: the same page says upgrading to the most recent version is free with Odoo Enterprise, including support to fix discrepancies in the upgraded database.
So we plan two operations and settle their order during the audit. One route is to switch first and let Odoo's upgrade service carry the Enterprise database forward. The other is to bring the Community database to a supported version with the OCA's OpenUpgrade project and switch there. Which fits depends on your modules and on the Enterprise versions available to you. Either way, the hosted platforms only accept supported versions, so the upgrade comes before any move to Odoo.sh or Odoo Online.
The version jump is where the engineering time goes, not the edition switch. SF Dyes moved from Odoo 13 to 18 in one migration, with every custom module rewritten and zero disruption at go-live, and our Odoo upgrade and migration work follows the same five stages, each with exit criteria. Our guide to what an Odoo upgrade costs explains what drives the quote, and the custom module guide for 16 to 19 shows what the rewrite involves.
Custom and OCA modules: check for overlap
The switch itself is the short part. What needs care is what happens next, when you install Enterprise apps beside modules that were filling the same gap.
Community databases often carry OCA or custom modules that do something Enterprise also does, because that was the only way to get the feature. Once the Enterprise app is installed, two pieces of code may extend the same model, add fields that mean nearly the same thing, put buttons on the same form, or hook into the same workflow step. Sometimes they coexist. Sometimes both run and you get duplicate actions, or one overrides the other and a rule you relied on quietly stops applying.
We work through it module by module. For each non-standard module, we ask which Enterprise app covers the same ground, if any, then decide whether to keep it, replace it with the Enterprise feature, or retire it. Replacement usually wins when Odoo maintains the app and carries it through upgrades, but only once the data the old module holds has a new home. Uninstalling a module in Odoo removes the models and fields it added, along with their data, so migrate or export first.
Studio changes the math for small modules. The upgrade service covers Studio customizations as long as Studio stays installed and subscribed, so a module that only adds a few fields or adjusts a view may be cheaper to rebuild in Studio than to maintain as code. Code you keep as a custom module stays yours to upgrade, unless you put it under a maintenance of customizations subscription, which Odoo charges by lines of code.
Licensing and user counts
Community has no user fees, so Community databases tend to collect users. Enterprise is priced per user, and it pays to know how Odoo counts before you sign.
Odoo's pricing page defines a paying user as someone with access to the Odoo backend to create, view or edit documents, or an employee record in the HR app with no linked user. Customers and suppliers who use the portal are free, as are website visitors who place orders. The Enterprise Subscription Agreement adds detail: deactivated accounts and portal users are not counted, and, where your version supports Light Users, an active employee record in the HR app that is not linked to an active internal user counts as a Light User, a lower-cost license with limited access. Otherwise the pricing page counts that employee as a paying user. Before the switch, deactivate the accounts of people who have left, move external people to portal access, and review employee records that have no user.
The plan matters as well. The pricing page puts on-premise and Odoo.sh hosting, multi-company, Studio and use of the external API in the Custom plan, while the Standard plan runs on Odoo Online only. A Community database with more than one company, or with outside systems calling Odoo's API, belongs in Custom. We do not quote prices here because they change; the pricing page has the current figures, and Odoo.sh hosting is billed on top.
On-premise, the count is checked for you. If a registered database has more users than the subscription provides, Odoo shows a message, and you have 30 days to add users to the subscription or deactivate some before the database expires.
Can you go back to Community?
Not in any way Odoo supports. Its documentation covers Community to Enterprise and nothing in the other direction, and its upgrade page lists downgrading to a previous version and switching editions among the things an upgrade does not do. The license points the same way: when the subscription ends, the agreement revokes the Enterprise license and the customer agrees to stop using the Enterprise software.
The practical obstacle is data. After a year on Enterprise, part of your data lives in Enterprise apps, and those apps also add fields to standard models. Taking them out means uninstalling modules, which deletes what they stored, or rebuilding on Community and importing what you can. Either way it is a migration project, not a switch. Treat the move as one-way, which is one more reason to rehearse it on a copy.
Frequently asked questions
Can we switch from Odoo Community to Enterprise without losing data?
Yes. Enterprise is a set of extra add-ons that runs on the Community server code, so the switch installs modules on your existing database rather than moving data out of it. Back up first, and run the switch on a copy before production.
Can we switch editions and upgrade versions at the same time?
Plan them as two operations. Odoo's upgrade documentation lists switching editions among the things an upgrade does not cover, and the upgrade platform asks for an Enterprise subscription code. We settle the order during the audit, then rehearse both on a copy.
How does Odoo count users on Enterprise?
Odoo counts active users with access to the backend. Deactivated accounts and portal users are not counted. Under the Enterprise Subscription Agreement, where your version supports Light Users, an active employee record with no linked user counts as a Light User; otherwise the pricing page counts it as a paying user. On-premise, a database with more users than its subscription has 30 days to add users or deactivate some before it expires.
Can we go back from Enterprise to Community later?
Odoo does not document a way back. Its documentation covers Community to Enterprise only, and the Enterprise license ends with the subscription. Uninstalling Enterprise apps deletes the data they hold, so treat the switch as one-way and test it on a copy first.
Moving to Enterprise?
Bring your version, hosting and module list, and in 30 minutes we will map the switch with you.
Book a discovery callKeep going
Related services and articles
Switch and upgrade in one plan
Custom modules audited and rewritten, data verified against the source before cutover.
Odoo upgrade and migration servicesSort out the module overlap
Upgrade-safe custom modules and integrations, rebuilt or retired where Enterprise now covers the ground.
Odoo customization and integration Odoo UpdatesOdoo Community vs Enterprise: a 2026 practical evaluation
Features, accounting gaps, hosting rules and total cost of ownership, from a partner that implements both.
Odoo UpdatesUpgrading custom Odoo modules from 16 to 19: what changes
What breaks in custom modules across three releases, with the old and new code side by side.
Plan your move from Community to Enterprise
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751