Moving from n8n Cloud to self-hosted n8n in 2026: export, rebuild, and the break-even

Running n8n Cloud feels simple until the execution bill does not. The managed service removes servers, databases, and backups from your plate, and it charges for each workflow run. As volume grows, the tier ladder climbs, and a common question follows: can self-hosting n8n cost less? This guide answers that with documented facts, and it leaves the one number you must supply, your server price, to you.

You will get a map of what exports from Cloud, what must be rebuilt, the install paths the documentation supports, a cutover sequence, and a break-even test. It is written for operators who run workflows, not for developers who enjoy server administration. If you are still choosing a platform rather than a hosting model, see our n8n vs Zapier vs Make 2026 comparison and n8n vs Activepieces self-hosting breakdown.

When self-hosting n8n actually cuts your bill

Self-hosting cuts your bill when your execution volume pushes you past the Cloud tier you would otherwise buy. Self-hosting only wins if the server plus your maintenance time costs less than that tier. On the Starter or Pro plan, that is a tight comparison, so count your hours before you assume savings.

Per the n8n pricing page as fetched October 27, 2026, Starter is $20/mo billed annually with 2.5K workflow executions and 5 concurrent executions. Pro is $50/mo billed annually with 10K workflow executions and up to 50 concurrent executions. Business is 667€/mo billed annually with 40K executions, and the page lists it as self-hosted only, with a hosted version on a waitlist. Enterprise is a contact-sales plan.

Executions are counted per full workflow run. The pricing page FAQ says one execution is one run regardless of step count, so a forty-node workflow and a two-node workflow each consume one execution. Many small, frequent workflows are what fill a tier fastest.

What exports cleanly from n8n Cloud

Workflow definitions export as JSON. You can download a workflow from the Workflow menu, copy and paste nodes, or import from a URL or file, as the export and import docs describe. The docs recommend the n8n CLI for moving workflows between instances. Its package command builds portable .n8np bundles that can carry folders, projects, and references, but that feature is in Preview and may change, so keep your JSON exports as the fallback.

Exported JSON includes credential names and IDs. The docs do not say whether secrets travel with them, so treat credentials as something you recreate on the new instance. Names can also be sensitive: a credential called “Production payments key” tells a stranger something useful, so store export files carefully.

What you must rebuild by hand

Three things need manual work after a move. Credentials should be recreated on the new instance, the safe default given the docs above. Execution history does not come along: Cloud keeps logs for 7 days on Starter and 30 days on Pro, per the pricing page, so pull any records you need for audits before you cancel. Webhook URLs change when the host changes, which is a general consequence of moving servers rather than an n8n quirk.

Assistant is worth a note. The pricing page says self-hosted n8n includes Assistant in preview, with your own API key (BYOK) and no credit limits, so Assistant does not block a move. Insights history is plan-limited on Cloud: the page lists 7 days on Pro and nothing on Starter. This guide did not verify how Insights behaves on a self-hosted Business license, so check that before you cut over.

Data location also changes. Hosted-plan data is stored in the EU, in Frankfurt, while self-hosted data lives wherever you host it, per the pricing page. If data residency is part of the reason you are moving, confirm your new host meets the same requirement.

Choose an install path

Two practical paths exist. The one-line setup script installs n8n quickly and requires Docker on Linux or macOS, or WSL on Windows, per the one-line setup guide. Docker Compose is the route the install docs describe for production deployments with a database, per the Docker Compose guide. Do not choose npm for a new install; the installation docs say it is deprecated from n8n 3.0.

On databases, the default is SQLite and PostgreSQL is supported. MySQL and MariaDB are deprecated from n8n 1.0, per the database configuration docs. Our advice, not a documented requirement: for anything beyond testing, run Docker Compose with PostgreSQL.

Owning the server means owning uptime, updates, and backups. The keep n8n running guide covers that work, and our self-host n8n on a VPS with Docker guide goes deeper on the server side. Without a license key, a self-hosted instance runs as the free Community edition, and a Business or Enterprise license key enables those editions, according to the installation docs. For the redistribution terms, read our fair-code license explainer and the n8n GitHub repository.

