Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Termix-SSH/Termix/llms.txt

Use this file to discover all available pages before exploring further.

Termix lets you export your data to a JSON file and import it back into any Termix instance. This is useful for migrating between servers, creating backups of your SSH configuration, or transferring your setup to a new account. The export covers your SSH hosts, saved credentials, and file manager state.
Exported files contain your SSH credentials, including passwords and private keys. Treat the export file like a password — store it somewhere secure and do not share it.

What gets exported

Each export file is a structured JSON document containing all of the following data for your account:
CategoryWhat’s included
SSH hostsAll saved SSH, RDP, VNC, and Telnet host configurations, including connection details and per-host settings
SSH credentialsNamed credential sets (passwords, private keys, key passwords) saved in your credential manager
File manager — recent filesRecently accessed files on remote servers
File manager — pinned filesFiles you have pinned for quick access
File manager — shortcutsCustom shortcuts saved in the file manager
The export format is always JSON (v2.0), with a metadata block that records the export timestamp, your username, and the total number of records.

Export your data

1

Open Settings

Click your avatar or username in the top navigation, then select Settings.
2

Navigate to Export Data

Find the Export Data option in the settings panel.
3

Download the file

Termix generates and downloads a .json file containing all of your data. Save this file in a secure location.
If you are an administrator, you can also export all users’ data from the admin panel. Each user’s data is exported as a separate bundle within the same file.

Import your data

Importing merges the data from an export file into your account. Existing records with the same host (matching IP, port, and username) or credential name are skipped by default — they are not overwritten unless you explicitly choose to replace existing entries.
1

Open Settings

Click your avatar or username in the top navigation, then select Settings.
2

Navigate to Import Data

Find the Import Data option in the settings panel.
3

Select your export file

Choose the .json file you previously exported from Termix.
4

Confirm the import

Termix shows a summary of what will be imported. Confirm to complete the operation.

Import behaviour

Termix checks for existing records before inserting each item:
  • SSH hosts: Duplicates are detected by matching IP address, port, and username. If a matching host exists, the incoming record is skipped.
  • SSH credentials: Duplicates are detected by credential name. If a credential with the same name exists, the incoming record is skipped.
  • File manager data: Recent files, pinned files, and shortcuts are always inserted as new entries.
You can import data exported from one Termix account into a different account on the same or a different instance. All imported records are reassigned to your account — the original user ID from the export file is not preserved.
Exports produced through the Termix UI keep credential fields encrypted using your account’s encryption key. When you import such a file into your own account, Termix re-encrypts the data using your current key automatically. If you import into a different account, the data is re-encrypted under that account’s key.

Migrating between Termix instances

To move your full configuration from one Termix server to another:
1

Export from the source instance

Log into your current Termix instance and export your data from Settings → Export Data.
2

Log into the target instance

Open your new Termix instance and sign in or create your account.
3

Import on the target instance

Go to Settings → Import Data and select the file you exported in step 1.
If you are migrating a self-hosted instance and have admin access to both servers, ask your administrator about server-level backup options which may be faster for large datasets.

Build docs developers (and LLMs) love