DBX

Connection Import

DBX can import connections from other database tools, saving you from manually re-creating dozens of connections when switching tools.

Supported Formats

SourceFormatWhat's Imported
Navicat.ncx export filesHost, port, username, database type, connection name
DBeaverConnection configuration filesHost, port, username, database type, connection name
DataGripProject or global files such as dataSources.xmlJDBC URL, driver, connection name, groups, and readable credentials
RedisDesktopManagerJSON exportRedis connections, nested groups, authentication, TLS, and SSH settings
Another Redis Desktop Manager.ano exportRedis connections, groups, ACL, SSH/TLS, Sentinel, and Cluster settings
Imported connections preserve the original connection name and type. Passwords stored in encrypted format by other tools cannot be decrypted — you will need to re-enter passwords after import.

Import Navicat Connections

Export from Navicat

In Navicat, select the connections you want to migrate. Use File → Export Connections and save the .ncx file.

Open Import Dialog

In DBX, go to Settings → Import Connections or right-click the sidebar group header and choose Import Connections.

Select the NCX File

Choose the .ncx file you exported from Navicat.

Review and Complete

DBX parses the file and lists all found connections. Review the list, re-enter passwords where needed, and save.

Import DBeaver Connections

Locate DBeaver Configuration

DBeaver stores connections in its workspace directory. The exact path depends on your OS and DBeaver version. Common locations include ~/.local/share/DBeaverData/workspace6/General/.dbeaver/.

Open Import Dialog

In DBX, go to Settings → Import Connections.

Select DBeaver Files

Choose the DBeaver connection configuration files (.dbeaver-data-sources.xml or similar).

Review and Complete

DBX extracts connection details from the configuration. Re-enter any passwords that could not be decrypted.

Import DataGrip Connections

Select Configuration

Choose Import DataGrip in DBX and select dataSources.xml from a DataGrip project or global configuration. A matching local file in the same directory can supply additional fields.

Review Type Detection

DBX combines driver references, database product names, JDBC subprotocols, and driver classes. Databases such as KingbaseES map to their DBX profile; unknown drivers remain generic JDBC.

Review Groups

DataGrip group paths are imported as DBX connection groups so project organization is preserved.

Complete Credentials

On macOS, DBX reads DataGrip Keychain passwords when available. Other encrypted or inaccessible credentials must be entered manually.

Import RedisDesktopManager Connections

Export a JSON file from RedisDesktopManager, then choose Import RedisDesktopManager from the sidebar or welcome-page import menu. Review the connection selector, select the connections to migrate, and confirm. Connections and nested groups are imported without overwriting existing connections.

Standalone Redis host, port, ACL username, auth password, key separator and filter, and SSH password, private-key or agent settings are supported. Connection and execution timeouts are converted from milliseconds to seconds.

TLS CA, client certificate and private-key paths are preserved, but files are not read or copied. Check paths after moving between machines. RDM's ignore-certificate-errors setting is not inherited. Export files may contain plaintext passwords; keep them secure. Importing does not automatically connect to Redis.

Import Another Redis Desktop Manager Connections

Export connections.ano from Another Redis Desktop Manager settings. Choose Import Another Redis Desktop Manager in the sidebar or welcome-screen import menu, select connections, confirm, and optionally restore their groups. Both legacy connection arrays and newer connections / groups bundles are supported, including standalone, Sentinel, Cluster, and read-only settings.

The file is Base64-wrapped UTF-8 JSON, not encryption, and may contain plaintext Redis, SSH, and Sentinel credentials. Keep it private. SSH key passphrases and certificate/key file paths are preserved without reading or copying local files; review paths after moving machines. Sentinel credentials remain separate from Redis node credentials.

Custom TLS servername overrides and nonempty NAT mappings cannot be faithfully represented and are explicitly rejected rather than silently dropped. Limits are 16 MiB and 10,000 connections/groups each. Invalid files fail before saving any connections. Runtime key / current db fields are ignored; importing neither overwrites existing connections nor connects automatically.

After Import

Imported connections appear in the sidebar alongside manually created ones. You should:

  • Test each connection to verify the imported settings work
  • Set passwords for connections where the original password could not be imported
  • Assign connection colors to distinguish production, staging, and development environments
  • Configure SSH tunnels for connections that require them
  • Set visible database filters if the server contains many databases

What Cannot Be Imported

SettingReason
Encrypted passwordsEach tool uses proprietary encryption; passwords must be re-entered
SSH tunnel keysKey file paths may differ between machines; re-select the key file
Custom driver configurationsDriver paths and versions are tool-specific
Proxy settingsRe-configure in the connection's Proxy tab

Import creates connection drafts; it does not prove they are reachable. Review the database profile, JDBC URL, SSL, SSH, proxy, and database fields before saving, then test every imported connection.