Migrate from Termius to CtrlOps
Move your saved Termius servers into CtrlOps in about 30 seconds. The built-in importer reads your hosts, ports, usernames, and SSH keys locally, so you never re-enter a connection by hand.
Already using Termius? Moving your servers into CtrlOps takes about thirty seconds, and you will not have to re-enter a thing. CtrlOps has a built-in importer that reads your saved Termius hosts directly, so there is no export file to generate and no IPs or keys to copy across by hand.
What comes over
| From Termius | Into CtrlOps |
|---|---|
| Host name or label | The server name on your dashboard |
| Address or hostname | The server IP address |
| Port | The SSH port |
| Username | The SSH username |
| SSH key or agent authentication | The saved authentication method for that connection |
What does not come across: Termius snippets, port-forwarding rules, sync groups, and your Termius subscription. Those are Termius-specific features with no direct equivalent in the CtrlOps server list. Your connections are what move.
Everything is read locally on your machine. CtrlOps opens the Termius data already stored on this computer and writes it into your local CtrlOps server list. Nothing is uploaded.
Before you start
- CtrlOps installed and signed in. If you have not installed it yet, start with the Quick Start.
- Termius installed on the same computer, with your hosts visible in it. The importer reads local Termius data, so hosts that exist only in Termius cloud sync need to be synced down to this machine first.
- Your computer login password. Your operating system will ask for it once, to grant CtrlOps permission to read the credentials Termius has saved.
Import your Termius servers
Open the Termius importer
Open CtrlOps and go to All Servers. In the top right, click the three-dot menu next to the view switcher.
The menu has two groups. Under SERVER LIST you get Import servers and Export servers, which work with the standard CtrlOps JSON format. The one you want is under MIGRATE: click Import from Termius.
Review what comes over
A confirmation screen appears showing exactly what CtrlOps is about to read: your servers, ports, usernames, and SSH keys.
Read it, then click Import Servers.
Unlock your saved Termius credentials
Termius stores its credentials in your operating system's secure credential store, so your OS asks you to approve access before CtrlOps can read them. This is your system granting permission, not CtrlOps asking you for a password it keeps.
macOS shows a dialog reading "CtrlOps wants to use your confidential information stored in 'Termius' in your keychain."
Enter your login keychain password - the same password you use to log into your Mac - and click Allow.
Click Always Allow instead if you would rather macOS stopped asking on future imports.
Windows may prompt you to confirm that CtrlOps can read the credentials Termius has saved on this machine. Approve the prompt to continue.
Depending on your desktop environment, your keyring (GNOME Keyring, KWallet, or similar) may ask you to unlock it before CtrlOps can read the saved Termius credentials. Enter your keyring password and allow access to continue.
CtrlOps then shows "Reading your Termius servers..." while it works through your saved hosts.
If you click Deny, the import stops and nothing is added. Open the three-dot menu and run Import from Termius again when you are ready.
Pick the servers you want
CtrlOps lists everything it found, for example "Found 4 servers", with a short summary above the list telling you how many are new and how many are already in your list.
Each row shows the server name, its user@address, and the authentication type it uses - Key for a saved SSH key, Agent for an SSH agent connection. Servers that are not already in CtrlOps carry a green NEW badge.
Everything is selected by default. Uncheck any server you do not want, or use Deselect all and pick just the ones you need. The running count on the right tells you how many are selected.
When the selection looks right, click Import.
Connect to an imported server
A confirmation appears and your servers land on the All Servers dashboard, each showing its address and the authentication method it will use.
Click the play button on any server card to open a connection. No manual setup, no copying IPs and keys across one at a time.
After the import
Your servers are in CtrlOps and ready to use. A few things worth doing next:
- Connect to one server to confirm the credentials work. If a connection fails, the first connection troubleshooting guide covers the common causes.
- Run the SSH Setup Wizard if you want to generate a fresh key or push a key to a server. See SSH Management.
- Export a backup of your new server list. Three-dot menu → Export servers writes a JSON file you can restore on another machine. See Server Management.
- Go beyond SSH. Once connected you get the AI Terminal, live CPU, RAM, and disk monitoring, log search, and one-click deployments from the same app.
Troubleshooting
Next Steps
- Your First Connection - the full connection form, authentication options, and proxy setup
- Server Management - organise, back up, and manage your whole server list
- AI Terminal - describe what you need in plain English and get the command
- CtrlOps vs Termius - a feature-by-feature comparison if you are still deciding
- Ughareja Infotech case study - how one team moved 6 servers off Termius in under 2 minutes
Need Help?
Can't find your answer in the docs? We're here to help you get unstuck.
- Email Support: support@ctrlops.io
- Feature Requests: Reach out if you have an idea that would make CtrlOps better!
- Need more help?: Join our Discord community
Your First Connection
Connect CtrlOps to your first Linux server using SSH keys, a password, or a pasted connection string. Step-by-step setup, no command line needed.
AI SSH Terminal
CtrlOps AI SSH Terminal is a full Linux terminal with a built-in AI terminal assistant. Ask questions in plain English, get the right Linux commands, review before execution, and let AI explain every output. It turns natural language into bash - instantly.