n8n 3.0 has no rollback. Run a dress rehearsal before December

Why a rehearsal, and why now

If your company runs on n8n, the automation tool that moves orders, leads and alerts between your other systems, version 3.0 is coming. n8n released a beta on October 27, 2026 and plans the stable release for early December. The headline features are welcome: tighter security defaults, a Migration Report that tells you what will break, and guardrails against runaway jobs.

The detail that should shape your plan is in n8n's own FAQ. Moving to 3.x is one way. There's no rollback to 2.x; going back means restoring the full backup you took before you clicked. That turns an upgrade from a button into a cutover.

You don't have to rush. n8n says 2.x keeps getting security and critical fixes for 12 months after 3.0 is stable, and new features ship only on 3.x. What you should do now, while nothing is due, is a dress rehearsal: upgrade a copy, run normal work through it, and write down what surprised you. The Migration Report tells you what will break. A rehearsal tells you what you didn't know was running.

One exception to "no rush": if you're still on 1.x, support ends December 31, 2026, and there's no direct path from 1.x to 3.x. Move to 2.x this month. n8n says self-serve Cloud instances still on 1.x at the deadline will be moved to 2.x automatically, which is a worse way to find out about your edge cases.

Read the script: the Migration Report

Every instance on 2.39 or later has a Migration Report under Settings. It has two tabs: workflow issues, which are problems inside specific workflows, and instance issues, which are about how n8n itself is set up. It suggests an owner for each workflow (whoever edited it last), lets an admin reassign, and emails owners what to fix. It also exports a CSV.

Three habits make it useful rather than overwhelming. Sort by most runs, so your busiest workflows get fixed first. Mark workflows that haven't run in a year as "won't fix," which n8n's docs explicitly allow, so the list reflects what matters. And reassign owners before the emails go out; the last person to edit a workflow is often a contractor who left in the spring.

Export the CSV and keep it with the rehearsal notes. It's the closest thing you'll have to a list of everything that touches your business through n8n, which is worth having whether or not you upgrade.

The cast changes: what 3.0 removes or tightens

The full breaking-changes page is long. These are the items that tend to bite a business setup, not a hobby one.

Installation. Self-hosted n8n must run on Docker. Installs run with npm or npx are no longer supported. Kubernetes setups aren't affected. If someone set n8n up on a spare server with npx two years ago, this is the first fix.

Old nodes. The Function and Function Item nodes are gone (use Code). Item Lists is gone (use Split Out, Aggregate, Sort and friends). Cron and Interval are gone (use Schedule Trigger). The legacy OpenAI node and some older AI Agent modes are removed. The report flags each one.

Time limits. The default Code node timeout drops from five minutes to one. A nightly script that reshapes a big export can quietly start failing. You can raise the limit with the N8N_RUNNERS_TASK_TIMEOUT setting, but decide that on purpose.

Files. The in-memory binary data mode is removed. The storage folder is renamed from binaryData to storage, and if both exist, 3.0 refuses to start rather than guess. Decompression limits are lower, which matters if a workflow unzips large supplier files.

Network and credentials. More private address ranges are blocked by default to prevent server-side request forgery. A workflow that calls an internal service on your network may need that host allowed explicitly. Slack credentials now need a signing secret, and unverified community packages are off by default.

Triggers. The Gmail Trigger behaves differently in older node versions: drafts and sent mail no longer fire it, and the per-poll email cap applies every time. If a support or sales flow starts from Gmail, test it with real mail.

The rehearsal itself

A rehearsal is a copy of production, upgraded, doing a normal week of work without touching customers.

Make the copy. Restore last night's backup to a separate instance. Point its credentials at sandboxes or test accounts where you can, and turn off anything that sends email, charges cards or writes to a live system you can't sandbox. Write down which ones you switched off; that list is part of the result.

Upgrade it. Follow n8n's path: latest 2.x, fix or mark items in the Migration Report, full backup, then 3.0 on the copy. Note how long each step took, because those times become your production maintenance window.

Run real work. Replay a day of webhooks if you can, let schedules fire, and push a few real files through the workflows that handle them. Watch the execution log for failures, slow runs and anything that hits the new one-minute limit.

Write the cue sheet. Every surprise becomes a line: what failed, why, the fix, and whether the fix is done on 2.x already or has to happen during the cutover. That sheet is the production plan.

It helps to decide in advance what still has to work if the automations are off for an evening. If the cutover runs long, someone should know which orders to process by hand.

Opening night

With the rehearsal done, production is mostly scheduling. Pick a quiet window after n8n's stable release, not the beta, unless you have a reason. Take the full backup and confirm you can restore it, since that backup is your only way back. Upgrade, run the checks from your cue sheet, and keep the 2.x copy untouched for a week in case you need to compare.

Check one more thing while you're there: who can sign in and who owns the credentials. Rehearsals often reveal that every automation runs on one person's login, and a version upgrade is a good moment to fix that too.

If you'd like a partner to run the rehearsal, read the Migration Report with you and plan the cutover, that's part of our business automation work. Get in touch and tell us how many workflows you run.

Related work: Paddle8.