Import & Export

Conduit can import connections from other remote connection managers and export your vault data as encrypted portable files, preserving your folder structure, credentials, and entry metadata.

Conduit Export (.conduit-export)

Export your vault to an encrypted .conduit-export file for backup, migration, or sharing. Files are encrypted with a passphrase you provide using PBKDF2-SHA256 (600,000 iterations) and AES-256-GCM.

Exporting

1. From the vault switcher menu, select Export to Conduit Export, or right-click a folder and choose Export Folder.
2. Enter and confirm a passphrase to encrypt the file.
3. Choose a save location. The file contains all entries, folders, and credentials from the selected scope.

Importing

1. Go to File > Import > From Conduit Export or use the vault switcher menu.
2. Select the .conduit-export file and enter the passphrase.
3. Preview the contents — see the source vault name, folder tree, and entry type counts before committing.
4. Choose to import into the vault root or a specific target folder, then confirm.

Supported Import Sources

In addition to Conduit export files, Conduit supports importing from Devolutions Remote Desktop Manager via .rdm XML export files.

Exporting from Remote Desktop Manager

Before importing into Conduit, you need to export your connections from Devolutions RDM:

1. In Remote Desktop Manager, right-click the folder (or vault root) you want to export.
2. Select Export > Export Vault (.rdm) and choose the V2 format.
3. Important: Ensure that no encryption is set on the export file (do not set a shared passphrase).
4. Check the Include credentials option so that usernames and passwords are included in the export.
5. Save the .rdm file to a location you can access from Conduit.

Importing into Conduit

1. In Conduit, go to File > Import > From Remote Desktop Manager.
2. Select the .rdm file you exported.
3. Preview the import: entries are grouped by folder with status badges indicating each entry's state — ready, decrypt-failed, unsupported, or duplicate.
4. If duplicates are detected (entries matching an existing vault entry by name, type, and host), you are prompted to choose a strategy: Overwrite All to update existing entries, or Skip All to leave them unchanged.
5. Confirm to import.

Supported Types

The following entry types are imported from RDM files:

Connections

• SSH — terminal connections with host, port, and credential mapping
• RDP — remote desktop sessions with display and authentication settings
• VNC — including Apple Remote Desktop (AppleRemoteDesktop) entries
• Web — browser-based sessions with URL and autofill configuration

Organization

• Group — folder structures and group-level credentials are extracted and recreated

Credentials

• PasswordList — flattened into individual credential entries (one per list item, with prefixed names)
• ApiKey — imported as standalone credential entries
• Simple credentials — username/password pairs imported directly

Documents

• DataEntry / SecureNote — decrypted and imported as markdown document entries in Conduit
• Document — reads the referenced local file content when the file exists on disk; the content is stored as a document entry

Duplicate Detection

When re-importing an RDM file into a vault that already contains some of the same entries, Conduit detects duplicates by matching on name, type, and host. Duplicates are flagged with a duplicate badge during the preview step.

Before the import executes, you are prompted to choose a strategy:

• Overwrite All — update existing entries with the data from the import file.
• Skip All — leave existing entries unchanged and only import new ones.

Automatic Decryption

Credentials stored in RDM export files are automatically decrypted using built-in per-type keys. No passphrase is needed — just select the file and Conduit handles the rest. This includes encrypted secure notes and data entries, which are decrypted and converted to markdown documents.

Folder Structure

Folder hierarchies from RDM are recreated in Conduit. Your organizational structure carries over exactly as it was.

Credential Resolution

CredentialConnectionID references in the RDM file are resolved automatically, linking credentials to their connection entries so authentication works immediately after import. PasswordList entries are flattened into individual credentials with prefixed names for easy identification.

Tier Limits

Import respects your tier's connection limit. If importing would exceed the limit, a partial import occurs. After completion, you receive a summary showing imported, skipped, overwritten, and error counts.

Export Log

After import, you can export an import log (.log file) with full details of what was imported, skipped, overwritten, or failed.