Assume a customer wants to migrate their M5 app to M6 and its new uI framework.

They used a multifield with a transformer storing data as a multivalue property https://documentation.magnolia-cms.com/display/DOCS61/Transforming+field+values#Transformingfieldvalues-MultiValueTransformer.

M6 currently offers a Multifield (a complex field holding a form potentially holding more complex fields) which ends up saved as a structure like that of https://documentation.magnolia-cms.com/display/DOCS61/Transforming+field+values#Transformingfieldvalues-DelegatingMultiValueTransformer

We should not force a data migration to the expected data structure of the new multifield, rather implement a special multi-value field, that would be bound to an array/list on the presentation side. It would look like a bunch of components of same type, and would write the data to the multivalue property.