n8n 3.0 upgrade checklist

n8n 3.0 lands in October and it is an operational release: breaking changes, removed nodes and legacy cleanup. This free checklist walks you through everything that breaks, in the order you should check it, so the upgrade takes minutes instead of a weekend.

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.

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.