Skip to content
ZyncDocs
GitHub Download Zync

Move to Zync

Import SSH config into Zync, move hosts from another SSH client, reconnect credentials, and verify files and tunnels before switching.

You can move common SSH host settings into Zync using Import Config, then assign credentials and recreate the workflows you need. An imported host is not a full migration of another application’s vault, history, tunnels, or settings. Keep your existing client available until you have checked the new connections.

Import an OpenSSH config

Section titled “Import an OpenSSH config”
  1. Install Zync and open New Connection > Import Config.
  2. Select your default ~/.ssh/config, choose a file, or paste config text. On Windows, the usual location is %USERPROFILE%\.ssh\config.
  3. Review the host preview, including the address, username, port, identity file, and jump host.
  4. Select the entries to import. For duplicates, choose Import as New, Update Existing, or Skip intentionally.
  5. Connect to one imported host, verify its host-key fingerprint against a trusted source, and resolve any credential prompt.

Here is a minimal example using placeholder addresses. Replace the addresses, usernames, and key paths with your own. It contains no private key material:

Host bastion
  HostName bastion.example.com
  User deploy
  Port 22
  IdentityFile ~/.ssh/id_ed25519


Host app-staging
  HostName 10.0.0.20
  User deploy
  Port 22
  IdentityFile ~/.ssh/id_ed25519
  ProxyJump bastion

Import both entries together so Zync can resolve the bastion alias. Verify the bastion first, then the staging host. A key path must point to a readable private key on the device running Zync. Moving the config file does not move the key itself.

What the importer carries across

Section titled “What the importer carries across”
Setting Result
Host, HostName, User, Port Saved host identity and endpoint fields.
IdentityFile A local key-file reference; an encrypted key still needs its passphrase.
ProxyJump A jump-host relationship when its value matches an imported host alias. Review unresolved aliases and multi-hop setups manually.
Host * and other wildcard defaults Not applied as OpenSSH inheritance. Give each imported host explicit values.
Include, Match, ProxyCommand Not evaluated as a complete OpenSSH configuration. Prepare simple host entries with the effective values you need.
Forward declarations Not imported with hosts. Recreate them or use the tunnel command importer below.
Key passphrases, vault contents, known-host trust Not transferred by config import. Resolve credentials and verify host fingerprints separately.

The importer recognizes common host fields; it does not run your system’s OpenSSH configuration engine. See Connections for conflict handling and credential choices.

Move from another SSH client

Section titled “Move from another SSH client”

For clients such as Termius, MobaXterm, or PuTTY, start with the actual host settings you are allowed to access. Do not assume a proprietary session file, encrypted vault export, or arbitrary JSON/CSV file matches Zync’s import format.

  1. Record a small set of test hosts: address, port, username, authentication method, and any bastion.
  2. If you have a standard SSH config, use the import flow above. Otherwise, add the hosts manually or prepare explicit SSH config blocks.
  3. Select an existing local private key or add a credential to Local Vault. Do not paste secrets into a public issue, chat, or example config.
  4. Recreate tunnels, snippets, and client-specific preferences separately. A host import does not bring over team access rules, session history, or a managed cloud vault.
  5. Verify each workflow below before retiring the old setup.

Zync’s Import File supports its connection exchange formats. A matching .json or .csv extension alone does not establish compatibility. Export a non-sensitive sample from Zync if you need to inspect the expected structure.

Recreate SSH tunnels

Section titled “Recreate SSH tunnels”

Host imports do not carry over LocalForward, RemoteForward, or DynamicForward directives. Open the tunnel import action and paste a command containing -L, -R, or -D flags instead.

Terminal window
ssh -L 15432:127.0.0.1:5432 -D 1080 deploy@bastion.example.com

For this example, select the saved bastion connection and review the imported entries. The local forward should listen on 127.0.0.1:15432 and reach port 5432 on the SSH server’s loopback interface. The SOCKS proxy should listen locally on port 1080. Use your own ports and targets, and connect the host before starting the tunnels.

Read Port Forwarding for bind addresses, server permissions, and reconnect behavior. Public URLs is a separate HTTPS sharing service.

Verify before switching

Section titled “Verify before switching”
Check Expected result
Connect to a test host The verified host fingerprint and intended remote user match your existing setup.
Open Files The server’s SFTP subsystem opens a directory your user can access.
Transfer a disposable test file Upload it to a test directory, download it, and compare the contents. Do not overwrite a production file for this check.
Start a local tunnel Your client reaches the intended service through the selected local port.
Reconnect Credentials resolve as intended and the expected tunnels restart.
Reopen Zync Saved hosts and settings are present. Key paths still resolve on this device.

Set up backup separately

Section titled “Set up backup separately”

Moving hosts does not enable cloud backup. Zync’s optional Sync & Backup encrypts selected records for your Google Drive and currently uses manual sync actions. Configure it after the local setup works, and review any restore before applying it on another device.

Next steps

Section titled “Next steps”