how to migrate n8n from SQLite to PostgreSQL without losing workflow credentials and execution history

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI), vendor status pages and changelogs, vendor help centers, in-product help

how to migrate n8n from SQLite to PostgreSQL without losing workflow credentials and execution history on n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 comes up often enough in the r/nocode, r/n8n, and adjacent automation communities that there is a stable fix pattern. The pattern I see most often is in Make for exactly this reason - last Tuesday I was mid-build for a client when this exact thing hit me, and the recovery path is mostly known, the vendor help just buries it under three layers of marketing copy.

What how to migrate n8n from sqlite to postgresql without losing workflow credentials and execution history actually involves on n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026

On n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 in my experience the most useful first-pass tools are Prometheus metrics endpoint at /metrics for n8n active execution gauge, n8n community node 'n8n-nodes-debug' for verbose item logging, ngrok for exposing local n8n editor webhook test URL to external SaaS. Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026, the methods that survive contact with a real Monday-morning workload are Run 'npm run lint && npm run build' in custom node package before linking and psql -c "SELECT count(*) FROM execution_entity WHERE finished=false;" to find stuck runs. Anything less than that and you are shipping on vibes.

Authoritative sources for n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 that I cross-reference before committing to a fix: n8n.io/workflows, docs.n8n.io, github.com/n8n-io/n8n. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the platform.

Spot the symptom

Fifth: replay the failing run against a second account or a second connector on the same n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 workspace. The point is to isolate "my credentials" from "my account" from "the whole workspace." If a teammate's identical scenario works but yours does not, the failure is local cache or a stale OAuth grant. If the same scenario fails for everyone in the same workspace, you have a tenant-wide config change or a vendor-side incident. Pin the platform version explicitly while you do this: the platform's About panel, the build hash in the footer, or the engine version returned by a diagnostic call. The version pin is what isolates "their rollout broke me" from "my client is out of date."

Fourth: open the vendor status page for n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 and the connector's upstream status pages for the failing window. The smoking guns are an open incident touching the exact service area you are using, a recent post-mortem covering the same symptom, or a Trust Center advisory on a partial outage. Cross-reference the timestamp of your first failed run against the incident start time - if they match within 5 minutes, stop debugging your own setup and subscribe to the incident updates. Many vendors lag the status page behind the actual incident by 10 to 30 minutes; if Twitter and Reddit are both lit up but the status page is green, trust the crowd and treat it as upstream until proven otherwise.

Start by capturing the exact failure signal in writing before you change a single thing on your n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 setup. In the browser that is the failing request in DevTools Network tab (right-click, Copy as cURL) plus the JS console error. In the platform UI that is the error toast text, the timestamp, and the scenario or workspace id from the URL. On the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 status page capture the incident id and timestamp. Screenshot it. Do not paraphrase. Most n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 support workflows will not even route the ticket without the workspace id or correlation id - the support rep pastes it straight into the internal trace tool and the first response is "we see your request, here is what the backend logged."

Field notes from real n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 incidents

My go-to verification step is `Hit /healthz endpoint on each worker for liveness before traffic shifting`; I learned the hard way that the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language UI will happily lie about whether a flow really ran. When an n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language flow goes sideways on me, the first thing I open is n8n editor Executions panel with per-node input/output inspection, it shows me the real execution state before I start guessing.

I keep Redis CLI BULL queue introspection: KEYS bull:jobs:* docked on a second screen whenever I am building inside n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language; one glance tells me whether the run actually fired or silently skipped. In Automation work, the cost of guessing is almost always higher than the cost of reading the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language changelog, read the changelog first.

Tools I actually reach for

For most n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 stalls I start with n8n editor Executions panel with per-node input/output inspection, fall back to Prometheus metrics endpoint at /metrics for n8n active execution gauge, pgAdmin for inspecting execution_entity and workflow_entity tables, Redis CLI BULL queue introspection: KEYS bull:jobs:* when n8n editor Executions panel with per-node input/output inspection cannot surface the answer, and keep n8n CLI 'n8n execute --id <workflowId>' for headless replay handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the platform.

