# Migrate from Termius to CtrlOps
URL: https://ctrlops.io/docs/getting-started/migrate-from-termius
Published: 2026-08-04
Updated: 2026-11-05

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.

[Watch: How to Migrate From Termius to CtrlOps - Servers, Keys & All](https://www.youtube.com/watch?v=zcJ4PaEUk5U)

## 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, sync groups, port-forwarding rules, and your Termius subscription. The importer reads the server list, so anything stored outside it stays behind. Your connections are what move. Forwarding rules are the one thing worth rebuilding straight away, and the [Port Forwarding](https://ctrlops.io/docs/modules/port-forwarding) tab takes a pasted `ssh -L` command directly.

> 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](https://ctrlops.io/docs/getting-started/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 CtrlOps `.ctrlops` backup files. The one you want is under **MIGRATE**: click **Import from Termius**.

![The All Servers three-dot menu open, showing Import servers and Export servers under SERVER LIST and Import from Termius under MIGRATE](https://cdn.ctrlops.io/docs/open-termius-impoter.webp)

Import from Termius sits under the MIGRATE heading in the three-dot menu.

### 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

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

Windows may prompt you to confirm that CtrlOps can read the credentials Termius has saved on this machine. Approve the prompt to continue.

### Linux

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**.

![The Found 4 servers dialog listing each imported server with its user@address, Key or Agent authentication type, NEW or UPDATE badge, and a checkbox, above the Import 4 servers button](https://cdn.ctrlops.io/docs/pick-server-you-want.webp)

Every server is checked by default - uncheck the ones you do not want before clicking 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](https://ctrlops.io/docs/getting-started/first-connection#connection-troubleshooting) 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](https://ctrlops.io/docs/modules/ssh-management).
- **Export a backup of your new server list.** Three-dot menu → **Export servers** writes a `.ctrlops` backup file you can restore on another machine. See [Server Management](https://ctrlops.io/docs/modules/server-management#backup-your-saved-servers).
- **Go beyond SSH.** Once connected you get the [AI Terminal](https://ctrlops.io/docs/modules/ai-terminal), live [CPU, RAM, and disk monitoring](https://ctrlops.io/docs/modules/infra-details), [log search](https://ctrlops.io/docs/modules/log-management), and [one-click deployments](https://ctrlops.io/docs/modules/deployment) from the same app.

## Troubleshooting

### The importer did not find any servers

The importer reads Termius data stored on the computer you are running CtrlOps on. If Termius is not installed on this machine, or your hosts live only in Termius cloud sync and have never been synced down locally, there is nothing for CtrlOps to read. Open Termius on this computer, confirm your hosts are visible there, then run the import again.

### I clicked Deny on the credential prompt

Nothing is imported if you deny the prompt. Open the three-dot menu again, choose **Import from Termius**, and approve the prompt this time. There is no limit on how often you can run the importer.

### My operating system asks for the password every time I import

On macOS, click **Always Allow** instead of **Allow** on the keychain prompt. macOS then remembers the decision for CtrlOps and stops asking on future imports.

### A server fails to connect after importing

The import brings across the address, port, username, and key reference exactly as Termius had them, so a failure here is usually the same as any other SSH connection problem. Work through [Connection Troubleshooting](https://ctrlops.io/docs/getting-started/first-connection#connection-troubleshooting) - it covers authentication failures, timeouts, refused connections, and the Windows SSH agent service.

### Does my Termius data leave my computer?

No. CtrlOps reads the Termius data stored locally on your machine and writes it into your local CtrlOps server list. Nothing is uploaded, and your keys and credentials stay on the same computer they were already on. See [SSH Security](https://ctrlops.io/docs/core/ssh-security) for how CtrlOps stores connection data.

### Can I import a plain JSON server list instead?

Not a plain list. The same three-dot menu has **Import servers** and **Export servers** under the **SERVER LIST** heading, and they only work with CtrlOps `.ctrlops` backup files. **Import from Termius** is a separate entry under **MIGRATE** that reads Termius data directly, with no export step in between. The [server discovery guide](https://ctrlops.io/docs/core/server-discovery#importing-infrastructure) covers the JSON route.

## Next Steps

- [Your First Connection](https://ctrlops.io/docs/getting-started/first-connection) - the full connection form, authentication options, and proxy setup
- [Server Management](https://ctrlops.io/docs/modules/server-management) - organise, back up, and manage your whole server list
- [AI Terminal](https://ctrlops.io/docs/modules/ai-terminal) - describe what you need in plain English and get the command
- [CtrlOps vs Termius](https://ctrlops.io/compare/ctrlops-vs-termius) - a feature-by-feature comparison if you are still deciding
- [Ughareja Infotech case study](https://ctrlops.io/case-studies/ughareja-infotech) - 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](mailto:support@ctrlops.io)
- **Feature Requests**: Reach out if you have an idea that would make CtrlOps better!
- **Need more help?**: Join our [Discord community](https://discord.gg/JhRCp3hsT9)
