Migrating blueprints from one project ot another makes dead actors

Tried to migrate some my blueprints from one project to another. While some blueprints and assets where parented from c++ migration of them failed. It produced blueprints parented from unknown classes, despite c++ classes where copied before, but the have different project API.
And there is no way to fix parents of those bluerpints

Hey -

Trying to migrate custom code / code based blueprints causes reference errors in the blueprint which corrupt it when you try to open. This is a known limitation that we would like to address in a future update to the engine, however there is no timeframe for this functionality at this time.


This is still an issue.