Guides · Migrate
Migrate from another emulator
Some Citron NEO builds detect an existing Switch emulator profile and offer to import settings. When in doubt, start clean — especially if the old install came from an unofficial bundle.
Do not import bundled keys
Never copy prod.keys, title.keys, or firmware that arrived with a third-party installer or download page. Use only keys and firmware dumped from hardware you own. See Security.
When the first-run wizard offers import
- Import — if you trust the old profile (your own keys, same machine, known-good paths).
- Clean / new folder — if the old emulator was broken, from an unknown source, or mixed with another fork.
- You can often re-trigger import from an in-app menu on supported builds — check the readme.
Manual clean start (recommended)
- Extract Citron NEO to a new folder from official GitHub Assets.
- Add an empty
userfolder next to the binary (setup). - Copy your legally obtained keys into
user/systemand install firmware through the app — do not reuse keys from random packs. - Point Game directories at the same game folders you already use (content you are entitled to).
- Shader caches and per-game configs may not transfer — expect to rebuild cache on first launch.
From Yuzu, Eden, Sudachi, or old Citron
Folder names and config formats differ between forks. A direct copy of an entire old user tree into Citron NEO sometimes works but often causes missing keys or crash-on-start. Prefer wizard import when offered, otherwise clean setup with the same keys and game paths re-applied manually.
Old download sites and domains may be dead or impersonated — verify you are on github.com/citron-neo only. About Citron NEO.
After migration
Pick one game to smoke-test before moving your whole library. Crashes → Troubleshoot. Per-game status changes every release → Compatibility.