Zapier to n8n migration, with the saving worked out before anything moves.
A Zapier to n8n migration rebuilds each Zap as an n8n workflow, runs both side by side, then switches over. It saves money when Zaps run many actions: Zapier bills each action as a task, while n8n bills a whole run as one execution. With us, one simple Zap moves from $999, and a $1,000 audit prices anything bigger.
If your Zapier bill is small, staying is cheaper, and we will say so.
Updated 15 November 2026 · Zapier, n8n and server prices read on 15 November 2026, sources below
What a Zapier to n8n migration involves
Zaps do not convert into n8n workflows. n8n imports workflows in its own JSON format and describes no importer for Zaps[1], so each Zap that moves is rebuilt. Its apps are authorised again, its webhook senders get a new address, and old and new run side by side until their outputs match. The rebuild is also the moment to add the retries and failure alerts most Zaps never had.
Teams move for three reasons. The bill: Zapier counts a task for each action that completes[2], while n8n counts one execution per run of a whole workflow[3]. Data that has to stay on servers you control, since n8n can be self-hosted[4]. And logic that belongs in a JavaScript or Python Code node[5]. It does not pay for a handful of short Zaps, and the calculator shows which side of that line you are on.
What would n8n cost against your Zapier bill?
Enter last month’s Zapier tasks. The calculator finds the Zapier tier that covers them, turns them into n8n executions, prices n8n Cloud and a self-hosted server, and shows how long the gap takes to repay a migration. Nothing you type is stored or sent.
Last month's count from your Zapier account. The default is the worked example below.
Count the actions in a typical run. Triggers and Filter, Formatter or Paths steps use no tasks. Default 4 is a placeholder.
Only used to show which of our published prices would apply.
Default $12: DigitalOcean's Basic Droplet with 2 GiB of memory and 1 vCPU, as of 15 November 2026.
Monthly cost of 40,000 Zapier tasks, billed yearly
The 50,000-task tier, the smallest that covers 40,000 tasks. Billed monthly: $433.50 a month.
40,000 tasks at 4 a run is 10,000 runs, and each run is one execution. Pro with 10,000 executions, €600 a year.
The free Community edition, with no n8n licence fee, on the server cost you entered. Someone on your side updates it, backs it up and watches it.
n8n Cloud would cost about $234 a month less than Zapier, about $2,805 a year.
Self-hosted n8n would cost about $277 a month less, before anyone's time.
If all these tasks moved, the saving against n8n Cloud would repay a $999 quick win in about 4 months, the $2,500 pilot floor in about 11 months and the $15,000 programme floor in about 5.3 years, on the bill alone.
With 12 Zaps, the $1,000 audit says which to retire, keep or move, and fixes the price. One simple Zap can move as a quick win from $999, live in about a week; one larger workflow is a pilot at $2,500 to $6,000; three to six connected workflows are a programme at $15,000 to $50,000.
Get an estimaten8n counts executions, not tasks. An execution is one run of a whole workflow, however many steps it has, so the calculator divides your tasks by your tasks per run. That number is the estimate here: long Zaps and Zaps that loop gain the most, one-step Zaps gain the least, and Zaps that a Filter usually stops can cost more on n8n, because each trigger still counts as a run.
Prices read on 15 November 2026: Zapier pricing, n8n pricing, DigitalOcean Droplet pricing and the ECB euro reference rate. Euro prices are converted at $1.1052 to €1, the ECB rate for 13 November 2026. The server is an example: DigitalOcean's Basic Droplet with 2 GiB of memory and 1 vCPU, $12 a month.
Move one simple Zap from $999
Rebuilt in n8n and running in your own accounts, live in about a week. Send the Zap and your monthly task count for a fixed quote.
How tasks and executions change the comparison
Zapier counts the work inside a run. n8n counts the runs. That difference decides most of the saving, and it cuts both ways.
| A run that | Zapier tasks | n8n executions |
|---|---|---|
| Has one action | 1 | 1, so only the price per unit changes |
| Has eight actions | 8 | 1 |
| Loops over 50 line items, with two actions each | 100: each action counts for each item[2] | 1, however much data it handles[3] |
| Stops at a Filter before any action | 0[2] | 1, because the trigger fired[6] |
| Runs on a schedule every five minutes | None for the trigger; its actions count as usual | About 8,600 to 8,900 a month, even when there is nothing to do[3][6] |
So long Zaps and loops save the most, one-step Zaps the least, and Zaps that a Filter usually stops can cost more on n8n. A good rebuild uses a trigger node or a webhook whose Only Run If option drops unmatched requests before they become executions[7].
What the calculator assumes
- One Zap run is one execution: tasks divided by tasks per run, rounded up. That is the estimate. Sub-workflows, test runs and error workflows do not count[6].
- Zapier is the smallest published tier of your plan that covers your tasks, up to 2,000,000[2]. n8n Cloud stops at Pro with 50,000 executions; Business, from €667 a month billed yearly, is self-hosted only[3].
- n8n prices in euros, converted at the ECB rate for 13 November 2026, €1 to $1.1052[8].
- Self-hosted is the free Community edition[4] on a $12 DigitalOcean Basic Droplet with 2 GiB of memory[9], a basic shared CPU plan of the kind n8n says suits most usage[10]. Your time is not costed.
- Earn-back counts the bill only, as if every task moved.
The migration, step by step
One workflow at a time, and nothing is switched off until its replacement has run cleanly.
Audit every Zap
Its trigger, steps, monthly tasks, owner, and whether anyone would notice if it stopped. Each Zap is marked retire, keep on Zapier, or move.
Map triggers and steps
Each trigger gets an n8n trigger node, webhook or poll, and each Filter, Formatter or Paths step the nodes that replace it.
Rebuild
Each Zap that moves becomes an n8n workflow, with retries and error routing designed in rather than copied.
Run both side by side
Old and new run on the same inputs until the outputs match for a full cycle.
Cut over
One workflow at a time: re-point its webhooks, then pause the Zap rather than delete it until the new run has a clean week.
Monitor and hand over
An error workflow posts failures to your channel, and the runbook and workspace go to a named owner on your side.
Rather have us run these six steps?
For more than one simple Zap, step 01 is the $1,000 audit week, refunded against a pilot. If staying on Zapier is cheaper, the audit says so in writing.
What breaks or needs care
Most of a migration is ordinary rebuilding. These seven parts are not.
Apps without an n8n node
Formatter, Filter and Paths
- Why
- Built-in steps that use no Zapier tasks[2], so Zaps lean on them, and they do not map one to one.
Tables and Forms
- Why
- Zapier Tables hold up to 100,000 records on Professional[2]; n8n’s data tables share 200 MiB per instance by default[16]. Forms, renamed from Interfaces[17], do not carry over.
- What we do
- Small tables move to data tables, large ones to a database you own. Forms are rebuilt on the n8n Form Trigger[18].
Webhooks
- Why
- Senders keep posting to the Zapier URL, and n8n registers a production webhook only when the workflow is published[7].
- What we do
- Each sender gets its n8n production URL while the Zap still runs, with Basic, Header or JWT authentication on the new one.
Connections and sign-in
- Why
- With no importer for Zaps[1], connections cannot travel either.
- What we do
- Every app is authorised again by its owner, as a named service account where the app allows one.
Error handling
Who keeps a self-hosted instance running
- Why
- n8n recommends self-hosting for expert users, warns of data loss, security issues and downtime, and releases a new minor version most weeks[10].
- What we do
- A named owner for updates and backups before cutover. If there is no one, n8n Cloud is the honest answer.
When not to migrate
- The task volume is low, so the two bills are about the same
- Nobody can own a self-hosted instance, and n8n Cloud would not save money
- A Zap depends on an app with a Zapier integration, no n8n node and no API you can call
- Your team edits its own Zaps and has no one technical to take over n8n
At the small end, Zapier Professional with 750 tasks is $19.99 a month billed yearly, and n8n Cloud Starter with 2,500 executions is €20, about $22[2][3]. At 2,000 tasks Zapier is $49, and a gap of about $27 a month takes about 3.1 years to repay even a $999 quick win. If that is your account, stay on Zapier. The audit will say so in writing.
What a migration costs with us
One simple Zap moved and running in your own accounts, live in about a week.
One week. Lists every Zap, says which to retire, keep or move, and fixes the price. Refunded against a pilot.
One larger workflow moved: rebuilt, shadowed and cut over, in about three weeks.
Three to six connected workflows, moved in one plan with shared credentials, logging and alerts.
Optional, after handover: monitoring, alert triage and changes as your process changes.
The same prices as our AI automation service. Self-hosting n8n adds a small server and someone to patch it, and that running cost goes into the plan before you sign. The n8n plan or the server is in your name, and we charge no licence or platform fee. How we price.
Example: 12 Zaps and 40,000 tasks a month
An illustration, not a client: 12 Zaps on Zapier Professional, billed yearly, using 40,000 tasks a month at 4 tasks a run. It uses the calculator’s own prices[2][3][8] and maths, and the calculator opens on these numbers.
If every task moved, the n8n Cloud gap of about $234 a month, about $2,805 a year, would repay a $999 quick win in about 4 months, the $2,500 pilot floor in about 11 months and the $15,000 programme floor in about 5.3 years, on the bill alone. A quick win or a pilot moves one Zap, so it repays only that Zap’s share.
Two inputs move the answer most. On Zapier’s Team plan the same tasks cost $399 a month and the gap grows to about $344. At 3 tasks a run, the Zaps make 13,334 executions, which needs Pro with 50,000 at €1,450 a year, and the gap shrinks to about $155.
So here the bill alone is a slow reason to move every Zap. Moving the Zap that makes most of the tasks, or moving for data or logic, is the stronger case, and the audit week checks which.
Who does the work
Eazetech is an agentic AI studio in Lahore, Pakistan, founded by Babar Ali. We build on n8n, Make, Zapier and Beam AI, with approval steps on risky actions, and resell none of them, so the audit is free to say stay.
Babar Ali built the approval gates, run traces and MCP integration picker of Beam AI’s agent builder (full record). Our hours overlap EU hours and US East mornings.
Free download · PDF, 3 pages · no email needed
Zapier to n8n migration checklist
An audit worksheet with a row for every Zap, the step plan, when to keep a Zap on Zapier, and the seven parts that break or need care.
Download itQuestions about moving from Zapier to n8n
With us, one simple Zap can move as a quick win from $999, live in about a week. For more than that, the $1,000 audit week lists every Zap, says which to retire, keep or move, and is refunded against a pilot. One larger workflow is a pilot at $2,500 to $6,000 over about three weeks, and three to six connected workflows are a programme at $15,000 to $50,000. Support after handover is optional, from $1,500 a month.
Not directly. n8n's documentation covers importing workflows in n8n's own JSON format, from a file, a URL or the clipboard, and moving them between n8n instances. It describes no importer for Zaps, so each Zap is rebuilt as an n8n workflow. That rebuild is the migration, and the moment to add retries and error alerts.
At volume, usually. Zapier bills a task for each action that completes, while n8n bills one execution per workflow run, however many steps it has. At the small end they cost about the same: as of 15 November 2026, Zapier Professional starts at $19.99 a month billed yearly for 750 tasks, and n8n Cloud Starter at €20, also billed yearly, for 2,500 executions.
n8n Cloud, unless someone on your team runs servers. Self-hosting is free as the Community edition, but n8n recommends it for expert users, warns that mistakes can lead to data loss, security issues and downtime, and releases a new minor version most weeks. A self-hosted instance needs a named owner.
For one simple Zap moved as a quick win, about a week. For one larger workflow, about three weeks: a week to audit and map, a week to rebuild, and a week running both side by side until the outputs match. A programme takes longer, and the audit week fixes its plan and price first.
When the bill is small, when nobody can own an n8n instance, or when a Zap depends on an app with no n8n node and no API you can call. You can also move only some Zaps: the audit marks each one retire, keep on Zapier, or move, and says so in writing.
Sources
Every outside price, limit and rule on this page comes from these pages, all read on 15 November 2026. Our own prices are the ones on our pricing page.
- n8n Docs: Export and import. docs.n8n.io/build/manage-workflows/export-and-import
- Zapier: Plans and pricing, with the task tiers in the page's pricing data. zapier.com/pricing
- n8n: Plans and pricing, with the plan sizes in the page's pricing data. n8n.io/pricing/
- n8n Docs: Choose how to use n8n. docs.n8n.io/choose-how-to-use-n8n
- n8n Docs: Code node. docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.code
- n8n Docs: Understand executions. docs.n8n.io/build/understand-workflows/understand-executions
- n8n Docs: Webhook node. docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook
- European Central Bank: euro reference rate for the US dollar, 13 November 2026. www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/eurofxref-graph-usd.en.html
- DigitalOcean: Droplet pricing. www.digitalocean.com/pricing/droplets
- n8n Docs: Deploy to DigitalOcean. docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean
- n8n: Integrations. n8n.io/integrations/
- n8n Docs: HTTP Request node. docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest
- n8n Docs: Risks when using community nodes. docs.n8n.io/integrations/community-nodes/risks
- n8n Docs: Edit Fields (Set) node. docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set
- n8n Docs: Switch node. docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.switch
- n8n Docs: Data tables. docs.n8n.io/build/work-with-data/data-tables
- Zapier: Forms, with its FAQ on the rename from Interfaces. zapier.com/forms
- n8n Docs: n8n Form Trigger node. docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.formtrigger
- n8n Docs: Work with nodes. docs.n8n.io/build/understand-workflows/workflow-components/work-with-nodes
- n8n Docs: Handle errors gracefully. docs.n8n.io/build/flow-logic/handle-errors-gracefully
Keep reading
Want to know if your Zaps are worth moving?
Send your monthly task count and a list of your Zaps. We reply within one business day with a straight answer on whether the move pays, and what the audit week would cover.