Enonic version: 6.10.2
OS: Windows 10 64 bit
Hi, I am looking into best practices on how to handle data model changes. We now have a situation where we need to do a slight change in a mixin used in multiple content-types. This change means that the controller handling this specific data might encounter both the old data model and the new. This won’t work unless we migrate the existing data to the new model or we create code that handle both the old and the new model. The latter is something I really want to avoid.
What I want is a safe way to “migrate” existing content into the new model, and in a broader sense; I would like to have a strategy to handle these kinds of changes in the future.
How do you guys handle this kind of change?