You can import server information from WinSCP to MobaXterm by exporting your sessions as an INI file and then using the MobaXterm session manager to load that configuration. This process allows you to leverage existing connection details without manually re-entering hostnames, usernames, or port settings. By converting the WinSCP format into a compatible structure, you ensure a seamless transition between these popular SSH clients on Windows.
Understanding the Format Differences
WinSCP stores its session data in a registry-based format or as an INI file when exported via the GUI. MobaXterm, while supporting PuTTY-style configurations natively, uses its own internal database for sessions stored in
MobaXterm.ini. Directly opening a WinSCP INI file in MobaXterm will not work because the key names and structure differ significantly. Therefore, a conversion step is required. The most reliable method involves exporting sessions from WinSCP and then manually mapping those values to MobaXterm’s session editor or using a script if you have many connections.
Exporting Sessions from WinSCP
First, open WinSCP and navigate to the
Sessions tab. You need to select the specific servers you wish to migrate. Click on
Advanced to view detailed settings, but for basic imports, the standard export function suffices. Go to the
Session menu at the top of the window and select
Save All Sessions.... Choose a location on your hard drive and save the file with an
.ini extension, such as
winscp_sessions.ini. This file contains all your saved credentials and host addresses in a plaintext format that you can edit.
MobaXterm and WinSCP Disconnect from My Connection Due to Sudden Inactivity highlights how both tools manage persistent connections, which is relevant when migrating keep-alive settings.
Converting the Configuration
Open the exported
winscp_sessions.ini file in a text editor like Notepad++. You will see sections named after your sessions, containing keys like
HostName,
UserName, and
PortNumber. MobaXterm does not read this format directly, so you must create new sessions within MobaXterm instead. Open MobaXterm and click on the
Session button in the toolbar. Select
SSH as the protocol.
In the new session dialog, manually enter the hostname, username, and port from your INI file. If you use key-based authentication, ensure you point the private key field to the correct
.ppk or
.pem file. WinSCP often uses
.ppk files generated by PuTTYgen, which MobaXterm supports natively. Once filled out, give the session a name matching the original WinSCP entry for easy identification. Repeat this for each server listed in your INI file.
Automating with Scripts (Optional)
If you have dozens of servers, manual entry is tedious. You can write a simple PowerShell script to parse the WinSCP INI file and generate MobaXterm commands. However, since MobaXterm’s session storage is proprietary, true automation usually requires importing PuTTY sessions instead. WinSCP can also export to PuTTY
.reg files. You can import these registry entries into Windows, and then use MobaXterm’s built-in "Import PuTTY sessions" feature found in
Settings >
Configuration >
Putty sessions. This bridges the gap more effectively than direct INI parsing.
WinSCP Connection through Wallix Bastion Failure but not with PuTTY demonstrates why ensuring protocol compatibility during migration is crucial for bastion host access.
Verifying and Troubleshooting
After creating your sessions, test each one by clicking
Connect. Pay attention to encryption algorithms; WinSCP and MobaXterm may default to different ciphers. If a connection fails, check the
Advanced SSH Settings in MobaXterm to match the algorithm used in WinSCP. Also, verify that proxy settings are correctly transferred if your network requires a jump host. Ensure that terminal types (e.g.,
xterm-256color) are consistent to avoid display issues.
Frequently Asked Questions
Can I directly open a WinSCP .ini file in MobaXterm?
No, MobaXterm cannot read WinSCP’s INI format directly due to structural differences. You must either manually recreate sessions or convert the data via PuTTY registry exports first.
Does MobaXterm support PuTTY .ppk files?
Yes, MobaXterm fully supports PuTTY’s private key format (
.ppk). When setting up an SSH session, simply browse to your
.ppk file in the private key field under advanced options.
How do I migrate proxy settings from WinSCP to MobaXterm?
Proxy settings are not automatically transferred. You must manually configure the SOCKS or HTTP proxy in MobaXterm’s session properties under the
Proxy tab, matching the details from your WinSCP advanced session settings.
Is there a risk of losing password encryption during migration?
No, because you are typically re-entering credentials or pointing to existing key files. Passwords are not stored in plain text in either tool’s session file, so no sensitive data is exposed during the manual recreation process.
Why do some sessions fail after importing via PuTTY registry?
Failures often occur due to mismatched encryption algorithms or missing host keys. Check the
Advanced SSH Settings in MobaXterm to ensure the cipher suite matches what the server expects, similar to how you configured it in WinSCP.