Back Office BeatSubscribe

Published by J9 Systems. What's new in business tech, and what it means for yours.

From the brief of Wednesday, October 28, 2026 · No. 15

From the daily brief · Automation

n8n 3.0 beta out Oct. 27 with breaking changes; stable release due early December

If job syncs, reminders or invoice flows run through n8n, the 3.0 upgrade can break them, and there is no rollback without a backup.

By Carter Josephson · · 2 min read

What happened

n8n released version 3.0.0 beta on Oct. 27, 2026, a breaking-changes release that removes legacy nodes such as Function, Cron and the legacy OpenAI node, tightens security defaults and ends npm installs for self-hosting in favour of Docker, with the stable release due in early December. Upgrading is one-way with no rollback, 2.x gets security and critical fixes for 12 months after the stable release, and support for 1.x ends Dec. 31, 2026.

What it means for a 10-to-50-person business

If nobody in your business uses n8n, ignore this. If you do, self-hosted or on n8n Cloud, 3.0 can break workflows that run fine today. Example: a 25-person plumbing company has 12 n8n workflows a contractor built two years ago (assumed). One copies finished jobs into the accounting system, one sends review requests on a Cron node, one cleans customer data in a Function node. In 3.0, Cron and Function are removed. Many migrate automatically to Schedule Trigger and the Code node, but not all. Any Code step that runs longer than 1 minute now times out, down from 5 minutes. If that n8n was installed with npm on a small server (assumed), it also has to move to Docker. The Migration Report (Settings > Migration Report, version 2.39 or later) lists what breaks, fixes much of it, and keeps published workflows running on v2 while you review. The announcement mentions no price change. The real risk is someone clicking upgrade and invoices quietly stopping syncing, with no way back except a backup.

What to do
Try it

Before December, update n8n to the latest 2.x, open Settings > Migration Report, fix or mark "won't fix" everything it flags, and do not move production to the beta.

What it costs
What it costs
n8n subscription change
$0 (none announced)
Update to latest 2.x and run Migration Report, assume 12 workflows
1–2 hrs (≈ $100 at $50/hr)
Manual fixes, assume 4 workflows not auto-fixed
2–4 hrs (≈ $200 at $50/hr)
Move self-hosted npm install to Docker, if applicable
3–6 hrs (≈ $300 at $50/hr), assumption
Full backup and test on staging before upgrade
1 hr (≈ $50 at $50/hr)
Doing nothing
$0 now; 2.x fixes end about 12 months after the December stable release, and 1.x support ends Dec. 31, 2026
Sources
blog.n8n.io (primary) · n8n 3.0 breaking changes (docs) · n8n v3 Migration Tool docs · Announcing n8n version 3.0 (community forum thread)

Questions owners ask

Do I have to upgrade to 3.0 in December?

No. After the stable release, 2.x keeps getting security and critical bug fixes for 12 months. New features ship on 3.x only.

We are still on n8n 1.x. What now?

Upgrade to 2.x first. There is no direct path from 1.x to 3.x, and n8n ends 1.x support on Dec. 31, 2026.

Will we lose credentials or run history?

n8n says credentials and execution history carry over and the upgrade needs only a short restart. Rolling back means restoring a full backup.

Three to five of these, every weekday morning.

Related