125 lines
4.5 KiB
Plaintext
125 lines
4.5 KiB
Plaintext
---
|
|
title: Connection Import
|
|
description: Import connections, groups, and recognized database profiles from Navicat, DBeaver, and DataGrip.
|
|
---
|
|
|
|
DBX can import connections from other database tools, saving you from manually re-creating dozens of connections when switching tools.
|
|
|
|
## Supported Formats
|
|
|
|
| Source | Format | What's Imported |
|
|
| ------- | ------------------------------ | ---------------------------------------------------- |
|
|
| Navicat | `.ncx` export files | Host, port, username, database type, connection name |
|
|
| DBeaver | Connection configuration files | Host, port, username, database type, connection name |
|
|
| DataGrip | Project or global files such as `dataSources.xml` | JDBC URL, driver, connection name, groups, and readable credentials |
|
|
|
|
<Callout type="info">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.</Callout>
|
|
|
|
## Import Navicat Connections
|
|
|
|
<Steps>
|
|
<Step>
|
|
### Export from Navicat
|
|
|
|
In Navicat, select the connections you want to migrate. Use **File → Export Connections** and save the `.ncx` file.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Open Import Dialog
|
|
|
|
In DBX, go to **Settings → Import Connections** or right-click the sidebar group header and choose **Import Connections**.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Select the NCX File
|
|
|
|
Choose the `.ncx` file you exported from Navicat.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Review and Complete
|
|
|
|
DBX parses the file and lists all found connections. Review the list, re-enter passwords where needed, and save.
|
|
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Import DBeaver Connections
|
|
|
|
<Steps>
|
|
<Step>
|
|
### 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/`.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Open Import Dialog
|
|
|
|
In DBX, go to **Settings → Import Connections**.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Select DBeaver Files
|
|
|
|
Choose the DBeaver connection configuration files (`.dbeaver-data-sources.xml` or similar).
|
|
|
|
</Step>
|
|
<Step>
|
|
### Review and Complete
|
|
|
|
DBX extracts connection details from the configuration. Re-enter any passwords that could not be decrypted.
|
|
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Import DataGrip Connections
|
|
|
|
<Steps>
|
|
<Step>
|
|
### 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.
|
|
|
|
</Step>
|
|
<Step>
|
|
### 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.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Review Groups
|
|
|
|
DataGrip group paths are imported as DBX connection groups so project organization is preserved.
|
|
|
|
</Step>
|
|
<Step>
|
|
### Complete Credentials
|
|
|
|
On macOS, DBX reads DataGrip Keychain passwords when available. Other encrypted or inaccessible credentials must be entered manually.
|
|
|
|
</Step>
|
|
</Steps>
|
|
|
|
## 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
|
|
|
|
| Setting | Reason |
|
|
| ---------------------------- | ------------------------------------------------------------------- |
|
|
| Encrypted passwords | Each tool uses proprietary encryption; passwords must be re-entered |
|
|
| SSH tunnel keys | Key file paths may differ between machines; re-select the key file |
|
|
| Custom driver configurations | Driver paths and versions are tool-specific |
|
|
| Proxy settings | Re-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.
|