Unreal to Godot, what moves, what you rebuild and when to stay

The open source Unreal to Godot Exporter by vortechU has two halves, a Python plugin inside Unreal and a GDScript addon inside Godot. It exports meshes to glTF and the level layout to JSON, then rebuilds the level in Godot with collision shapes, PBR material parameters, lights, decals, foliage as MultiMesh, landscapes through the Terrain3D plugin and navigation regions. Its README states plainly that it is not a project converter and that gameplay logic, Blueprint graphs and systems do not come across.

Relative Games' Unreal To Godot Exporter covers similar ground, including skinned meshes with animation, spline meshes, terrain after converting landscapes to static meshes, and materials converted to visual shaders or StandardMaterial3D, and can generate a Godot project. GameFromScratch's launch coverage lists it as Windows only and names what it does not handle, such as cloth, particle emitters, subsurface scattering and runtime virtual textures.

Use either to move a level's content quickly, then check scale, material look and collision on one level before you export the rest.

There is no format another engine can run a Blueprint from. Blueprints are stored in binary .uasset files and call into Unreal's framework, and your C++ gameplay classes inherit from Unreal types such as AActor and ACharacter. The logic moves as knowledge, not as files.

The concept table above covers the everyday mappings. The one that takes longest is movement. Unreal's Character Movement Component bundles several movement modes and their rules into one component. Godot's CharacterBody3D gives you move_and_slide() with wall and slope detection, and you write the movement rules yourself. That is more work up front, but every rule is visible in your own script.

Teams with most of their logic in C++ usually move faster than Blueprint-heavy teams, because the spec is already text. Blueprints can become text too. Nodes you select and copy in the Blueprint editor paste as plain text, the format sites such as blueprintUE use to share graphs, so save each graph's text with a short note on what it does.

The Fab Standard License lets you use assets commercially, modify them, ship them inside your projects and use them with any compatible tools, and it states that usage is not limited to Unreal Engine. You may not resell or redistribute the assets on a standalone basis. The Personal and Professional tiers grant the same rights and differ only by the buyer's revenue, with Personal for buyers under 100,000 USD in gross revenue in the last 12 months.

Older purchases can differ. Content bought under the UE Marketplace licence is governed by the Epic Content License Agreement, which defines UE-Only Content as content designated for use only with Unreal Engine and Unreal Engine based products. If a pack was marked UE-Only, it stays in Unreal. Fab's documentation also notes that if a creator adds new file formats on Fab, those new formats come under the Fab Standard License, while the old format keeps its Marketplace licence. Creative Commons listings follow their Creative Commons terms. Megascans are the other common catch. The Epic Content License Agreement says Megascans content acquired while your account was on the Unreal Engine plan may only be used as UE-Only Content, so free Megascans pulled into an Unreal project usually stay in Unreal.

Unreal's EULA charges a royalty of 5% of gross revenue, and nothing is owed until a product directly generates more than 1 million USD in lifetime gross revenue. Revenue from sales on the Epic Games Store, and in-game purchases that use Epic's payment services, is excluded from the calculation. So a game that grosses 1.5 million USD on Steam owes 5% of the 500,000 USD above the threshold, which is 25,000 USD.

Epic also announced Launch Everywhere with Epic, which lowers the rate to 3.5% from January 1, 2025 for Windows, macOS and Android games that release on the Epic Games Store no later than on other stores. For the large majority of indie games, which never reach 1 million USD, the royalty costs nothing. Move for workflow, performance or platform reasons, not for the royalty alone. Summer charges no royalty and takes no revenue share on games made with it.

Nanite and Lumen are features of Unreal's renderer, not properties of your assets. Content built to rely on them, such as film-quality meshes with no LODs or scenes lit only by Lumen, needs rework in any other engine.

Godot 4 offers VoxelGI, SDFGI and screen-space indirect lighting in the Forward+ renderer, while LightmapGI and reflection probes work in every renderer. For mobile, LightmapGI and reflection probes are the only supported options. Plan the lighting per scene, and budget time for LODs on anything that depended on Nanite.

Stay if your game's look depends on Nanite, Lumen or MetaHuman, if your team's skill and tooling are built around Blueprints, or if the game is close to release. A port is a rebuild of every system, and that time usually matters more than any engine difference.

Consider moving if you are making a stylized or 2D game that never needed a high-end renderer, if editor size and build times slow a small team down, or if you want every movement and gameplay rule in plain script you can read. Summer is a desktop engine for macOS and Windows, compatible with Godot 4 workflows, with an agent that rebuilds systems from your notes and code, and it exports desktop builds for Steam and itch.io.