Cutover, step by step

The sequence below exports first, builds the new instance, recreates credentials, imports, tests, and only then switches triggers. Steps 3 and 6 are operator advice, not documented requirements, and are labeled as such.

Export each workflow as JSON from the Cloud editor, and store the files in version control. (export docs)
Stand up the self-hosted instance with the one-line setup or Docker Compose, choosing PostgreSQL if you expect real volume. (one-line setup, Docker Compose)
Advice, not sourced fact: recreate every credential on the new instance, then run a test execution of each workflow before touching live triggers.
Import the workflows from file or URL, then re-point each webhook to the new host’s address. (export docs)
Switch the trigger URLs inside every external system that calls your webhooks.
Advice, not sourced fact: keep the Cloud account active until the new instance has completed your slowest schedule, whether that is daily, weekly, or monthly.

The break-even test

The cleanest test needs no hosting price from this guide. Your self-host cost per month is the server price plus your maintenance hours times your hourly rate. Self-hosting is cheaper than a given Cloud tier only when that total is below the tier’s monthly price.

Against the published tiers, the thresholds are fixed. Self-hosting beats Pro ($50/mo, billed annually) only if your server cost plus maintenance cost stays under $50 a month. It beats Starter ($20/mo, billed annually) only if the total stays under $20. Compare your own server quote and hours against those numbers, and count one-time cutover hours separately, amortized however your budget works. Business is 667€/mo billed annually and self-hosted only, so the Business comparison matters only if your volume exceeds Pro’s 10K executions.

When you should stay on Cloud

Stay on Cloud if your executions fit inside Starter or Pro, if nobody on your team can own server maintenance, or if managed updates matter more than cost. Spiky or unpredictable load is a reason to pause as well, because you would need to size and watch a server yourself. Overage fees on Starter and Pro are listed as capped on the pricing page, so Cloud’s cost ceiling is predictable within the tier you choose.

Self-hosting trades money for responsibility. For a team that already runs stable workflows, that trade often pays. For a team still finding its footing, the managed service is usually the cheaper choice once the hours are counted.

FAQ

Does n8n count every workflow step as a separate execution?

No. n8n counts one execution per full workflow run, regardless of how many steps the workflow contains, according to the n8n pricing page FAQ. A ten-node workflow and a two-node workflow each use one execution per run. That is why step-heavy workflows can be inexpensive on n8n Cloud, while frequent small triggers can fill a tier quickly.

Is self-hosted n8n actually free?

The software is free under the Community edition, which runs without a license key, per the installation docs. You still pay for the server, the storage, and your time for setup, updates, and backups. Treat the software as free and the infrastructure as your real cost.

How does n8n Cloud pricing compare with Zapier?

The meters differ. Zapier’s Free plan includes 100 tasks per month, Professional starts from $19.99/mo, and Team starts from $69/mo, with task usage varying by step and connector type, per the Zapier pricing page and the Zapier pricing rates page. n8n Cloud bills per full workflow execution. Compare your actual workflow shapes before deciding which tool is cheaper.

The Bottom Line

Moving from n8n Cloud to self-hosted n8n is a trade. Workflows export as JSON with moderate effort, while credentials, execution history, and webhook addresses need rebuilding. The decision itself is arithmetic: compare your server cost plus maintenance hours against the Cloud tier that covers your executions, and run that test before you start the migration.

How This Guide Was Built

This guide is based on official n8n documentation and pricing pages, fetched October 27, 2026. We did not run n8n Cloud or a self-hosted instance hands-on. Prices, plan limits, export behavior, install options, and database support come from the linked pages as they appeared on that date, including Business at 667€/mo billed annually and self-hosted only.

ToolBrain — tool reviews, LLM comparisons, and AI workflow guides

Cross-links automatically generated from NoCode Insider.