To open Import session dialog go to Tools > Import Sites on Login dialog.
On the dialog, select if you want to import from PuTTY, FileZilla, OpenSSH
You will receive list of all sites/host keys stored in the selected application or configuration file. Next to each site name there is a checkbox. Use it to select sites/keys you would like to import. By default WinSCP selects only sites with supported protocol,1 for which there is no WinSCP site with the same name. You can alter the selection as you like.
For PuTTY, WinSCP looks for sites in registry.
If you use PuTTY clone, such as KiTTY, you can configure WinSCP to look for its registry keys instead.
For FileZilla, WinSCP looks for sites in
config file, WinSCP looks to
C:\Users\username\.ssh\config. In the file, it looks for all
Host directives with specific hostname and imports them as sites to WinSCP.
When resolving site settings, it considers all
Host directives, even those with wildcards. The following directives are recognized:
ProxyJump (single jump only) and
When private key is found in the
IdentityFile directive, WinSCP will offer you to convert the key to PuTTY format, unless a key file with the same name and
.ppk extension exists already.
known_hosts files, WinSCP looks to
C:\Users\username\.ssh\known_hosts. You can also paste hosts key in OpenSSH format from clipboard using Paste button.
WinSCP imports also SSH host keys from the source application cache for hostnames from all selected sites. So you do not need to verify again the SSH host keys that you have verified in the other application already.
When you finish your selection, press OK to import the sites. Note that when the name of imported site collides with name of an existing site, WinSCP appends number to the end of the name to name it unique.
For session options that the source application does not have, WinSCP will use the defaults.
- It does not select Raw, Telnet, Rlogin and Serial sessions from PuTTY.Back