Hi Baptiste,
I get it - as developers, you can't be forever bound by an early data model, especially when going from beta to release.
However, as a user who has invested significant time into the beta, reporting bugs and building hundreds of materials, there is serious negative impact to changing the model with no data migration strategy in place. It renders all early adopter work virtually lost. Sure, there are still JSON files around, but I have to uninstall and re-install the beta every time I want to look at an old material. I can't even have both versions open to help me recreate the v1 materials in the new version.
In my case, this will lock me to the beta for the duration of my project - which means I will have to keep building new materials in the obsolete data model, to eventually be thrown away.
Grasping at straws here to not lose this work... maybe the development or QA team had to go through a material upgrade process with testing materials from the early beta? Honestly I'd be happy for a script I could execute locally, not worried about UI integration or anything. Just something to transform this JSON to the new model.
Please consider defining a path to convert v1 beta materials into the new v2 data model.
Thanks,
Chris