Fryguy's Blog
Home About Fryguy JNCIE-ENT Workbook Published Workbooks Cisco Live Hats Network Tools Financial Tools RSVLTS Search
Fryguy's Blog

SecureCRT to SuperPutty Session Converter

Legacy terminal client to modern session manager migration diagram
← Back to Tools

Drop in a SecureCRT session XML export and get back a ready-to-import SuperPutty Sessions.xml — instantly, in your browser. This is the same logic as the SCRT_2_SPUTTY.py script, ported to JavaScript so you don't need Python installed. Nothing is uploaded anywhere; the file never leaves your browser tab. Folder hierarchy is flattened into path-prefixed names, protocols are mapped to their closest SuperPutty equivalent, and anything that can't be converted (Serial, Local Shell, template stubs) is skipped and listed so you know exactly what didn't make the trip.

Ready
SecureCRT XML Export 0 bytes
SuperPutty Sessions.xml 0 sessions
Converted XML will appear here…
Import into SuperPutty via File → Import Sessions → From XML File… and point it at the downloaded file. Passwords are never stored in the SecureCRT XML export, so there's nothing to carry over — you'll re-enter credentials (or rely on key auth) in SuperPutty as usual.
Examples (click to load)
SSH2→ SSH
SSH1→ SSH
Telnet→ Telnet
TelnetSSL→ Telnet (no native TLS-Telnet in SuperPutty)
RDP→ RDP
SFTP→ SSH (SuperPutty has no dedicated SFTP session type)
Serial→ skipped, no SuperPutty equivalent
Local Shell→ skipped, no equivalent
TAPI / Raw→ skipped, no equivalent
  1. Open SecureCRT
  2. Go to Tools → Export Settings…
  3. Select Sessions and choose XML as the format
  4. Save the file (e.g. SecureCRT_Sessions.xml)
  5. Drop that file into the box above, or paste its contents directly
  1. Click Convert, then Download above
  2. Open SuperPutty
  3. Go to File → Import Sessions → From XML File…
  4. Select the downloaded file
  5. Your sessions will appear in the session list, grouped by their original SecureCRT folder path

Provided as-is, with no warranty of any kind. This conversion runs entirely in your browser and is not an officially supported migration path for either product — field mappings, protocol defaults, and folder-flattening behavior may not match every SecureCRT export variant. Passwords and other credentials are never carried over. Always review the converted sessions in SuperPutty before relying on them, and keep your original SecureCRT export as a backup. See the full disclaimer.