Importing and Exporting Connections

Use the Connections Explorer import and export actions to reuse connection metadata instead of recreating every profile. Review the selected file format carefully because SQL Developer and Nexo handle passwords differently.

Supported import types

Import type	Imported	Password behavior
Nexo connections export	Profiles, credentials, nested folders, policies, and supported settings	Encrypted credentials are restored after entering the export passphrase
Oracle SQL Developer export	Classic desktop SQL Developer JSON metadata, folders, and supported editor colors	Encrypted SQL Developer passwords are ignored
Oracle SQL Developer for VS Code connections	DBTools connection information, folder hierarchy, and supported TNS or wallet references	Passwords and private wallet credentials are never imported
PL/SQL Developer connections export	Profiles, folders, connection options, and optional TNS alias resolution	Only supported decoded legacy passwords are imported
Oracle tnsnames.ora	TNS aliases and connect descriptors	TNS files do not contain passwords, so none are imported

The Oracle SQL Developer for VS Code importer reads the shared DBTools store used by the extension and SQLcl. It imports connection names, usernames, connect identifiers, supported connection options, and the saved folder structure. It does not read or decrypt credentials.sso, Java wallets, wallet passwords, or saved database passwords. After importing, enter each database password in Nexo and configure or unlock the wallet manually when required.

Import from Oracle SQL Developer

1. In Oracle SQL Developer, export the connections you want to transfer in its JSON connections format.
2. In Nexo SQL Studio, run Import Connections from the Connections Explorer.
3. Select Oracle SQL Developer export.
4. Choose the exported .json file.
5. Review and select the connections to import.

Nexo reads supported connection metadata from the JSON export and recreates SQL Developer navigation folders. It also preserves supported editor colors as folder or connection presentation data.

Saved SQL Developer passwords are not imported. SQL Developer encrypts exported passwords using a format that Nexo cannot decrypt safely, so encrypted password values are ignored. After import, edit or connect each profile, enter its database password, and enable Save password if you want Nexo to store it.

An import may therefore reproduce connection names, database addresses, usernames, connection options, folders, and colors while still requiring credentials. Unsupported SQL Developer-specific properties are ignored.

Import from Oracle SQL Developer for VS Code

1. In Nexo SQL Studio, run Import Connections from the Connections Explorer.
2. Select Oracle SQL Developer for VS Code connections.
3. Choose a detected DBTools store or browse to another DBTools folder.
4. Review and select the connections to import.

Nexo discovers the DBTools store in the standard operating-system locations used by Oracle SQL Developer for VS Code and SQLcl. It recreates the available nested connection folders and imports supported connection metadata. SQLcl connmgr is used as a read-only fallback when direct DBTools metadata is unavailable.

Passwords and private wallet credentials are never imported from Oracle SQL Developer for VS Code. The importer does not read or decrypt credentials.sso or Java-wallet files. Enter the database password in Nexo after import and configure the wallet or TNS configuration directory manually when needed.

Import a Nexo export

Choose Nexo connections export and select a .nexoconn file. Current Nexo exports are protected by a passphrase; enter the same passphrase that was used when the file was created.

The import can restore selected:

• Connection profiles and credentials
• Nested connection folders and colors
• Per-connection AI/MCP policies
• APEX and ORDS base URLs
• Default deployment targets

You can review the connection list and import only the profiles you need. Existing and imported folder structures are merged for the selected connections.

Export Nexo connections

Run Export Connections from the Connections Explorer and select the profiles to include. Nexo writes a .nexoconn file and asks for a passphrase of at least 12 characters.

The passphrase encrypts the connection snapshot, including exported database credentials, using authenticated encryption. Store and transfer the file as sensitive material even though it is encrypted. The passphrase is not recoverable from the export and should be shared through a separate secure channel.

Metadata-only sharing

Do not assume an exported connection file is safe to publish. A profile can reveal internal hostnames, service names, usernames, deployment targets, and environment organization even without a usable password.

For documentation or support, share only the individual non-sensitive fields that are required. Remove credentials, wallet secrets, private addresses, and production details before attaching connection data.

After an import

1. Open each imported profile and confirm its connect identifier and username.
2. Enter any password that was not transferred.
3. Click Test before saving changes.
4. Review production status, inherited folder safeguards, and AI/MCP permissions.
5. Connect and expand the object tree to confirm that the account reaches the expected schema.