Import guide

Import from the client you already have

Fourteen formats: twelve clients, ssh_config and known_hosts. Bring your saved connections across, then check what each source can carry. Royal TS/TSX documents cannot be imported.

Start in Termiyo

Unlock your vault. Above the host list, open the cloud button named “Import hosts from somewhere else”, or use “Import” on the launch screen. Follow the menu path under your source below.
For host imports, check the preview and tick the hosts you want, including any jump hosts they need. Expand “Not imported” beside its count to read the omissions. “Choose a different file” keeps the same source format.
Press “Import” with the selected count, review the result, then “Done”. Hosts marked “already imported” start unchecked. Selecting them again can update existing personal-vault hosts; importing an unchanged file does not create duplicates.
The known_hosts route is different: selecting the file saves its supported host-key pins immediately, without a host preview. It creates no hosts.

Termius

File and location: JSON or CSV written by a community exporter, such as termius-local-export or termius-exporter: hosts.json, credentials.json, decrypted-indexeddb.json, credentials.csv or termius_hosts.csv. Keep exported key files available too. Termiyo does not read the encrypted Termius store directly.
What comes across: Hosts, ports, usernames, available saved passwords and supported inline or referenced keys. Group paths become labels. The raw decrypted entity export can also carry inherited group settings, resolved jump hosts and local, remote or dynamic forwards.
What stays behind: Group folders, tags, snippets, terminal appearance and key passphrases. An export without secrets cannot supply passwords or keys that it omitted. Do not expect the flat CSV or host list to contain the raw export’s forwarding rules.
Open it in Termiyo: Import → “Termius” → choose the community exporter’s JSON or CSV. Then review the host preview.

JuiceSSH

File and location: On the phone, open JuiceSSH → Backup / Restore and create an unencrypted backup. Copy its JSON backup (.json, .jsbk or .txt) to this computer.
What comes across: SSH connections, ports and usernames from referenced identities, their saved passwords and readable private keys. Group names become labels. Mosh entries become SSH connections.
What stays behind: Encrypted backups are refused. Telnet and local sessions, port-forward collections, snippets, saved host keys, app settings and key passphrases are not imported.
Open it in Termiyo: Import → “JuiceSSH” → choose the unencrypted backup. Then review the host preview.

PuTTY

File and location: The Windows key HKCU\Software\SimonTatham\PuTTY\Sessions is read automatically from “PuTTY sessions”. A .reg export of that key also works. On Linux or macOS, use ~/.putty/sessions or a single session file.
What comes across: SSH session names, addresses, ports, usernames and referenced supported keys. Local, remote and dynamic forwards, plus a recognised plink -nc jump through a saved session.
What stays behind: Non-SSH sessions, Default Settings, saved proxy passwords, ordinary SOCKS/HTTP proxies, appearance and remote commands. PuTTY .ppk keys require the separate key import described below; they are not converted here.
Open it in Termiyo: Import → “PuTTY sessions”. Termiyo looks for local sessions, including the Windows registry; if none are found it opens a file chooser. Use “Choose a different file” for your own export.

FileZilla

File and location: sitemanager.xml: %APPDATA%/FileZilla on Windows; ~/.config/filezilla on Linux and macOS, also ~/Library/Application Support/FileZilla on macOS.
What comes across: SFTP sites with names, addresses, ports, usernames and referenced keys. Saved passwords in plain text or base64 come across when the site uses normal saved-password login.
What stays behind: FTP, FTPS, WebDAV and other non-SFTP sites; the folder hierarchy. Master-password-protected passwords cannot be decoded. “Ask” or interactive logins have no saved password to transfer.
Open it in Termiyo: Import → “Look on this computer” → the FileZilla result. Then follow the host preview steps above.

WinSCP

File and location: WinSCP.ini with [Sessions\…] sections. The scan checks %APPDATA%/WinSCP.ini on Windows; a registry-only configuration needs an INI export from WinSCP first.
What comes across: SCP and SFTP sessions, names, addresses, ports, usernames, referenced keys and decodable saved passwords. A session path stays in its label.
What stays behind: FTP, WebDAV and S3 sessions. Passwords protected by a WinSCP master password do not come across. Proxy, forwarding and interface settings are not mapped.
Open it in Termiyo: Import → “Look on this computer” → the WinSCP result. Then follow the host preview steps above.

MobaXterm

File and location: MobaXterm.ini on Windows, under %APPDATA%/MobaXterm or Documents/MobaXterm.
What comes across: SSH bookmarks: name, address, port and username. SubRep folder names are folded into the label.
What stays behind: Other session types, private keys, forwards and display settings. Passwords in MobaXterm’s separate protected store (DPAPI/master password) are not read; enter them when connecting.
Open it in Termiyo: Import → “Look on this computer” → the MobaXterm result. Then follow the host preview steps above.

JetBrains IDEs

File and location: options/sshConfigs.xml inside each product folder under %APPDATA%/JetBrains on Windows, ~/Library/Application Support/JetBrains on macOS or ~/.config/JetBrains on Linux.
What comes across: SSH configuration names, hosts, ports, usernames and referenced keys. The $USER_HOME$ macro in a key path is expanded.
What stays behind: Passwords in the IDE’s password safe or OS keychain, IDE settings and project configuration. No group folders are created.
Open it in Termiyo: Import → “Look on this computer” → the JetBrains IDEs result. Then follow the host preview steps above.

