Migration From
Unreal Engine
Your chapter-by-chapter roadmap from UE to Unity. Translate what you already know into Unity's world — concepts, code, and workflows.
What This Migration Guide Helps You Translate
This guide is for Unreal Engine developers who already understand actors, components, Blueprints, scenes, collision, and gameplay scripting, but need the Unity names, workflows, and C# patterns that map to those habits. It is not an engine-war article; it is a practical translation layer for building faster in Unity.
Start with concepts
The first chapters map Unreal terms to Unity terms: Actors to GameObjects, Components to MonoBehaviours, Levels to Scenes, and Blueprint graphs to C# scripts. Use the chapter cards below when you need the direct equivalent.
Then connect real scripts
After the naming layer makes sense, pair the guide with the Unity script library, the complete game systems, and the free Unity C# scripts guide to turn the migration notes into working project code.
Chapters
4Concepts & Naming
What Unreal calls X, Unity calls Y
Map your Unreal Engine mental model to Unity equivalents — actors, levels, blueprints, and more.
Scenes & Level Structure
From UE Levels to Unity Scenes
Learn how Unity scenes compare to Unreal levels — loading, management, and multi-scene workflows.
Scripting: Blueprint vs C#
From visual nodes to clean C# code
Compare UE Blueprints and C++ with Unity's C# scripting — lifecycle, events, coroutines, and more.
Physics & Collision
Rigidbodies, colliders, and raycasting
Translate your UE physics knowledge to Unity — rigidbodies, collision layers, triggers, and raycasting.