Projects
Import a Unity project
Import from Unity makes a new Godot 4 project from a Unity project, without opening or installing Unity. Scenes, prefabs, models, sprites, tilemaps and settings convert on import; the Port report lists what is left, and the AI ports it with you.
Import the project
The new project goes where your new games go, named after the Unity project with "(Godot)" after it. The Unity project is only read: nothing in its folder is changed, and Unity does not need to be installed.
Flockbay reads the scenes in the Build Settings and everything they reference, the Resources and StreamingAssets folders, and every script. A folder you open with Open project… that turns out to be a Unity project gets the same import from its card.
- On Home, open the ▾ beside Open project… and choose Import from Unity….
- Pick a project from Unity Hub projects, or choose Choose folder… and pick the folder that holds Assets and ProjectSettings.
- Flockbay reads the project under "Importing <folder>…". Cancel stops it and removes what it wrote.
- The new Godot project opens in the editor with the chat docked and the Port report card above the composer.
Unity saves scenes and prefabs as text by default (Asset Serialization: Force Text). A project saved in binary still imports, more slowly.
What converts on import
The import is built on the open-source Unidot Importer (MIT), running inside the Godot editor that comes with Flockbay. Unity's axes are right-handed in Godot, so X is mirrored on the way in.
| Unity | Godot |
|---|---|
| Scene (.unity) | Scene (.tscn) |
| Prefab, with its overrides in each scene | Scene (.prefab.tscn), instanced |
| FBX and glTF models, rigs and animations | Imported with Godot's own FBX and glTF import |
| Standard and URP Lit materials | StandardMaterial3D with the same colours and texture maps |
| Camera, AudioSource | Camera3D, AudioStreamPlayer and AudioStreamPlayer3D |
| Animator Controller and AnimationClip | AnimationTree and AnimationPlayer |
| SpriteRenderer, sorting layers and order | Sprite2D, z_index |
| Tilemap and its tiles | TileMapLayer with a TileSet |
| Rigidbody2D and 2D colliders, triggers | RigidBody2D, CharacterBody2D or StaticBody2D, CollisionShape2D, Area2D |
| Orthographic camera | Camera2D with the same framing |
| Physics layers, gravity, fixed timestep, window | Project Settings |
| Input Manager axes and .inputactions | Input Map actions |
What the AI ports
A component the import does not convert stays in the scene as a placeholder node named after its Unity class, with every Inspector value kept on it. A MonoBehaviour keeps its fields and the script it used; references keep the object they pointed at. The AI reads them with the ordinary scene tools, so a port starts from the values you set in Unity, not from defaults.
Scripts are ported to GDScript, or to C# if you ask, on Windows and Linux. Unity's API is not Godot's, so each MonoBehaviour is rewritten as a script on the node it belongs to: Start becomes _ready, Update _process, a coroutine await, a UnityEvent a signal. uGUI canvases become Control nodes, particle systems GPUParticles2D or GPUParticles3D, and custom shaders are rewritten in Godot's shading language.
Unity's own packages (TextMeshPro, the render pipelines, Cinemachine, the Input System) are not copied into the project: their licence does not allow it. The AI rebuilds what the game used from them with Godot nodes, and the Port report lists each package.
The Port report
The card above the composer has three columns, Converted, Approximated and To port, each split by kind: scenes, prefabs, scripts, UI, particles, settings. Approximated is a conversion that is close but not exact, such as a mouse axis that Godot reads from mouse motion events instead.
Finish port sends "Port the rest of this Unity project." to the chat. The AI works through the list in order, the input and camera first, then the main scene and what it uses, and marks each item ported or skipped with a reason. After the first turn the card reads "12 of 41 left" and the button becomes Continue port. Not now folds the card to one line.
Open report opens PORT_REPORT.md, the same list as a file, with every approximation and skip and the reason for it. .flockbay/unity-port.json is the list the AI works from.
When the port is finished
With nothing left, the card reads Port finished. The port is not compared with the original game: play it and check it against the Unity build, and say in the chat what feels different.
The import keeps a copy of the Unity sources in unity-source/, with C# saved as .cs.txt and a .gdignore so Godot never imports it. Delete Unity sources removes that folder and the import's asset database. Your Godot project is not affected.
Bring in a .unitypackage
The chat's + menu has Import Unity package…. It opens your Asset Store downloads folder; pick a .unitypackage and its assets are imported into the open game the same way, at their own Assets/ paths, with their scripts added to the Port report and the game's settings left as they are. Each package keeps its own licence: check it before you ship the game.
Your own agent
Claude Code, Codex or Cursor connected over MCP gets the same port tool, flockbay_unity_port: status, next, mark and language, and the same working order in the unity_port guide. Connect your own agent sets it up.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
