Datasets:
File size: 3,360 Bytes
2b7a1dd | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 | ---
license: lgpl-3.0
language:
- en
pretty_name: Odoo Model and Field Changes, Odoo 16 to 20 (Community)
tags:
- odoo
- erp
- code
- software-upgrades
- schema
size_categories:
- 10K<n<100K
configs:
- config_name: changes
data_files: data/changes.csv
default: true
- config_name: fields
data_files: data/fields.csv
- config_name: models
data_files: data/models.csv
---
# Odoo Model and Field Changes, Odoo 16 to 20
Which models and fields were added, removed or renamed between Odoo 16, 17, 18, 19 and 20, for **Odoo Community**. Built by parsing the Odoo source code of each release.
Use it to plan an upgrade, to check whether a custom module still points at fields that exist, or to give an AI coding assistant accurate facts about a specific Odoo version.
Browse the same data, with Enterprise coverage and upgrade notes, in the free [Odoo Change Explorer](https://snmdigitechconsulting.com/odoo-changes).
## Files
| Config | Rows | One row per |
|---|---|---|
| `changes` | 8,662 | model or field added, removed or renamed in one upgrade step |
| `fields` | 18,984 | field of a model, with the versions it exists in |
| `models` | 1,230 | model, with the versions it exists in |
### `changes`
| Column | Meaning |
|---|---|
| `step` | Upgrade step, such as `19->20` |
| `change` | `model_added`, `model_removed`, `model_renamed`, `field_added` or `field_removed` |
| `model` | Technical model name, such as `res.partner` |
| `field` | Field name, for field changes |
| `field_type` | Field type, such as `Many2one`, for field changes |
| `module_or_new_name` | The module that defines it, or the new model name for `model_renamed` |
### `fields`
`model`, `field`, `type`, `relation` (the related model for relational fields), `label`, `module`, then `in_odoo_16` to `in_odoo_20` as true or false.
### `models`
`model`, `description`, `module`, then `in_odoo_16` to `in_odoo_20` as true or false.
## Quick start
```python
from datasets import load_dataset
changes = load_dataset("msubash96/odoo-model-changes", "changes", split="train")
removed = changes.filter(lambda r: r["step"] == "19->20" and r["change"] == "field_removed")
print(removed.select(range(5)).to_pandas())
```
## How it was built
A static parse of the Python models (`_name`, `_inherit`, `_inherits` and `fields.*` declarations, with mixins merged) of every module in each release. A field counts as removed only when no parent, mixin or delegated model still provides it.
- **Sources:** Odoo 16.0, 17.0, 18.0, 19.0 and 20.0 Community.
- **Scope:** models and fields defined by Community modules only. Models and fields that come only from Enterprise modules are left out.
- **Generated:** 2026-10-14.
## Limits
- Field renames are not detected as renames. A renamed field appears as one `field_removed` and one `field_added`.
- Changes in field attributes, such as a new `required` or a changed selection list, are not included.
- Fields added at runtime, outside the Python declarations, are not seen.
## License and credit
The data is derived from Odoo Community source code, which is licensed under LGPL-3.0, so this dataset uses the same license. Odoo is a trademark of Odoo S.A. This dataset is not made or endorsed by Odoo S.A.
Compiled by [Subash Magar](https://subashmagar.com) at [SNM Digitech and Consulting](https://snmdigitechconsulting.com).
|