iLead
iLeadYour hosts stay home.

Blog · 2026-10-06 · 7 min read

Import PuTTY and MobaXterm into a local vault

Step-by-step guidance for migrating PuTTY, MobaXterm, WinSCP, and ~/.ssh/config into one encrypted local vault without a cloud account.

Migrating an SSH fleet should not require a new cloud account. This guide covers how to import PuTTY and MobaXterm sessions (and related sources) into an encrypted local vault so one unlock opens the inventory you already built.

How do I import PuTTY sessions into another client?

In iLead, open the sidebar Import / Export menu and choose the PuTTY importer. Point it at your saved sessions (registry or exported files, depending on how you used PuTTY). Review the preview list, then commit into the vault. First connections still need host-key confirmation, import copies what PuTTY knew; it does not skip SSH trust on the wire.

Can I migrate MobaXterm sessions safely?

Yes. Import MobaXterm sessions the same way, then spot-check a few production hosts before deleting the old store. If Moba stored passwords, treat the migration window as a chance to rotate anything that lived in a weaker container. Keep a backup of the Moba config until you have connected successfully from the vault.

What happens to passwords when I import SSH sessions?

Imported secrets land inside the Argon2id-sealed vault file, not in a new plaintext folder. They are not uploaded to ileadapp.org. After import, prefer key-based auth where you can, mask-reveal stays password-gated in the host editor, and avoid leaving old session exports on USB drives.

How do I move an SSH fleet without a cloud sync account?

Import on machine A, enable sync to a folder you already use, unlock machine B against the same folder, and let the merge settle. Alternatively export a sealed backup and restore on the second device. Either path keeps the vendor out of the host list. Related: what local-first means.

Sources iLead can pull in today

  • PuTTY, MobaXterm, WinSCP, SecureCRT
  • Termius, Tabby, NeoServer, Remmina, Bitvise, Royal TS, WindTerm
  • ~/.ssh/config, CSV, JSON, Ansible YAML/INI

That is 15+ import / migration paths, enough to leave a pile of legacy tools without retyping every hostname. Full capability list: features.

Prefer a product walkthrough? See the feature list, the client comparison, or download iLead.

Questions this article answers

  • How do I import PuTTY sessions into another client?Use the client’s PuTTY importer, review the preview list, commit into the vault, then confirm host keys on first connect. Import copies session data; it does not skip SSH trust on the wire.
  • Can I migrate MobaXterm sessions safely?Yes. Import MobaXterm sessions, spot-check production hosts, rotate passwords that lived in weaker stores, and keep a backup of the old config until connects succeed from the vault.
  • What happens to passwords when I import SSH sessions?Imported secrets should land inside the encrypted vault file on disk and must not be uploaded to the vendor’s website. Prefer moving to key-based auth after migration when you can.
  • How do I move an SSH fleet without a cloud sync account?Import on one machine, sync the vault through a folder you already use, or restore a sealed backup on the second device. No product account is required for the host list itself.

Related reading

← All blog posts