Hi, Thank you for your answer and, of course, I am very thanffull to OCA contributors too !
My surprise is about Odoo.com : they should have already done the job to migrate the databases they manage. So, don't they share this code with community ? So, in my understanding, they oblige the community to do the job a 2nd time : I feel that it would not be quite "open-source spirit" isn't it ?
Do you have any information about that ?

Hey Herve,
in general i do understand your statement concerning the open-source-spirit.
But does the open-spirit means to you, that it must provide of straight forward solution for migrating you db´s that must be available as soon as a new release is out? Its more or less the possibility to use Odoo CE free. Thats it. And thats where the OCA comes into the game with OpenUpgrade if you dont want to migrate manually. But in the end you are still on your own to succeed the migration.

As the migration process provided by Odoo is an enterprise feature... It pretty clear that they do not share the migration code with the community. Its a service they provide to licensed customers. Thats market economy at least...

Just to make sure.... are we talking about Odoo SH instances? Or does this problem refers more to CE intances... I think you are aware of the fact, that if you implement user specific code, 3rd party apps (also OCA modules), that you are facing issues concering the migration process. You should always keep that in mind.

I do follow the OpenUgrade Repo for quite a while now and the people working on it provide a lot of work on it. I just can advise you to contribute to the OCA if you can. More people active on it, means a faster dev and probably better solutions due to more brains involved.
Any maybe this will increase the Open-Source-sprit for you as well.

In the end it is always a question of the benefit-effort-ratio. For everybody...

Hi Nils,
I agree with you about "Odoo corp" developping code about migration scripts and the migration service they provide with enterprise licence : there is a price for that, it is the "double pricing model" that Odoo corp adopted some years ago, F.Pickaers tell that is was mandatory to sustain Odoo software evolution and, after some years, I think we can all see that it was not only words : The quality of Odoo today as software and business tool is undenyable and the money licences put into it is not nothing about that !
A point is that I know about the Odoo migration process for Odoo EE instances (whatever they are instéalled on Odoo.sh or on premices, and I know also the migration OCA process with Openupgrade because I used it to migrate successfully my own instances from v14 to v15 with OCA modules, third party modules and my inhouse developed modules embedded (I plan do migrate also other instances from v12 to v16 but it will be another story).
So, I wrote my post after migrating quite easily an instance from v14 to v15 and migrating my inhouse code from v14 to v15 and v16, and I found that the migration script in Openupgrade for such a quite widely spread module as 'account' (='invoicing') was only initiated.
My point is not at all 'against' OCA : they do a wonderfull job, and if CE version did not exist, I surely not be an Odoo integrator today, and CE exists because OCA continues to live the best they can.
My point is only about Odoo (and me) : I knew that the EE code (repository 'entreprise') is not 'free' and, once again, I am ok with that, but, as Odoo corp continues to let free their odoo/odoo repository and authorize OCA to clone it into OCA/OCB, I thought that it was the same 'pricing strategy' for the migration scripts, and I was surprised when I understood that it was not.
So, my concern it that I think Odoo is doing something which is not 'ethic', respect to the sprit of open-source code : they oblige the Odoo community to re-develop a piece of code which do exactly the same job as a code they already developed. I thought that it was enough for Odoo to put in EE codes like accounting, but here they put also the ability to migrate to new CE versions quite quickly + oblige to develop the migration scripts twice (one for odoo, one for oca).
It looks a little bit like Odoo would have been pleased to go fully to the commercial EE model, or to let free only obsolete versions of Odoo, but they were empeached to do that because the core code was already strucked with the community and so they were still almost obliged to let the repo odoo/odoo open-source and free, isn't it ?
(conclusion : I'm surely on the path to contribute to Openupgrade migration scripts soon ... as soon as I get free time to do that ...), Best regards, Herve

Hey Herve,
never mind! As mentioned... I do understand your approach...
I just dont think that this kind of discussion will lead to anything in this forum here.

From technical aspect the mentioned options are there (from my level of knowledge). And i guess you will be welcome in the OCA for contribution.

Cheers
Nils