9. Coming from Swifty

Nimby imports an existing Swifty installation instead of asking you to retype it: close the old client, preview, then apply.

nimby migrate --dry-run
nimby migrate

It reads %APPDATA%\Swifty\Settings.json and imports the Arma 3 path (only if it still holds an Arma executable), the scratch folder, the parallel download count, every repository with URL, name and stored credentials, the workspace root taken from the first repository's path, and that repository's launch parameters.

It does not delete, move or modify anything in the old client, and its repositories stay where they are. Use --source "<path>\Settings.json" if the file lives elsewhere. After importing, open Repositories and press Use this repo on your community — the active repository is what Install and Launch act on.

Old installs at the root. Swifty put mods directly in its install folder while Nimby uses a subfolder per repository. nimby migrate --layout moves the @mod folders (and .nimby metadata) into the active repository's subfolder. It only renames entries, so hardlinks and junctions survive and no byte is copied; existing names are skipped.

nimby migrate --layout --dry-run
nimby migrate --layout