GODOT 4.7 / MIGRATION

Migrate to Godot

Bring your Unity or Unreal experience to Godot 4.7 — the practical path, not a vocabulary dump.

Unity→Godot

Move from Unity

Translate GameObjects, Prefabs, MonoBehaviours, and C# habits into Godot's scene-first workflow.

  • GameObject → Node
  • Prefab → PackedScene
  • ScriptableObject → Resource
Start path Unreal→Godot

Move from Unreal

Map Actors, Components, Blueprints, UMG, and Data Assets into focused Godot systems.

  • Actor → Node
  • Blueprint → Scene + script
  • Event Dispatcher → signal
Start path
Reference

Look up any equivalent

Type a Unity or Unreal concept and get its Godot 4.7 equivalent with side-by-side code, verified against the engine documentation.

Open the Equivalents Dictionary
Decide first

Not sure yet?

Compare Godot, Unity, and Unreal side by side before you commit a project to a move.

Compare engines

Migration guides

Practice tools

Equivalents Dictionary

Look up the Godot version of any Unity or Unreal concept.

Terminology Game

Drill Unity/Unreal → Godot terms.

Code Lab

Side-by-side C#/C++ → GDScript translations.

Frequently asked questions about migrating to Godot

Should I port my existing project or rebuild it in Godot?
For most projects, rebuild the gameplay in a vertical slice first and port only assets. Godot's scene model and signals differ enough from Unity/Unreal that a mechanical port usually costs more than a focused rebuild of the core loop.
How long does migrating from Unity or Unreal to Godot take?
A 2D prototype's core systems transfer in days; a production project is typically weeks, with an extra 1-2 months for 3D-heavy work. Concepts transfer faster than you expect because your game-development instincts still apply.
Do I have to learn GDScript, or can I keep C#?
Godot supports C# via .NET, so Unity developers can keep C#. GDScript is recommended for gameplay glue because of instant iteration, but C# remains available for teams that prefer it.