dbx/docs/content/docs/connection-import.mdx

79 lines
3.0 KiB
Plaintext

---
title: Connection Import
description: Import connections from Navicat and DBeaver so you can switch to DBX without re-entering connection details.
---
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 |
<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>
## 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 |