Skip to Content
This question has been flagged
modulecustomstudioodoo18.0
1 Respondre
1277 Vistes
Avatar
Sylvain Albasser

Hello,

We recently moved from Odoo SaaS to Odoo SH (v18.0).


We made a lot of customizations either with Studio or manually (models and fields directly created in dev mode).

We want to move some of those models into proper modules so we can go further in customization.


I found this comment in Odoo Forum (https://www.odoo.com/fr_FR/forum/aide-1/migrating-odoo-studio-fields-to-a-custom-module-287357#answer-287426).

This works fine for a custom field in a non-custom model.

The field's state is changed from "manual" to "base".


But what about a custom model?

How one can move a custom model created manually in Odoo interface (ie. "x_model") to a custom module?


class Model(models.Model):
    _name = "x_model"

    x_name = fields.Char('Name', required=True)

^ this code does nothing. Model's and field's states remain "manual".

And a new field added in the module is not created in Odoo after update (no error in logs).


class Model(models.Model):
    _inherit = "x_model"

    x_name = fields.Char('Name', required=True)

^ this code generate the following error :

TypeError: Model 'x_model' does not exist in registry.
Avatar
Descartar
Avatar
Cybrosys Techno Solutions Pvt.Ltd
Best Answer
Hi,

When moving from Odoo SaaS (Studio) to Odoo.sh, custom models created through Studio or developer mode exist only in the database with their state set to “manual”. Defining the same model in Python using _name = "x_model" does not automatically convert it into a module-managed model because Odoo does not take ownership of existing manual models by default. Similarly, using _inherit = "x_model" fails because Studio-created models are not loaded into the registry early enough for Python inheritance during module initialization.

The correct approach is not to override or delete the existing model, but to formally take ownership of it. You should create a proper module defining the same _name as the Studio model, and then use a post_init_hook to update the corresponding records in ir.model and ir.model.fields, changing their state from manual to base. This transfers control of the model and its fields from Studio to your module.

Once this ownership change is done and the module is upgraded, Odoo treats the model as a standard module-based model. You can then safely extend it with additional fields, logic, views, and security rules, and it will behave like any other custom module model. This method is clean, upgrade-safe, and avoids risky operations such as deleting the model, renaming tables, or manually manipulating database structures.

Hope it helps

Avatar
Descartar
Sylvain Albasser
Autor

Thanks a lot.

I managed to do this using a migration script.

```
class Model(models.Model):
_name = 'model'

name = fields.Char('Name', required=True)
```

module/migrations/18.0.0.2/pre-custom.py:
```
from odoo.upgrade import util

def migrate(cr, version):

cr.execute("UPDATE ir_model SET state = 'base' where model = 'x_model'")
cr.execute("UPDATE ir_model_fields SET state = 'base' where model = 'x_model' and name = 'x_name'")

util.rename_field(cr, 'x_model', 'x_name', 'name')
util.rename_model(cr, 'x_model', 'model', ignored_m2ms=[])
```

Related Posts Respostes Vistes Activitat
New application multiple forms using odoo studio odoo10?
module custom studio
Avatar
0
de des. 17
4009
custom module on odoo V9 enterprise
module custom odoo
Avatar
0
de maig 16
5116
odoo studio computed field
studio odoo
Avatar
Avatar
1
de maig 25
5775
How to custom addons in Odoo is these steps are correct?
custom odoo
Avatar
Avatar
Avatar
2
de març 24
21052
How can we Uninstall odoo module from terminal? Solved
module odoo
Avatar
Avatar
Avatar
Avatar
3
de set. 25
24784