In brief Before any Odoo 20 migration, a structured inventory identifies what is genuinely in use, what has been custom-built and what communicates with external systems. This step prevents unpleasant surprises in production and sets project priorities from the very first week.
The team opens the session. The screen displays the list of applications installed in the current Odoo database. The question that immediately presents itself: what does the business actually use? This is the starting point of any serious Odoo 20 migration. Not a shortcut, not a formality: a methodical inventory that determines everything that follows.
This article is the first in a series of eight episodes. The journal follows the project steps in order: inventory, test database, custom modules, first migration run, gap analysis, user acceptance testing, go-live, retrospective. Each episode documents the method, not invented results.
Which applications are genuinely in use?
Installed does not mean used. The first task is to distinguish between the two. For each application, identify the date of the last record created per model, the number of active users per department and the menus that have never been opened.
Stock managed in an external spreadsheet should be noted at this stage, as it calls for Odoo's native replenishment rules. This kind of parallel workflow carries as much weight as a module installed in the database.
This functional review goes beyond a simple technical list. It aligns the inventory with the business's real priorities. For more on what the target version delivers natively, see what's new in Odoo 20.
Which custom modules will carry through the migration?
Specific developments are identified by their author in the application list: any module whose author is not Odoo SA deserves an entry in the register. Distinguish between in-house modules, third-party modules and modules produced by the integrator.
The odoo-bin cloc command, available in the Odoo 20 source code, measures the volume of code specific to your database. It provides a first estimate of the porting effort to plan for. Sorting through each module and deciding whether to port or replace it is covered in episode 3.
Who talks to Odoo from the outside?
The integration inventory is often the most underestimated part. You need to catalogue automated scripts, e-commerce or logistics connectors, active API keys and all XML-RPC or JSON-RPC calls coming from third-party systems.
One documented fact to check right now: according to the official Odoo 20 documentation, the db service from the old XML-RPC and JSON-RPC entry points has been removed in this version. Any script that creates or duplicates databases via this service must be identified and reviewed before starting the migration. Missing this point mid-project costs time. If you have doubts about a specific integration, the support team can assist you throughout the project.
Which reports and data actually matter?
The fourth area covers everything that structures information in the database. List custom reports and document templates, automated and scheduled actions, fields added through configuration and large attachments.
Each item receives a functional label: what it does, who uses it and how often. This qualification directly prepares the testing and validation phase later in the journal.
What decisions need to be made by the end of the week?
The inventory leads to a decision table with four columns: keep (compatible without modification), port (adapt for Odoo 20), replace (functionality covered natively by the new version) and remove (no longer in use). This table becomes the roadmap for the episodes that follow.
To frame this analysis and planning work, draw on Odoo integration consulting support from the very start of the project.
- Installed applications vs applications in use: list established
- Last record created per model: checked
- Active users per department: catalogued
- Menus never opened: identified
- Custom modules: listed with their author
- Volume of specific code measured with odoo-bin cloc
- External scripts and connectors: inventoried
- XML-RPC and JSON-RPC calls using the db service: flagged
- Reports, document templates and custom fields: listed
- Keep / port / replace / remove table: completed
Episode 2 opens the test database: how to prepare it, what data to load and what criteria to validate before making any changes. The series continues every week.
Would you like an expert to carry out this inventory before you decide anything? Request a free audit: the team will analyse your database and provide you with a ready-to-use inventory register.