Before Magnolia 4.5 a node representing an available component (paragraph in prototype for instance) will often have the same name as the value the node's name property (node data). When this is not the case (which is valid AFAIK) TransformStkBasedTemplateMigrationTask#updateAvailableComponent(node) will look for the wrong component name.

I believe the fix is to have this method use node.getProperty("name") (which is used when removing the old value!) instead of node.getName().