Problem
Switching to TablePro from Navicat means re-entering every connection by hand: host, port, user, database, SSH/SSL settings, and so on. For anyone with a large Navicat connection list this is slow and error-prone, and it's a real barrier to adopting TablePro.
Proposed solution
Add an "Import from other apps" flow that can read Navicat's saved connections and create matching TablePro connections.
- Detect or let the user point at Navicat's exported connection file (
.ncx) or its on-disk connection store.
- Map Navicat connection fields to TablePro's connection model: name, database type, host, port, user, default database, SSH tunnel, SSL/TLS options.
- Handle Navicat's encrypted password format where possible; otherwise prompt the user to re-enter passwords after import.
- Show a preview of what will be imported and let the user pick which connections to bring over.
- Surface it in the welcome screen / connection list as "Import from Navicat" (alongside room for other apps like TablePlus, DBeaver later).
Alternatives considered
- Manual re-entry: works but painful for large lists.
- Generic config-file import: still requires the user to understand the format. A guided per-app importer is friendlier.
Related database type
N/A / General
Problem
Switching to TablePro from Navicat means re-entering every connection by hand: host, port, user, database, SSH/SSL settings, and so on. For anyone with a large Navicat connection list this is slow and error-prone, and it's a real barrier to adopting TablePro.
Proposed solution
Add an "Import from other apps" flow that can read Navicat's saved connections and create matching TablePro connections.
.ncx) or its on-disk connection store.Alternatives considered
Related database type
N/A / General