Remmina

File and location: The .remmina files in ~/.local/share/remmina on Linux. Password decoding also needs the secret in ~/.config/remmina/remmina.pref or ~/.remmina/remmina.pref on this computer.
What comes across: SSH/SFTP hosts, ports, usernames, referenced keys and passwords decodable with that secret. Group names become part of the label.
What stays behind: RDP, VNC and other non-SSH profiles, commands, appearance, proxies and tunnels. Without the matching remmina.pref secret, protected passwords stay behind.
Open it in Termiyo: Import → “Look on this computer” → the Remmina result. Then follow the host preview steps above.

Tabby

File and location: config.yaml under %APPDATA%/tabby on Windows, ~/Library/Application Support/tabby on macOS or ~/.config/tabby on Linux.
What comes across: SSH profiles, names, hosts, ports, usernames and referenced private keys. Group names become part of the label.
What stays behind: Passwords, proxy commands, jump-host settings and non-SSH profiles. Group folders and terminal appearance are not recreated.
Open it in Termiyo: Import → “Look on this computer” → the Tabby result. Then follow the host preview steps above.

SecureCRT

File and location: Session .ini files in %APPDATA%/VanDyke/Config/Sessions on Windows, ~/Library/Application Support/VanDyke/SecureCRT/Config/Sessions on macOS or ~/.vandyke/SecureCRT/Config/Sessions on Linux.
What comes across: SSH sessions named after their files, with addresses, ports, usernames and referenced keys. The directory reader reads .ini files directly inside the selected folder.
What stays behind: Nested session folders, Default.ini in a directory import, non-SSH sessions, passphrase-protected saved passwords, scripts, proxies, forwards and appearance. Import a nested session file separately.
Open it in Termiyo: Import → “Look on this computer” → the SecureCRT result. Then follow the host preview steps above.

Cyberduck

File and location: XML .duck bookmarks under %APPDATA%/Cyberduck/Bookmarks on Windows or ~/Library/Group Containers/G69SCX94XU.duck/Library/Application Support/duck/Bookmarks on macOS.
What comes across: SFTP/SSH bookmarks, nicknames, hosts, ports, usernames and referenced private keys.
What stays behind: Keychain passwords, other protocols and the bookmark’s starting folder. Binary plists need an XML copy first; no bookmark groups are recreated.
Open it in Termiyo: Import → “Look on this computer” → the Cyberduck result. Then follow the host preview steps above.

iTerm2

File and location: ~/Library/Preferences/com.googlecode.iterm2.plist on macOS, in XML form. Convert a binary plist copy before choosing it.
What comes across: Profiles whose enabled custom command runs ssh: profile name, destination, username, -p port, -l user and -i key path.
What stays behind: Local-shell profiles, passwords, colours and groups. Other SSH options, including -J, forwards and remote commands, are reported rather than imported.
Open it in Termiyo: Import → “Look on this computer” → the iTerm2 result. Then follow the host preview steps above.

ssh_config

File and location: ~/.ssh/config or another OpenSSH configuration file, plus readable Include files and referenced keys.
What comes across: Concrete Host aliases, resolved hostname, port and user, supported keys, resolvable ProxyJump chains, recognised ssh -W proxies and local, remote or dynamic forwards. Matching known_hosts entries can supply pins, including hashed entries for these known destinations.
What stays behind: A wildcard block supplies defaults but does not create hosts. No passwords or group folders. Match exec and arbitrary ProxyCommand commands are never run; unsupported directives, algorithm lists and StrictHostKeyChecking overrides are reported.
Open it in Termiyo: Import → “SSH config” reads ~/.ssh/config. Use “Choose a different file” for another config, then review the host preview.

known_hosts

File and location: ~/.ssh/known_hosts, or another OpenSSH known_hosts file selected in Settings.
What comes across: Trusted server public-key pins for literal hostnames and ports, with one preferred key per host and port. Existing pins are kept unchanged.
What stays behind: No hosts, usernames, groups, private keys or passwords are created. Standalone import skips hashed and wildcard-only entries, revoked keys, certificate-authority markers and DSA keys.
Open it in Termiyo: Import → “Look on this computer” → “Known hosts” imports the detected file immediately. For another file, use Settings → Known hosts → “Import a known_hosts file”.

Keys, groups and missing sources

A key path is not a copy of the key. Referenced private-key files must be readable at their named paths on this computer. Supported OpenSSH and PEM keys can come across; passphrases are not copied. Missing or unsupported keys are reported in the preview. Imported credentials are stored encrypted in the vault.

Groups are not recreated as folders. Where supported below, their names become part of the host label. For clients reached through “Look on this computer”, check the listed locations if no source appears. Once its preview opens, “Choose a different file” can select another file of that format.

PuTTY .ppk files need the separate Settings → SSH keys → “Import from a file…” flow, then an identity using the imported key. The host importer does not convert them. If Cyberduck or iTerm2 reports a binary plist, convert a copy to XML with plutil -convert xml1 -o converted.plist input.plist on macOS, then select the XML copy; keep .duck as the extension for a Cyberduck copy.