Compatibility

Bring connections, notebooks and snippets over from other database tools, and hand them back out, in each tool's own documented file format.

Nobody switches database tools on a quiet afternoon with nothing else to do. You switch in the middle of a project, with forty saved connections, a notebook someone shared last quarter, and a drawer of snippets your fingers already know. This section covers everything SQLly can read from other tools and write back for them, so trying SQLly costs one import and leaving it (or working alongside a teammate who uses something else) costs one export.

Only documented formats. SQLly reads and writes a tool's files only when the tool documents them, or ships them as a plain, stable export that the tool itself re-imports. Guessing at a private format produces imports that half-work and break on the next release, so tools without one are listed under Formats SQLly does not read yet with the quickest way across.

At a glance

Tool	File	Import into SQLly	Export from SQLly
DataGrip & JetBrains IDEs	`dataSources.xml`	Connections	Connections
DBeaver	`data-sources.json`	Connections	Connections
pgAdmin	`servers.json`	Connections	Connections
Azure Data Studio & VS Code	`settings.json`, `.ipynb`, snippet files	Connections, notebooks, snippets	Connections, notebooks, snippets
DbGate	connection `.env`	Connections	Connections
psql & libpq tools	`pg_service.conf`	Connections	Connections
Jupyter	`.ipynb`	Notebooks	Notebooks
VS Code	`.code-snippets`, `sql.json`	Snippets	Snippets
TablePlus	`Connections.plist`, `.tableplusconnection`	Connections	-
Navicat	`.ncx`	Connections	-
Redis Insight	database export (JSON)	Connections, with passwords	-

Where the commands are

Connections in - File → Import From Other Tools… (also in the command palette). Pick the file; SQLly works out which tool wrote it, shows every connection it found and every one it is skipping, with the reason, and imports nothing until you confirm.
Connections out - File → Export for Other Tools, then the tool. The picker lists only the connections that tool can open; tick the servers and databases you want and save.
Notebooks - open an .ipynb with File → Open Notebook…; a notebook opened that way saves back as .ipynb, and Export Jupyter in the notebook toolbar writes a copy of any notebook. See Jupyter notebooks.
Snippets - Preferences → Editor → Snippets & Quick Actions, then Import from VS Code… or Export for VS Code….

Passwords

Exports for other tools never contain a password, a passphrase, or a token, whatever the target format allows. Imports leave passwords behind too, even when the other tool stored them in the file in clear text: SQLly asks for each one the first time you connect, then keeps it in your system keychain. The one exception is a Redis Insight export you deliberately made with Include passwords ticked; those passwords go straight to the keychain. To move connections with passwords between two copies of SQLly, use the SQLly connection file instead.

What always carries over, and what never does

Host, port, database, user name, and engine come across in every connection format. Folders and groups become SQLly projects, DBeaver connection types and TablePlus environment tags become environments, connection colors are left behind, and TLS modes, certificate paths and SSH tunnel hosts come along wherever both sides can describe them. A connection that already exists in SQLly (same engine, host, port and database) is skipped rather than duplicated. Oracle connections are not imported or exported yet in any format. Per-tool extras with no SQLly equivalent, such as a tool's driver properties, editor layouts or result-set history, are left behind, and each tool's page lists exactly which.

In this section

DataGrip & JetBrains IDEs: Import a project's dataSources.xml, or export your SQLly connections as one DataGrip, IntelliJ and the other JetBrains IDEs read.
DBeaver: Import DBeaver's data-sources.json with its folders and connection types, or export a data-sources.json DBeaver picks up.
pgAdmin: Move PostgreSQL servers between pgAdmin and SQLly with the servers.json file pgAdmin's Import/Export Servers tool reads and writes.
Azure Data Studio & VS Code: Connections from settings.json, SQL notebooks as .ipynb, and snippet files: what comes over from Azure Data Studio and the VS Code MSSQL extension, and what goes back.
DbGate: Read and write the documented DbGate connection variables (CONNECTIONS, SERVER_, ENGINE_ and friends) as an .env file.
psql & pg_service.conf: Import PostgreSQL connection service files, or export your PostgreSQL connections as one psql and every libpq tool understands.
Jupyter notebooks: Open .ipynb notebooks as SQLly notebooks and save SQLly notebooks back out in the standard Jupyter format.
VS Code snippets: Import VS Code and Azure Data Studio snippet files, placeholders and all, and export yours in the same format.
TablePlus: Import TablePlus's Connections.plist, with group names, or a connection export saved without a file password.
Navicat: Import a Navicat .ncx connection export, with SSH tunnels, TLS settings and project folders.
Redis Insight: Import a Redis Insight database export with its passwords, TLS certificates, Cluster and Sentinel settings.
Formats SQLly does not read yet: HeidiSQL, Beekeeper Studio, SSMS registered servers and a few others: why they are missing, and the quickest way across today.