The n8n 3.0 timeline
These dates come from n8n's announcement and its support article on preparing for 3.0. The stable date is a plan, not a commitment, so check n8n's blog before you schedule anything.
| Date | What happens | What it means for you |
|---|---|---|
| October 27, 2026 | n8n 3.0.0 beta released, opt-in | Cloud users can pick "3.0.0 Beta (early access)" when changing version. Don't put production on it. |
| Early December 2026 | Stable 3.x planned | New features ship on 3.x only from then on. |
| December 31, 2026 | Support for n8n 1.x ends | There is no direct path from 1.x to 3.x. Move to 2.x first. |
| 12 months after 3.0 stable | 2.x security and critical fixes end | You don't have to jump on day one, but plan the move within the year. |
Why the n8n 3.0 upgrade needs a plan, not a click
n8n's own wording is that "moving to 3.x is one way." If something breaks after the upgrade, the way back is restoring the database backup you took before it, and losing whatever ran in between. For a workflow that only posts to Slack, that is an annoyance. For a sync that creates sales orders or invoices in an ERP, a few hours of failed or duplicated runs means reconciliation work.
The changes that hurt integration workflows most are the quiet ones. A removed node doesn't throw an error in the editor until someone opens the workflow. n8n's breaking-changes page says that published workflows containing removed nodes won't activate at startup, so their triggers stop. A nightly order sync built on a Cron node simply stops running, and nobody notices until the numbers don't match.
n8n 3.0 breaking changes, sorted by what they do to a running integration
The Migration Report groups findings into five impact levels: Upgrade blocked, Executions will fail, Executions might fail, Behavior changes and Capability removed. Here is where the changes that matter most for ERP, CRM and ecommerce syncs land, using n8n's breaking-changes list.
| Change in 3.0 | What happens to the workflow | Typical place it hides |
|---|---|---|
| Cron and Interval nodes removed | Published workflow won't activate; the schedule stops | Older polling syncs (orders, inventory, invoices). Replace with Schedule Trigger. |
| Function, Function Item and Item Lists removed | Executions fail | Workflows built before n8n 1.0. The report can convert them to Code nodes. |
$getPairedItem removed | Code that calls it fails | Mapping lines back to their source record. Use $('<node>').item, .itemMatching() or .pairedItem(). |
| Code node task timeout cut from 300 to 60 seconds | Long Code steps can now time out | Transforming large result sets in one Code step. Set N8N_RUNNERS_TASK_TIMEOUT explicitly if you need longer. |
| Execute Sub-workflow: Local File and URL sources removed | Parent workflow can't load the child | Shared "library" sub-workflows loaded from disk or a URL. Use Database or Define Below. |
| AI Agent version 1 removed | Old agent types stop working | SQL Agent, Conversational, OpenAI Functions, Plan and Execute and ReAct agents. Rebuild on the latest Tools Agent; use Postgres or MySQL tool sub-nodes for SQL. |
| Slack API credential needs a Signature Secret | Slack Trigger workflows stop receiving events | Approval and alerting workflows that react to Slack messages. |
| Unverified community packages off by default | Those nodes stop loading | Any npm community node that isn't on n8n's verified list. Set N8N_UNVERIFIED_PACKAGES_ENABLED=true only if you accept that risk. |
Larger SSRF block list (when it includes default) | HTTP calls to some private ranges are refused | Adds 100.64.0.0/10, among others. If internal systems are reached over addresses in that range, allow them with N8N_SSRF_ALLOWED_IP_RANGES or N8N_SSRF_ALLOWED_HOSTNAMES. |
| Gmail Trigger 1 to 1.3 runs as 1.4 | Behavior changes | Max 10 emails per poll by default (cap 50); sent and scheduled emails no longer trigger. Matters for inbox-to-ERP flows such as emailed purchase orders. |
The full list is longer. It also removes the OpenAI Assistant and legacy OpenAI nodes, several AI memory and vector-store nodes (including the Pinecone, Supabase and Zep Insert/Load nodes), HTML Extract, the binary-file nodes and Read PDF. Read n8n's v3.0 breaking changes page end to end; the report itself warns that it can't detect every change.
Self-hosted n8n 3.0: Docker or nothing
For self-hosted teams, the biggest change isn't a node. n8n 3.0 doesn't publish a runnable n8n package to npm, and installs with npm or npx n8n are no longer supported. If your instance runs from a global npm install on a VM, move it to Docker first, as its own change, and only then upgrade to 3.0. Existing Docker Compose setups don't need to change.
Three instance-level changes to check while you're there:
- Storage folder renamed.
~/.n8n/binaryDatabecomes~/.n8n/storageon first start, and n8n won't start if both folders exist. SetN8N_STORAGE_PATHif you want to keep the old path. - Encryption key rotation is on by default. Existing credentials stay readable and are re-encrypted on their next update. Keys are managed under Settings > Data Encryption Keys.
- Lower compression limits. The Compression node now stops at 256 MiB decompressed (was 2 GiB) and 1,000 zip entries (was 5,000). Large export files unzipped inside a workflow can hit this. Set the old values explicitly if you need them.
In queue mode, manual executions now always run on workers, and the OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS setting is gone. Tags can no longer be disabled, so tags you had hidden will reappear.
n8n Cloud and the 3.0 upgrade
On n8n Cloud you don't manage Docker, storage folders or environment variables, so the instance-level list mostly doesn't apply. The workflow-level changes do: removed nodes, the AI Agent version, $getPairedItem, the Slack signing secret and the Gmail Trigger behavior all affect Cloud workflows too. n8n's announcement doesn't say when Cloud instances will be moved to 3.x. Its support article says only that self-serve Cloud instances still on 1.x at the deadline will be upgraded to 2.x automatically. Run the Migration Report now rather than waiting to find out.
A six-step n8n 3.0 upgrade plan for integration workflows
- Check your version. Settings > Personal. On 1.x, upgrade to 2.x first. The Migration Report needs 2.39 or later.
- Run the Migration Report and read both tabs. "Workflow issues" covers nodes and code; "Instance issues" covers environment variables and deployment. An instance can need work even when every workflow is clean. Only owners and admins see the whole instance; other users see only the workflows they can edit.
- Fix the scheduled and money-moving workflows first. Anything that creates orders, invoices, payments or stock movements. Use the report's Migrate button where offered. It saves the fix as a new workflow version, so review the output before publishing it.
- Search your Code nodes. Look for
$getPairedItem,$evaluateExpressionand any step that ran longer than a minute in your execution history. - Back up, then rehearse. Take a full database backup. Restore it to a staging instance, upgrade that copy to 3.0, and replay a day of real inputs. Compare record counts with what production created.
- Upgrade in a quiet window and watch the first runs. Confirm every scheduled workflow activated, and check your error workflow is still catching failures. Our n8n error handling guide covers how to set that up.
The n8n-nodes-netsuite-rest community node we maintain is a verified community node, so the new default that disables unverified packages doesn't stop it loading. NetSuite workflows built on older patterns still need the checks above, especially Code steps that page through large SuiteQL results. Our NetSuite pagination guide shows how to keep each step small.
Should you wait for n8n 3.0 stable?
For production, yes. The beta is opt-in, and n8n says 2.x keeps security and critical fixes for 12 months after 3.0 goes stable. Use the time between now and December to run the Migration Report, clear the findings and rehearse on staging, so that upgrading becomes a planned maintenance window rather than a surprise. The one hard deadline is for 1.x: support ends December 31, 2026, and there's no direct route from 1.x to 3.x.
Frequently Asked Questions
When is n8n 3.0 released? n8n released the 3.0.0 beta on October 27, 2026. The stable release is planned for early December 2026, according to n8n's announcement and support article.
Can I roll back from n8n 3.0 to 2.x? No. n8n states that moving to 3.x is one way and there is no direct rollback to 2.x. Going back means restoring a full backup taken before the upgrade, so take one and test the upgrade on a staging instance first.
Which nodes are removed in n8n 3.0? Among others: Function, Function Item, Item Lists, Cron, Interval, HTML Extract, Read PDF, the binary-file nodes, the legacy OpenAI and OpenAI Assistant nodes, several AI memory and vector-store nodes, and version 1 of the AI Agent. Most have a listed replacement, such as the Code node and Schedule Trigger.
How do I check if my workflows will break in n8n 3.0? Open Settings > Migration Report on n8n 2.39 or later. It lists affected workflows and instance settings by impact level, and can migrate some nodes automatically. It can't catch everything, so also read n8n's breaking-changes page.
Can I still install n8n with npm in 3.0? No. n8n 3.0 requires Docker for self-hosting and doesn't publish a runnable n8n package to npm. Move npm or npx installs to Docker before upgrading.
How long is n8n 2.x supported? After 3.0 becomes stable, 2.x receives security and critical bug fixes for 12 months. Support for 1.x ends on December 31, 2026.
Sources
- Introducing n8n 3.0 (n8n blog, October 27, 2026)
- v3.0 breaking changes (n8n docs)
- v3.0 migration tool (n8n docs)
- How do I prepare for n8n 3.0? (n8n support, updated October 26, 2026)
All checked November 2, 2026. 3.0 is in beta, so details can change before the stable release; we'll update this page when it ships.
Want a second pair of eyes on the upgrade?
Entech Solutions has built production workflows on n8n for over two years, including NetSuite, CRM and AI-agent integrations. We can review your Migration Report, fix the flagged workflows and rehearse the upgrade on staging with you. See our n8n automation services or get in touch.