SQLly logoSQLly

pgAdmin

functional

Move PostgreSQL servers between pgAdmin and SQLly with the servers.json file pgAdmin's Import/Export Servers tool reads and writes.

pgAdmin 4 imports and exports its server list as servers.json, a format documented on pgAdmin's Import/Export Servers page. SQLly reads and writes the same file for PostgreSQL and the engines that speak its protocol: CockroachDB, YugabyteDB, Neon, Supabase, Amazon Aurora and RDS for PostgreSQL, Azure Database for PostgreSQL and Cloud SQL for PostgreSQL.

From pgAdmin into SQLly

  1. In pgAdmin choose Tools → Import/Export Servers, pick Export, choose the servers, and save the file. (On a server install, setup.py dump-servers servers.json does the same from the command line.)
  2. In SQLly choose File → Import From Other Tools… and pick the file.
  • Kept - name, server group (as a project, except pgAdmin's default Servers group), host or host address, port, maintenance database, user name, SSL mode and certificate paths (read from the top-level SSLMode or from ConnectionParameters, whichever the pgAdmin version wrote), and the SSH tunnel's host, port, user and identity file.
  • Left behind - passwords and pass files, colors and tags, the role and database restriction, and servers defined only by a Service name (import your pg_service.conf for those).

From SQLly into pgAdmin

  1. Choose File → Export for Other Tools → pgAdmin (servers.json)…. Only PostgreSQL-family connections are listed. Tick the ones you want and save.
  2. In pgAdmin choose Tools → Import/Export Servers, pick Import, choose the file, leave Remove all the existing servers off, and finish the wizard. A server install can run setup.py load-servers servers.json instead.

SQLly projects become pgAdmin server groups (connections without one land in Servers), and each server's SSL mode is written both at the top level and in ConnectionParameters, so older and newer pgAdmin releases read it the same way.