Migrating from FlexionTech to Dobermann
Dobermann has moved from the FlexionTech publisher to the new DBMN publisher on the VS Code Marketplace. Because the publisher has changed, the new extension uses a separate storage namespace — your existing data will not carry over automatically. You need to export from the old extension and import into the new one.
The process takes about 2 minutes.
Before You Start
Open the same Dobermann workspace you were using with the FlexionTech extension. Execution history (your past batch results and transaction logs) is stored in a SQLite database inside your workspace folder. If you open a different workspace, that history won’t be there.
Your endpoints and environments will be migrated via export/import (Step 1–4 below). But execution history stays with the workspace automatically — as long as you keep using the same one, the new extension picks it up.
Step 1: Export Your Data
While the FlexionTech extension is still installed, export everything:
- Open Command Palette (
Ctrl+Shift+P/Cmd+Shift+P) - Run
Dobermann: Export Workspace(the old extension’s command) - Save the file somewhere easy to find
This exports all your endpoints, folders, and environments into a single file. Sensitive data (tokens, secrets) is excluded for security.
Step 2: Install Dobermann from the Marketplace
Install the new version published under DBMN:
- Open Extensions (
Ctrl+Shift+X/Cmd+Shift+X) - Search for “Dobermann”
- Look for the one published by dbmn (not FlexionTech)
- Click Install
Or install directly from the VS Code Marketplace.
Step 3: Open Dobermann
In the Activity Bar, click Dobermann — the icon tooltip now reads “Dobermann”. The Hub opens as an editor tab.
Endpoints will be empty — this is expected. Your data is coming in the next step.
Step 4: Import Your Data
- In the Hub, open Import
- Drag the export file from Step 1 onto the drop zone, or click Browse Computer
- Review the list — every item should be marked CREATE on a fresh install
- Click Import Configuration
See Import/Export for what the badges mean.
Step 5: Re-enter Credentials
Tokens and secrets are never included in exports. For each environment:
- OAuth — Re-enter your client secret, then sign in. Important: the OAuth redirect URI has changed from
vscode://FlexionTech.active8/oauth-callbacktovscode://dbmn.dobermann/oauth-callback. You must update this in your OAuth provider’s client configuration — otherwise you’ll get anInvalid parameter: redirect_urierror in the browser when signing in. - JWT — Re-enter your token
- Test — Run a single API call against a non-production environment to confirm connectivity
Step 6: Uninstall the FlexionTech Extension
Once you’ve confirmed everything works:
- Open Extensions (
Ctrl+Shift+X/Cmd+Shift+X) - Find the old FlexionTech version
- Click Uninstall
- Reload VS Code when prompted
Do not run both extensions at the same time — they can conflict with each other.
After Migration
- Sign in to DBMN — If you had a DBMN account, sign in again from the Account panel.
- Execution history — If you kept the same workspace (see Before You Start), your past batch results and transaction logs are already available in the new extension.
Troubleshooting
I can see both extensions in the Activity Bar Uninstall the FlexionTech version (Step 6). Having both installed simultaneously can cause conflicts.
OAuth stopped working / Invalid parameter: redirect_uri
The redirect URI changed with the new publisher. Update your OAuth provider’s client configuration to use vscode://dbmn.dobermann/oauth-callback (was vscode://FlexionTech.active8/oauth-callback). Then re-enter your client secret in the environment settings — secrets are never transferred between extensions.
Need help? Report an issue or ask in GitHub Discussions.