Export connections for SecureCRT

Your connection list, as a CSV that SecureCRT can import. Useful when a colleague uses SecureCRT, when a customer wants the session list for their own tooling, or when you keep both installed and would rather not type the estate in twice.

What is in the file

A CSV for SecureCRT 9.2 and later, with the columns its text importer expects:

• Session Name
• Folder
• Hostname / IP Address
• Port
• Protocol
• Username
• Emulation

Your folders come across as SecureCRT folder paths, so an estate organised by site or by customer arrives organised the same way rather than as one flat list.

Importing it

In SecureCRT: Tools → Import Settings from Text File, and point it at the CSV. A README with these steps is written beside the file, because the menu item is not where most people would look for it.

No credentials, by design

No passwords, no passphrases, no private keys, and no references to the vault entries that hold them. Authentication has to be set up again on the SecureCRT side.

Usernames are off by default and are a deliberate choice at export time. A connection list is a fairly harmless thing to email; a connection list annotated with the account used on each device is a different sort of document.

Serial connections are reported, not exported

SecureCRT's text importer has no columns for baud rate, parity, data bits or flow control. A serial session written through it would arrive carrying the port name and silently wrong line settings — which is worse than not arriving, because it looks like it worked.

So they are listed for you at the end of the export instead, and you set them up by hand on the other side. There are usually few enough of them for that to be the right trade.

Going the other way

There is no SecureCRT importer. If you are arriving from PuTTY rather than leaving for SecureCRT, see importing PuTTY sessions.