Good to hear that you are upgrading to enjoy the latest features and security updates!
Indeed, between these two versions there has been quite a few updates to the database structure. Fields have been added, renamed, etc. This is to support new features and fix potential bugs.
If you have built some customization on top of some fields that have been updating (with 7.6 or earlier), you’ll indeed have to review the changes and possibly adapt your customization.
Thanks for your answer.
My question is more about the database itself and not the customizations that I had.
I’m doing a clean install with 7.6.0. The plan is to take advantage of all the features from 7.6.0 and build some customizations on top of it (but not use prior customizations I had before).
My dev seems to say that my database structure from 7.3.1 is not compatible with 7.6.0.
I suggested to migrate the data from the old database to the new (new structure).
Could you please be a bit more specific as to what I should consider and pay attention to?
Indeed if you want to migrate your data from one version to another, you may have to go through a bit of work to manage the new fields. Because parts of the database structure has been changed, you can “move” your data with a 1 to 1 match.
This is quite specific to your own current data structure and existing customization, and it might be actually quite little work to make it match the new structure.
Did they share a few specific examples of what poses problems?