What it does
Reads from a SQLite database, a live Postgres-backed n8n, or the n8n Public API. Exports to disk or pushes straight into another running instance. Cross-instance, key-aware credential handling included.
📁
Three source modes
Read directly from a local database.sqlite file, connect to a Postgres-backed n8n (production deployments), or talk to a running instance via its Public API with a URL and key. Toggle without disconnecting — all three can be configured at the same time.
🛡️
Read-only by design
For Postgres sources the wizard forces every session into default_transaction_read_only = ON at the protocol level. Postgres itself rejects writes regardless of the role's permissions. The wizard's code only ever issues SELECT queries anyway — but if someone hands over a write-capable role by mistake, nothing destructive can happen.
🧬
Workflows: portable JSON
Output matches what the n8n editor's "Download" button produces, so the file pastes straight into the canvas, imports via "Import from File", or works with n8n import:workflow. Server-managed fields are stripped automatically so cross-instance imports never break.
🔐
Credentials, encrypted or decrypted
Default export is the encrypted blob (CLI-compatible, ideal for same-instance restore). Tick "Decrypt" with the source instance's encryption key to produce plaintext JSON for cross-instance migration. The target instance re-encrypts with its own key on import.
🚀
Push directly to another n8n
From the export modal pick "Push to a remote n8n instance" — the app POSTs each item to the target's Public API. For credentials, the target re-encrypts on receipt. Ideal for staging → production promotion or migrating between hosts.
📥
Import local JSON files
Already have JSON files from n8n export:workflow or another tool? Switch to Remote API mode and use the Import workflows tab to push files (or a whole folder) into your connected instance with one click.
📜
Built-in logs for support
Every run writes to a rotating log file. The Logs button in the top bar opens its location, so when something goes wrong you can attach the log to your bug report. Portable saves logs next to the .exe; installed saves to %APPDATA%.