Unreal Engine 4.26 Documentation

Unreal Engine 4.27 Documentation

Unreal Engine 5.0 Documentation

Unreal Engine 5.1 Documentation

Unreal Engine 5.2 Documentation

> Understanding the Basics > Assets and Content Packs > Migrating Assets to UEFN

Light Theme

Dark Theme

Migrating Assets to UEFN

Using the Migration Tool to Migrate Assets from Unreal Engine to UEFN.

On this page

Using the Migration Tool
Limitations

You can use content originally created in Unreal Engine 5 (UE5) in Unreal Editor for Fortnite (UEFN). UEFN supports a wide range of UE5 asset types.

The preferred asset migration workflow is to use the Migration Tool in the Unreal Editor, and select the Content folder in your UEFN project as the target destination.

This migration path provides a means to reuse your previously-saved assets from UE5 in new UEFN projects, while also leveraging the new features and Fortnite content available in UEFN.

UEFN does not support all of Unreal Engine's asset types. Further, some supported asset types have additional limitations to comply with Fortnite performance requirements. For example, Static Mesh assets should not exceed 20k vertices. Read about UEFN asset limitations here.

Using the Migration Tool

The Migration Tool was updated in Unreal Engine 5.1 to support UEFN as a target destination.

Prerequisites

To move content from UE to UEFN with the Migration Tool, your projects must meet the following minimum version requirements.

Source — An Unreal Engine project running in UE 5.1 or newer.
Destination — A UEFN project running on Fortnite 23.00UEFN or newer.

Procedure

Use the following steps to migrate content from UE to UEFN with the Migration Tool.

Open the Unreal Engine project from which you want to migrate assets.
Right-click an asset or folder in the Content Browser to display the context menu and select Asset Actions > Migrate.
Review the Asset Report dialog and click OK to confirm you want to migrate the selected assets. For assets with dependencies, such as a Static Mesh with associated Materials and Textures, the entire dependency tree is displayed. You can uncheck any assets you don't want to migrate, but be aware that you can break asset references if you do this.
In the file browser dialog, open your UEFN Project folder. Navigate to Plugins > Project Name > Content, and click Select Folder.

You must select the base Content folder of the UEFN Project, otherwise the migration will fail. If the asset or its dependencies are located deeper in your UE5 folder hierarchy, those additional folders are automatically created in the UEFN project.

The asset and its dependencies appear in the Content Browser of your UEFN project. You can now drag the asset into your Level.

Limitations

The Migration Tool is not aware of the content limitations of the destination, so it cannot perform any sort of asset validation when you attempt to migrate content. In other words, the Migration Tool will migrate your assets whether or not they are actually compatible with UEFN.

As noted above, UEFN has many asset limitations. For example, some asset types cannot exceed a certain size, and some UE5 asset types are not supported at all.

The current implementation of the Migration Tool needs to load all the assets in memory to migrate them. This tool is in active development. We expect to provide performance improvements and a better user experience for validating and cleaning up incompatible content in the future.