Verification I run before I call it fixed

Before I mark a n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

psql -c "SELECT count(*) FROM execution_entity WHERE finished=false;" to find stuck runs

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

redis-cli LLEN bull:jobs:wait to confirm queue is draining

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Run 'npm run lint && npm run build' in custom node package before linking

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

docker exec n8n n8n list:workflow --active=true to confirm workflow status

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Inspect ~/.n8n/config to verify encryptionKey matches across worker pods

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 detail, the disambiguation order I lean on is stable. I usually check docs.n8n.io for the ground-truth view on this part of n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026. I usually check blog.n8n.io for the ground-truth view on this part of n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026. I usually check community.n8n.io for the ground-truth view on this part of n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026. Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

If the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 platform is slow, stale, or serving cached errors, work the cache and CDN stack in order. Sign out of the desktop app or browser session, quit it fully (Cmd+Q on macOS, right-click the system tray icon -> Quit on Windows - not just the close button), reopen, sign back in. Clear the local cache (most platforms expose this under Help -> Clear cache, or Settings -> Advanced -> Reset cache). Hard-refresh the web app with Ctrl+Shift+R (or Cmd+Shift+R on macOS) to bypass the local browser cache. Always capture timing before the cache clear to baseline: time how long the failing run takes three times, write it down, then repeat after the cache clear so the delta is provable in your notes. Decision point: managed-device issues go through your IT admin for a tenant-wide config push; personal-device issues go through the in-product Help + Diagnostics flow before you escalate to support.

When the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 platform returns intermittent errors, run delays, or "something went wrong" under normal load, suspect the vendor before blaming your setup. Subscribe to the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 status page RSS or webhook so an open incident lights up your inbox or Slack automatically. Cross-check the vendor Trust Center for any planned maintenance window covering your region. Listen to the vendor X/Twitter status handle - many incidents land there 15 to 30 minutes before the formal status page update. Decision point: if the status page is green but multiple teammates in the same region are seeing the same toast, fail over to the web app (if the desktop client is broken) or to a different device (if the web app is broken) and file a support ticket with the failing screenshot, the workspace id, and the timestamp window; major vendors all accept the workspace id as the primary trace key. Screenshot the failing run with the network indicator and the platform version visible before the failover - that screenshot is what the support team asks for first on any latency or error report.

For any n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 failure that smells like auth or permission, walk the principle of least surprise chain in order. Confirm which account you are actually signed into (top-right avatar on web, account menu on desktop, profile tab on mobile) and confirm it matches the email the connector is bound to. Many "my scenario stopped firing" reports trace to the connector being bound to your personal account while you are signed into your work workspace identity on the same browser profile. Sign out of every account, sign back in with only the canonical work account, and retry. Clear the OAuth grant from the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 connected-apps page if you suspect a stale third-party token (the platform's connector settings, the upstream provider's "third-party apps" page). Decision point: if the account is correct, the connector is bound to that account, and the action still fails with a permission error, ask the workspace owner to re-grant the scope explicitly and to check their workspace-level connector policy for a new restriction.

Automate this fix so you do not do it twice

Codify the platform version pin and rollback as a single notes entry

Once a stable platform version is identified for the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026, write the version string, the build hash, and the workspace policy state to a personal notes entry with the date in the title. Reproducible rollback is then a single download-and-install plus a sign-in. Pin the workspace policy state explicitly so a vendor-side default change does not silently shift behavior under you. Stage the notes entry next to a checklist that lists the failing screenshot, the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 incident id (if any), and the support case number; the second time the workflow breaks at 9 a.m. you do not want to be rediscovering which platform build was actually green.

# Personal notes template (n8n)
Date: 2026-05-31
Platform: n8n
Working build: 2.45.1 (Build hash: a1b2c3d)
Account: work@example.com
Workspace: ws-prod-n8n
Failing screenshot: ~/notes/n8n-2026-05-31.png
Support case: SUPP-n8n-12345
Rollback path: download installer from vendor releases page, sign out, reinstall, sign back in

