Import/Migrating assets properly from another sample or project

NeoMurakami · January 19, 2026, 3:39am

Hi, I am consistently running into issues with moving around and migrating assets from sample projects to my project or even moving assets around within my own project without breaking references.

Is there a proper way of migrating assets or moving them?

For example, I am interested in migrating the PCG assets along with all of their dependencies from the ‘Electric Dreams‘ demo project to my project. I tried Right-Clicking the PCG folder and selecting the ‘Migrate‘ option which seems to include all the neccessary materials, textures, and blueprints required which is what I wanted.

Upon selecting the Content folder of my new project (would really like to know how I can also migrate the assets a subfolder), the materials dont load properly.

I can even see the texture is assigned properly in the parent material

I’ve tried using the ‘Update Redirector References‘ which seems to do nothing.

I have seen this problem before which some of the cause was the conversion of Regular Textures to Virtual Textures when I import. That prevented some materials from compiling. I was able to fix that manually. Every imported material I open from the imported materials dont have errors and there are an extremely lot of materials to go through to check.

So again, my original question is, how can I properly migrate assets from one project to another?

brs-sebascova · January 20, 2026, 8:31pm

Hello there @NeoMurakami!

Migration can be a quite daunting task, yet I think your process so far has taken the correct steps. In regards of a “proper” method to migrate assets to a new project, it can be summarized like this:

1. Match plugins in both origin and target projects
2. Match rendering settings as well
3. Migrate everything from /Content
4. Restart the editor after transfer
5. Reopen, then fix up all redirectors
6. Only reorganize files from this point onwards
7. Clear up your cache to get rid of any lingering old files

As for the virtual texture problem, when migrating, the engine can sometimes auto convert textures to VT, making a bit of a mess.

You can force UE to avoid this effect, via disabling VT support before migration. Go to Edit > Project Settings > Engine > Rendering, look for Virtual Textures section, and disable “Enable Virtual Texture Support”.

After that, close UE, and perform a cache clear, via deleting folders Saved, Intermediate, and DerivedDataCache from your main directory. Finally, open back the project, let it rebuild, and perform the migration.

For further steps, it’s always helpful to revisit the migration docs from Epic. You can find the guide for the migration tool below, as well as an alternative from the community, which uses manual migration with a custom plugin. Please give it a look: