Edgely Console and Edgely Database Manager write your connections, settings and credentials to a file you can keep or carry to another computer and import there. This page covers the four kinds of file, how to make one, how its password encrypts it, and what an import does with duplicates and with a file from the other app.
Checked on 2026-11-02 against the code of Edgely Console 1.1.0 and Edgely Database Manager 1.2.0, the releases on Downloads; Console's import of an SSH key that holds a file path on 2026-11-08 against Edgely Console 1.3.0.
When to use an export
- Moving to a new computer. Sync brings your connections but never a password, an SSH key or a token (What sync carries): an encrypted export is how they move. From Console, export the vault (
.evlt) and a Full Export (.efull); from Database Manager, the vault and a connections file (.econor.efull). On the new computer import the.evltfirst, then the other file, so every connection finds its credentials. - A vault in silent mode. Its key is kept by this computer's operating system, so the vault file opens nowhere else (Silent mode and master password). Export the credentials before you change computers.
- A backup kept away from the computer, to import after a reinstall or a lost disk.
Other tools' files have their own importers: see Import your connections from other tools.
The four files
| File | What it carries | Encrypted | Read by |
|---|---|---|---|
.econ | Connections and groups; from Console, optionally the credentials they use | Console: optional, required with credentials. Database Manager: never | Both apps |
.efull | Connections, groups and app settings, in a ZIP archive; from Console, optionally the credentials they use | As .econ | Both apps |
.eset | App settings, connections and groups, never a credential | Never | Both apps |
.evlt | Every credential in the vault, and nothing else | Always | Both apps |
Only an .evlt backs up the whole vault. A Console .econ or .efull with credentials carries each exported connection's default credential and any credential one of its protocols has of its own, but leaves out every other credential and every SSH key certificate.
A connection travels with what you set in its editor, its group and, from Console, its port forwarding rules and its links to credentials and to its jump host. A Database Manager connection carries its SSH key's path, not the key, and the names of the vault entries it uses (their ids, never a password). Console's app settings leave out what belongs to one computer, such as the AI API key and the vault's unlock options. Database Manager's are its theme and accent colour, its editor, query, grid and export preferences, the connection timeout and a few general switches.
Export from Edgely Console
Connections, full and settings exports are made in the Export Data wizard:
- Open it from Connections > Export Connections in the ribbon, Settings > Vault > Unified Export, or Settings > Account & Sync > Backup & Restore > Export.
- On Type, pick Connections (
.econ), Full Export (.efull) or Settings (.eset), and click Next. - On Select, tick the connections to export (all are ticked at first). A full export also lists the groups and offers Include app settings. Click Next.
- On Security, for connections and full exports, turn on Include Credentials to put the credentials the selected connections use in the file: each one's default credential and any credential a protocol has of its own. Encrypt Export File then turns on and stays on; without credentials it is your choice. A settings export is never encrypted.
- When encrypting, type the Encryption Password and Confirm Password. Click Export and choose where to save.
Include Credentials is greyed out (No credentials are used by selected connections) when no selected connection uses a credential.
Export the whole vault (.evlt)
- Open Vault > Export Vault in the ribbon, or Export beside Export Vault in Settings > Vault, with the vault unlocked.
- With a master password, type it in Master Password; a wrong one is refused with
Invalid master password. A vault in silent mode does not ask. - Type the Export Password and Confirm Export Password, click Export and choose where to save.
The .evlt holds every credential: passwords, private keys with their passphrases, API tokens and client secrets, and SSH key certificates.
Export from Edgely Database Manager
- Settings > Account & Sync > Backup & Restore > Export asks Choose what to export: (Connections, Full Export or Settings), then where to save. Every saved connection goes in, with no selection and no password.
- Connections > Export Connections in the ribbon, and Export in the Connections Manager's quick actions, write an
.econof every connection. - Settings > Vault > Export Vault, or Vault > Export Vault in the ribbon, writes an
.evltof every credential: type a password of at least 12 characters twice (Export stays off until it is), click Export and choose where to save. No master password is asked.
A Database Manager SSH-key credential names a key file on disk. Its .evlt carries the key itself, read from that file, with its passphrase. A key whose file cannot be read travels as its path only, and the export names it: Console cannot sign in with such an entry, and Database Manager needs the key file at the same path. Console imports it all the same and names it (see Between Console and Database Manager, below).
The export password
- Both apps refuse an export password shorter than 12 characters: Console for every file it encrypts, Database Manager for its
.evlt, the only file it encrypts. - The export password is separate from the master password, and Edgely keeps no copy of it: a lost password is a lost file.
How a file is encrypted
An encrypted file uses AES-256-GCM with a key derived from your password by Argon2id (64 MiB of memory, 3 passes). GCM authenticates the encrypted part, so a wrong password and altered encrypted content are refused alike. An encrypted .econ or .efull hides everything, connection names and hosts included; an .evlt shows only when it was written and how many credentials it holds.
Every other file is plain JSON (zipped, for an .efull) that anyone can read: every .eset, every Database Manager .econ and .efull, and a Console file exported without encryption. A very old Console file whose content starts with EDGELY_B64_V1: was never encrypted, whatever was asked when it was written: Console imports it without a password.
Import into Edgely Console
- Open the Import Data wizard from Connections > Import Connections in the ribbon, Settings > Vault > Unified Import, or Settings > Account & Sync > Backup & Restore > Import.
- Use Click to select file to choose an
.econ,.evlt,.efullor.eset. Click Next. - For an encrypted file, type the Decryption Password and click Next. A wrong one shows
Failed to decrypt: Invalid password or corrupted file. - The preview counts and lists the connections, credentials and groups, and the conflicts with yours. When the file has settings, untick Import app settings to keep your own. Click Next.
- Choose how to handle conflicts and click Import.
The preview is not a selection: every item is imported, subject to the conflict choice.
Vault > Import Vault > Edgely (.evlt) also imports an .evlt, with no preview and no conflict choice: a credential it already knows is skipped.
Duplicates and conflicts in Console
An item conflicts with one of yours when it is the same, ignoring case: a connection when its name and host both match, a group when its whole path matches, a credential when its name matches.
| Choice | What happens |
|---|---|
| Skip existing (the default) | Yours is kept. The file's connections in a skipped group go into yours, and links to a skipped credential or jump host point at yours |
| Overwrite existing | Yours is updated in place and keeps its identity, so whatever used it still does. A group keeps what was inside it |
| Rename imported | The file's item is added with _imported after its name |
In an .evlt, a credential conflicts only if it is the very one the file was exported from (or was imported from that file before), whatever it is called now. Overwrite existing replaces it in place and counts it as replaced, the other two skip it, and every other credential is added, even under a name you already use.
A link to a credential or jump host that is neither in the file nor in this vault is dropped (a protocol then uses the default credential), and the result warns about a lost default credential or jump host.
Import into Edgely Database Manager
- The Welcome page's Import Connections card and Settings > Account & Sync > Backup & Restore > Import show an Import Preview of what the file holds and its conflicts; confirm with Import N items.
- Import in the Connections Manager's quick actions imports at once, without a preview.
- The ribbon's Connections > Import Connections reads other tools' files only.
There is no conflict choice: a connection whose name you already use, ignoring case, is skipped and counted as skipped. Settings in the file are always applied, at once. A file of a newer format version is refused and asks you to update Edgely Database Manager, and an .evlt is refused with a pointer to Settings > Vault > Import Vault.
An imported connection keeps the vault entry its file names when the vault is unlocked, holds that entry, and no other connection uses it yet: import the .evlt first, then the connection file, and each connection finds its credentials again. Otherwise it comes in without them: open it and pick its credential again, or type its password.
To import an .evlt, from either app, open Settings > Vault > Import Vault or Vault > Import Vault in the ribbon, click Browse, type the password, click Preview to count the credentials if you like, then Import. A credential the vault already holds (the same entry imported before, or one whose name is spelled exactly the same) is skipped; nothing is overwritten. An SSH key in the file is written to the ssh_keys folder of the app's data folder, readable by your account only. A wrong password is refused with Wrong password, or the vault backup has been modified. An .evlt written by Database Manager 1.1.0 or earlier still imports with its password; one written before 0.9 was only scrambled, not encrypted, and its import says to export the vault again and delete the old file.
Between Console and Database Manager
| File | Imported into | What happens |
|---|---|---|
Console .econ, .efull or .eset, not encrypted | Database Manager | A connection with a protocol on port 5432, 3306, 1433 or 1521 becomes a PostgreSQL, MySQL, SQL Server or Oracle connection with its name, host, port, username and group; its notes are replaced by Imported from Edgely Console. The other servers are left out, counted in the preview and named in the import's notice |
| Console file, encrypted | Database Manager | Refused: Database Manager cannot decrypt it. Export it again without encryption (so without credentials), or import it in Console |
Database Manager .econ, .efull or .eset | Console | Each database connection is skipped, with a warning naming it, and a group that holds only such connections is not created. The file's settings are left out, with the warning Settings not imported: they are Database Manager's. |
.evlt | The other app | Imported as in the app that wrote it: both apps write and read the same file. An SSH key whose file Database Manager could not read at export travels as its path only, which Console cannot sign in with. Console imports it and names it, in the preview's Key file paths and in the result: edit it and use Load from file to bring in its key. Console 1.2.0 and earlier import it without a word |
Credentials therefore cross between the apps in an .evlt only. Settings never cross: each app reads only its own, and neither reports settings imported from the other's file.
Keep the file safe
- A file that holds credentials opens all of them for whoever has its password: send the two by different routes. An unencrypted file still names your hosts, users and notes.
- To be sure of a backup's password, open it in the import wizard as far as its preview (in Database Manager's Import Vault, Preview), then cancel. Delete the exports you no longer need.