Scrape n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 workspace audit log + integration log via scheduled job

For the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026, workflow faults usually surface as failed run executions, audit-log denials, or quota nags before a full hang. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with platform updates, policy changes, and vendor incidents without staring at the settings panel live. Register the task via cron (Linux / macOS), Windows Task Scheduler (schtasks /create /XML), or a GitHub Actions schedule, then write the CSV to Dropbox / OneDrive / Google Drive for retention. Subscribe a simple dashboard (Google Sheets with a daily import, Airtable scheduled sync, Notion database via the API) to the same bucket so audit events from every n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 workspace converge on a single view without per-workspace clicking.

# Export the platform audit log via the API (Enterprise plan)
curl -X POST https://api.example.com/v1/audit_logs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ -H "Accept: application/json" \ -d '{"start_date":"2026-05-24","end_date":"2026-05-31"}' \ -o n8n-audit-log.json
# Export the run history for the last 7 days
curl -G https://api.example.com/v1/runs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o n8n-runs.json

Monitor + alert via n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 admin reports, audit logs, and personal dashboard ingestion

For the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026, the most useful long-running telemetry is the admin reports + audit logs shipped to a personal dashboard (Google Sheets daily import, Airtable scheduled sync, Notion database via the API, Grafana with a CSV source) and graphed on a single view. Pair that with synthetic monitoring (a small script that triggers the failing scenario or runs the failing action every 5 minutes from at least two devices) so a regional incident lights up before teammates report it. Subscribe the personal inbox or a private Slack channel to the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 status page (Atom/RSS or Statuspage webhook) plus the vendor X/Twitter status handle so an open incident self-correlates with the synthetic failures.

# Tiny synthetic monitor - hit the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 health endpoint every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://api.example.com/v1/me \ >> ~/logs/n8n-synth.log sleep 300
done

Pitfalls

The deepest trap with n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 workflows is treating a recurring class of failure as a one-off incident. A connector hang or a sharing 403 burst gets papered over with a sign-out / sign-in or a re-auth, the platform runs for two weeks, and the exact same signature returns because the root cause was never identified. Codify every case in a personal notes entry, save the working platform version (the About panel) in the same note, and write the exact workspace settings, sharing policy, and connected-apps list into a checklist. After any major platform update on n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 review the workspace settings and the connected-apps grants explicitly, since vendors silently grant or revoke permissions between major releases.

The second half of this pitfall is confirming the fix on a single device when the team is identical. If you and three teammates use the same n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 workspace on the same plan, a vendor-side rollout tends to bite a whole batch within the same hour. Verify on every device and account that touches the failing workflow, log the result and the platform version per attempt, and only then declare the class closed.

Full fix path

• Reproduce the original failing run against n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
• Watch for 24 to 48 hours via the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
• Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
• Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note platform version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
• If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

• Test in a n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 test workspace or on a duplicate scenario first before any change that touches the real workspace. Snapshot the platform version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
• Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
• Use idempotent runs where the n8n Self-Hosted, Queue Mode, Custom Nodes & Expression Language, 2026 API supports it (the platform's run id de-dupe, external id keys on destination records) so a retried run does not create duplicate records.
• Know your rollback path. Platform version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
• For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to back up n8n PostgreSQL database and ~/.n8n/config encryption key before major version upgrade
• how to fix n8n 'Could not decrypt data' after restoring backup without N8N_ENCRYPTION_KEY
• how to fix n8n 'No active workers' error after enabling queue mode without Redis QUEUE_BULL_REDIS_HOST
• how to fix n8n workflow stuck in 'running' state when worker dies mid-execution in queue mode
• how to build n8n expression with $json, $node, $items, and $execution.id for cross-node data lookup
• how to compare n8n self-hosted Community Edition vs n8n Cloud Starter for cost at 50k monthly executions