Migrated assets still reference Script/OldProject

I have started a new project and am trying to migrate assets from the old project. I am following the process described here.

As far as I can tell, all dependencies are selected. The asset migration to the new content folder appears to succeed, and I receive a message that it did. But when opening the new project, I cannot open any of the assets, and trying produces this error:

[2015.09.02-02.07.49:902][494]LoadErrors:Error: Error /Game/Assets/Items/DA_Item_Water : Can't find file for asset. /Script/TestProj

Where TestProj is the name of the old project, not the new one. The binary files when examined with the “strings” command still reference Script/TestProj. I don’t even know what that “Script” reference is: it’s nothing I ever added on purpose to any of my assets, but it’s present in all of them, and the fact that it still references the old project means I can’t use any of the migrated assets in the new project.

What am I missing? I selected the “Content” directory as described, and got the “successful” content migration message after migrating. Yet, they don’t work :-(.

On further investigation, this only seems to be a problem for assets I’ve made which derive from the UAssetData class. I have moved a bunch of material assets between projects using the very same process with apparent success.

Perhaps custom assets cannot be so moved?

Edit: That appears to be so. I’ve moved many other assets across projects and it’s all fine except custom assets deriving from UDataAsset.

However, that’s kind of a big deal, IMHO :).

Hi, did you get anywhere with this issue at all? Currently trying to migrate all my content over and noticed the exact issue that my blueprint, which links to some C++ code had a script/OldProj reference so my new project just wont load them up.