When a dialog provides a control of type "multiselect" the content created contains a subnode "multiselect" with the values -> see screenshot.

The problem is that the step "Update Primary type" will update the node and applies it the type "Area".. but it's not an area, it should stay a contentNode.

The goal here is to update the step "Update Primary type" of the migration process in order that it does not update these kind of nodes.
The difficulty is that only by analyzing the content you have no clue if this node is created by a "multiselect" and must stay a content node.

An analysis of the configuration is required before.

Idea:
The steps updating the content and the steps updating the configuration are more or less independent. If we want to keep them independent we should analyse the "old configuration" before running the migration of the content.

Analysis of the configuration:

• find every paragraphs that have a control "mutliselect"
• store the template and the name of the node created by multiselect in a map.

Update step "Update primary type":

• when you find a node whose the template is in the map, you should skip the process over its child with the corresponding name.