How Migration Works
Desktop Legacy was a single-install desktop app. Comfy Desktop is a multi-installation manager. When you migrate:- A new Standalone installation is created — with its own Python environment and ComfyUI version
- Your custom nodes are copied — to the new installation
- Your models are linked (not copied) — they stay where they are
- Your workflows and settings are carried over — so you can pick up right where you left off
Step-by-Step Migration
Step 1 — Install Comfy Desktop
Download and install Comfy Desktop from the official download page.Step 2 — Start Comfy Desktop
When you first open Comfy Desktop after installing, it will automatically detect any Desktop Legacy installation on your system. You’ll see a migration banner or be prompted to migrate.Step 3 — Choose “Migrate Now”
Click Migrate Now to start the migration process. Comfy Desktop will:- Detect your Desktop Legacy installation
- Create a new Standalone installation
- Copy custom nodes, workflows, and settings
- Link your model directories
Step 4 — Verify
Launch your new installation to confirm everything works:- All your workflows should be available
- Custom nodes should be installed
- Models should be accessible
Post-Migration
After migrating successfully, you can continue using your new Standalone installation. Your Desktop Legacy installation remains untouched as a backup.What Gets Carried Over
| Item | Carried Over? | How |
|---|---|---|
| Workflows | ✅ | Copied to the new installation |
| Custom Nodes | ✅ | Re-installed in the new environment |
| Models | ✅ | Linked via shared directories (not copied) |
| Settings | ✅ | Desktop Legacy settings are carried over |
| Python Environment | 🆕 | Fresh environment with bundled Python |
| ComfyUI Version | 🆕 | Latest version installed |
Troubleshooting
Desktop Legacy not detected automatically
If Comfy Desktop doesn’t detect your Desktop Legacy installation, you can manually add it:- In the Chooser view, click the + card
- Select Legacy Desktop as the source type
- Comfy Desktop will search for any existing Desktop Legacy installations
- Follow the migration prompts
Migration fails
If the migration process encounters an error:- Check the logs at the platform-specific log directory for details
- Ensure your Desktop Legacy installation is intact — the migration process reads from your existing install
- Try again — if the issue was a network timeout or temporary error, a second attempt may succeed
After migration, models are missing
Models are linked (not copied) during migration. If models don’t appear in the new installation:- Open the Manage panel for the migrated installation
- Go to Settings → Model directories
- Verify that your old model directory is listed
- If not, add it manually