What kind of release this is
n8n 3.0 is not a feature release. It removes legacy nodes, changes defaults and tightens security. Your workflows run real processes, and some of them will behave differently, or stop, the day you upgrade. Six areas change: deployment, removed nodes, AI and chat, behaviour, security and configuration.
Three steps to a calm upgrade
01 Scan. Open Settings › Migration Report in your 2.x instance and read your startup warnings. It lists the affected nodes, Chat Hub use and removed variables on your own instance, before you update.
02 Fix on 2.x. Swap legacy nodes for their successors, update AI Agent nodes, set changed defaults explicitly and export test workflows.
03 Upgrade. Back up the database and volumes, move to Docker, upgrade a staging copy first, then production.
What is in the checklist
- Deployment: self-hosted n8n runs on Docker only, with the one-line setup
- Removed nodes and what to use instead, from Function and Cron to Read PDF and Item Lists
- AI and chat: AI Agent v1 modes, legacy OpenAI nodes, the new chat frame format and Chat Hub
- Behaviour changes in If, Switch, Gmail Trigger and Code node timeouts
- Security: SSRF block list, decompression limits, community packages and key rotation
- Configuration: the renamed storage folder, removed variables and new defaults
- An upgrade-day list with backups, staging and test workflows
Six pages, printable, based on the official v3.0 breaking changes on docs.n8n.io.
Where n8n is heading after 3.0
3.0 is the clean-up. The bigger shift comes after it. The n8n team is rewriting the workflow engine from the ground up around six reliability principles: data saved after every step so runs can be inspected and resumed, automatic retries only for steps that are safe to repeat, repair of stuck runs, sandboxed code, dedicated worker pools and shared load instead of idle backups.
On top of that come one view over all your instances (code name Manifest, currently in trial) and a governance roadmap: native identities for AI agents, SCIM provisioning, policies and hard spending limits, smoother promotion between environments and automated testing for workflows. End-user credentials, which let a workflow run as the person who triggers it, are already available in preview. Read the full recap of the n8n talk on reliability and governance, and see how we apply it in our governance approach.
Go through it together
Bring your Migration Report to the next n8n Amsterdam meetup and we go through it live. Or book a strategic call and we audit your instance with you. The upgrade takes minutes. The audit takes an afternoon. Do the audit first.
Planning to use n8n across more teams or departments? See how we handle an n8n rollout, from the first use case to a central automation team.
Strategic call