Unreal Engine’s object model is the closest architectural cousin to Unity’s of any engine in this series. Actors and Components map almost directly onto GameObjects and Components. Where the two engines really part ways is scale: Unreal ships a mature, opinionated multiplayer architecture and a first-class visual scripting language as standard equipment, not optional add-ons.
Core concept mapping #
| Unity | Unreal | Notes |
|---|---|---|
| GameObject + Component | Actor + ActorComponent | A close, direct match. |
| Prefab | Blueprint Class | A Blueprint is a reusable template and a visual-scripting canvas at once, not a pure-data template the way a Unity Prefab is. |
| Scene | Level | Different word, same idea. |
| C# scripting | C++ and/or Blueprint visual scripting | Blueprint is unusually central here. Many real, shipped Unreal games are Blueprint-only or a genuine C++/Blueprint hybrid. |
| PhysX | Chaos Physics | Unreal moved off PhysX to its own Chaos system as of UE5. Unity and O3DE still use PhysX. |
| Netcode / Mirror / FishNet (add-on) | Built-in replication | Unreal ships a mature client/server replication model as standard, where Unity requires a separate networking package. |
| No native equivalent | GameMode / GameState / PlayerController / PlayerState | See below. |
The architecture Unity developers don’t have a direct equivalent for #
Unreal ships a native GameMode / GameState / PlayerController / PlayerState cluster, with server-authority roles and replication built into the framework itself. Unity has no direct built-in equivalent; most Unity teams either hand-roll this pattern or adopt it from a networking package.
This is the same architecture Heathen’s own Game Framework modeled its Subsystem/World/GameMode/GameState/PlayerState system on for Unity and Godot, and it’s why Heathen chose not to port Game Framework to Unreal at all: Unreal already has the real thing this pattern was modeled on. If you’re coming from Unity via Game Framework, Unreal’s native tooling is the more direct, more mature version of what you were already using.
Blueprint is not “Unity’s visual scripting add-ons” #
If your only prior exposure to visual scripting was an optional Unity plugin, recalibrate: Blueprint is core Unreal tooling, used at production scale, not a beginner on-ramp. Expect a real decision early in any Unreal project about how much logic lives in C++ versus Blueprint, a decision Unity development generally doesn’t force since C# is the only serious option there.
What transfers, what you’ll need to rebuild #
Transfers well: your Actor/Component mental model (the closest match of any engine here), and if you go the C++ route, general object-oriented systems thinking. Unreal’s built-in GameMode/GameState layer does natively what you likely built by hand or with an add-on in Unity.
Needs rebuilding, not porting: any C#-specific code (full language change), and any physics tuning done against PhysX, since Chaos behaves differently enough to need real re-tuning, not just a settings tweak. Editor tooling built against Unity’s Editor API has no shortcut into Unreal’s own editor extension model either.
Heathen tooling across this migration #
- Toolkit for Steamworks: available on Unreal. No separate Foundation layer; Epic’s own Online Subsystem Steam fills that role.
- Not available on Unreal: GameplayTags, Lexicon Localisation, Ogham Storyteller, DataLens, Attribute Tag Engine (HATE), Discord Social, Game Framework.
Related guides #
- Migrating from Unity to Godot
- Migrating from Unity to O3DE
- Not sure yet? Read the Game Engine Selection Guide
- Unreal at Heathen, the full current product/tier availability list
- Foundation vs. Toolkit, what that split actually means across every Heathen product