How to switch from Community to Enterprise

What is it for?

It answers anyone asking whether they can already switch from Odoo Community to Odoo Enterprise with fiscaldoo. Today, the answer is no: the fiscaldoo version for the Enterprise edition is not yet available to customers.

This article says what exists, what does not and what the switch is expected to change, so that you can plan.

When to use it?

• When a customer asks whether they can switch to Enterprise.
• When you want to plan the switch and tell the customer what changes.
• Do not use this article as a guide to carry out the switch: none of the technical steps have been carried out for customers.

Where to find it?

There is no menu, assistant or button for this switch. In a Community database, the menus have no entry about Enterprise.

Before you start

• You have access to the Settings app (system administrator), to confirm the edition.
• You know there must be a backup before any change to a customer's database. See Backups.

How to use it

1. Open Settings and scroll down to the About group. The first line gives the edition, for example “Odoo 20.0 (Community Edition)”. The steps are in Supported editions and versions.
2. If you are on Community Edition, keep using fiscaldoo in that edition. Do not install the Enterprise modules in the customer's database.
3. If the customer really needs Enterprise, talk to fiscaldoo support before deciding. Give the edition, the number of companies and whether the customer uses budgets, deferrals, retainers with direct debit or authorised cards.

What exists and what does not

	Today
fiscaldoo for Odoo Community	Exists: it can be installed and used.
fiscaldoo for Odoo Enterprise, for customers	Does not exist yet.
Menu, assistant or button to switch edition	Does not exist.
Team's technical procedure	Exists in the modules being prepared for Enterprise. It runs off screen, on a server, and is not yet for use on customer databases.

What the switch is expected to change

This section comes from the technical documentation of the procedure. Pending validation on screen: nothing in this section was seen in an Enterprise database, because the demo is Community.

• Carried over: budgets with their revisions, deferrals and fiscal years.
• No longer the fiscaldoo ones: the budget, deferral and exchange-rate modules, because Enterprise has its own. Exchange rates already imported remain.
• Should not change: series, numbering, signatures, ATCUD and SAF-T. The procedure compares series, numbering and the last signature before and after, and fails with the list of differences. Pending validation by a certified accountant: effect of the switch on numbering and certified series.
• Not carried over: direct debit on retainers (the retainer is carried over, without automatic collection) and card authorisations (the customer authorises again).
• Must be dealt with first: budget lines with only general accounts, because the Enterprise budget only works with analytic accounts.
• Lost: the log of exchange-rate imports and exchange revaluations. The journal entries they generated remain. The budget type (annual, quarterly, monthly) is not carried over either: in Enterprise, the period is given by the dates.

The rule of the procedure is to rehearse first on a copy of the database, never on the customer's database.

Expected result

You know which edition the database is on and what to tell the customer: today the switch is not available, and the list above shows what will need planning when it is.

Important notes

• The “Enterprise only” badge at the top says which edition the article is about. It does not mean the edition is already available.
• A company that already uses Enterprise without fiscaldoo has a different path, with the old documents marked as coming from another system. It is not available to customers either.

Common problems

I cannot find the menu to switch to Enterprise

• Symptom: you look in Settings or in Accounting › Configure › Migration and imports and there is nothing about Enterprise.
• What to do: it is not an error in your database. That menu does not exist.