Zapier Alternative Self-Hosted: Migrate Zapier to n8n

Looking for a Zapier alternative you can self-host? For most Dutch and EU small businesses the realistic answer is n8n on a server you control. This guide shows how to migrate Zapier to n8n step by step, what it really costs (with public prices checked on 2 November 2026), and when you should stay on Zapier.

Zapier is a good product. It connects thousands of apps, it is easy to start, and someone else runs the servers. The problems show up later: the bill grows with every step your workflows run, your customer data passes through a US-based service, and the logic that runs your business lives in an account you rent.

n8n solves those three problems differently. It is a workflow tool with a visual editor, like Zapier, but the Community Edition can be installed on your own server. You pay for the server, not for each step. Your data stays where you put it. And the workflows are JSON files you can back up, version and move.

I build and run n8n workflows for small teams in the Netherlands and the EU, and I host my own on a server in Europe. This is the process I follow when a client asks to move off Zapier.

Who this migration is for

A move from Zapier to self-hosted n8n usually makes sense when at least two of these are true:

• Your Zapier bill is climbing. You moved up a task tier, or you hit pay-per-task overage more than once.
• Your workflows handle personal data. Leads, customer emails, invoices, HR forms. Under the GDPR you need to know where that data goes and who processes it.
• Your Zaps have become complex. Many steps, Paths, Code steps and Formatter chains that are hard to read and harder to debug.
• Someone can own a server. That can be an in-house person or a partner on a care plan. Self-hosting is not "set and forget".

If none of these apply and you run three simple two-step Zaps, stay where you are. Migration takes time, and time is also a cost.

What it costs: Zapier vs n8n, honestly

Prices change, so treat this as a snapshot. I checked both public pricing pages on 2 November 2026. Always confirm on the live pages before you decide: zapier.com/pricing and n8n.io/pricing.

How Zapier charges

Zapier bills by tasks. A task is one successful action step. Triggers and built-in tools like Filter, Formatter and Paths do not count, but every "create a row", "send an email" or "update a contact" does. At the time of checking, Zapier listed these self-serve prices in USD:

• Professional, 2,000 tasks/month: $49 per month billed annually, or $73.50 billed monthly.
• Professional, 10,000 tasks/month: $129 per month billed annually, or $193.50 billed monthly.
• Team, 2,000 tasks/month: $69 per month billed annually, or $103.50 billed monthly (up to 25 users).

When you go over your task limit, Zapier can keep running and bill extra tasks at an overage rate (2.5× the base rate on monthly plans, 1.25× on annual plans, according to the same page).

How n8n charges

n8n counts executions. One execution is one full run of a workflow, no matter how many steps it has. That difference matters. A Zap with one trigger and four actions that runs 500 times a month uses 2,000 Zapier tasks. The same workflow in n8n is 500 executions.

• n8n Community Edition (self-hosted): free to use under n8n's license. You pay for your own server and your time.
• n8n Cloud Starter: €20 per month billed annually. Pro: €50 per month billed annually. n8n says hosted data is stored in the EU, in Frankfurt.
• n8n Business (self-hosted): €667 per month billed annually, for companies that need SSO, Git version control and multiple environments. Most small teams do not need it.

The cost you do not see on either page

Self-hosting is not free. You need a small Linux server (most EU providers rent suitable machines for a modest monthly fee; check current prices with your provider), plus updates, backups and monitoring. If you do that yourself, it costs hours. If a partner does it, it costs a care plan.

So the honest comparison is: Zapier subscription versus server + maintenance + one-time migration. For a team paying for a few thousand tasks a month, the self-hosted side often wins within the first year. For a team on the free plan, it rarely does. If you want to model your whole software stack, not only automation, try the SaaS cost calculator.

The GDPR and EU hosting angle

For Dutch and EU businesses this is often the real reason to move, more than price.

• Data location. With self-hosted n8n, the workflow data, execution logs and stored credentials sit on a server you choose, for example in the Netherlands or Germany.
• Fewer processors. Every SaaS tool in a data flow is another processor you list in your records and privacy policy. Removing the middle layer simplifies that list. The apps you connect (your CRM, email or accounting tool) still process data, so you still need agreements with them.
• Retention control. You decide how long execution data is kept. In n8n you can turn off saving successful executions, or prune them after a set number of days.
• Access control. You decide who can log in, from where, and with which second factor.

Self-hosting does not make you GDPR compliant on its own. It gives you control, and control makes compliance easier to prove. Keep a short record of what each workflow does with personal data. It helps when a client or auditor asks.

How to migrate Zapier to n8n: step by step

There is no one-click import from Zapier to n8n. Zaps are rebuilt, not converted. The good news is that most Zaps are simpler than they look, and many get shorter in n8n.

Step 1: Inventory every Zap

Export a list of your Zaps and, for each one, write down: the trigger app and event, every action step, any Filter, Paths or Code step, how often it runs (Zap history shows this), and who depends on it. Mark the ones that touch personal data. Turn off and delete Zaps nobody uses. In my experience this step alone removes a surprising share of the bill.

Step 2: Group and prioritise

Sort the remaining Zaps into three groups: simple (trigger plus one or two actions), business-critical (leads, orders, invoices) and complex (Paths, loops, Code). Migrate a simple one first to learn the setup, then the critical ones, then the complex ones.

Step 3: Set up n8n properly

Install n8n with Docker on an EU server, behind a reverse proxy with HTTPS. Use PostgreSQL rather than the default SQLite for anything in production. Set an encryption key for credentials and store it safely; without it, you cannot restore credentials from a backup. Turn on two-factor login and keep the editor behind a strong password or a VPN. Set up automatic backups of the database and of exported workflows before you move anything important.

Step 4: Recreate credentials

Zapier does not export your app connections, and it should not. In n8n, create a credential for each app: OAuth for Google, Microsoft and most CRMs, API keys for others. Use a dedicated service account where the app allows it, so workflows do not break when an employee leaves.

Step 5: Rebuild each Zap as a workflow

Map Zapier concepts to n8n:

• Trigger → a trigger node for the app, a Schedule Trigger, or a Webhook node.
• Filter → an If or Filter node.
• Paths → a Switch node.
• Formatter → a Set (Edit Fields) node, or a small Code node.
• Code by Zapier → a Code node (JavaScript or Python).
• Webhooks by Zapier → the Webhook node to receive, the HTTP Request node to send.
• Delay → a Wait node.

Where n8n has no ready node for an app, the HTTP Request node can call the app's API directly. That is how most "missing integrations" are solved.

Step 6: Add error handling

Create one error workflow that sends you a message (email, Telegram or Slack) when any workflow fails, and attach it to every production workflow. Turn on retries for steps that call external APIs. This is where self-hosted setups usually beat what teams had on Zapier, because you see exactly which node failed and with which data.

Step 7: Run in parallel, then switch

For critical flows, run the n8n version next to the Zap for a few days with the final action pointed at a test sheet or test inbox. Compare results. When they match, switch the trigger (for example, change the webhook URL in your form), turn off the Zap, and watch the first real runs.

Step 8: Cancel and document

Once every Zap is off and has been quiet for a full billing cycle, downgrade or cancel Zapier. Export every n8n workflow to JSON and keep it in version control. Write one line per workflow: what it does, who owns it, what data it touches.

A real example: a website contact form

The contact form on this site runs on self-hosted n8n. The form posts to an n8n webhook. The workflow checks a honeypot field, validates the email, verifies a Cloudflare Turnstile token so bots are rejected, saves the lead to a sheet and sends me a Telegram message. In Zapier terms that is several premium steps per submission. In n8n it is one execution, on a server in Europe, and the workflow JSON sits in a backup I control.

When you should stay on Zapier

• You run only a few simple Zaps and stay within a low tier.
• Nobody, in-house or external, will maintain a server.
• You depend on a niche app that has a Zapier integration and no usable API.
• You need a vendor-run service with formal support for compliance reasons, and n8n Cloud or Enterprise does not fit.

A mixed setup is also fine: move the high-volume and data-sensitive workflows to n8n, and keep a small Zapier plan for one or two odd connectors.

If you are still choosing between tools — including Make — start with the comparison: n8n vs Make vs Zapier for small EU teams.

Need help with the move?

I plan and carry out Zapier to n8n migrations for small teams: inventory, EU server setup, rebuilding workflows, error alerts and handover. See n8n automation services and prices (starting from, excl. BTW), read how I work as an n8n consultant in the Netherlands, or, if you are in Gelderland, see automation in Apeldoorn. Not sure the numbers work? Start with the SaaS cost calculator.

Frequently asked questions

Can I import my Zaps into n8n automatically?

No. There is no official Zapier-to-n8n importer. Each Zap is rebuilt as an n8n workflow. Most simple Zaps take less than an hour to rebuild and test; complex ones with Paths and Code take longer.

Is self-hosted n8n really free?

The Community Edition has no license fee for use inside your own business. You still pay for a server, backups and maintenance time. Paid n8n plans add features such as SSO and Git-based environments.

Is n8n GDPR compliant?

No tool is compliant by itself. Self-hosted n8n lets you keep workflow data on an EU server you control and set your own retention, which makes GDPR compliance easier to achieve and document.

How is an n8n execution different from a Zapier task?

A Zapier task is one successful action step. An n8n execution is one full run of a workflow, however many steps it has. A five-step workflow that runs once is several tasks in Zapier and one execution in n8n.

How long does a Zapier to n8n migration take?

For a small business with 10 to 20 Zaps, plan on one to three weeks including server setup, rebuilding, parallel testing and switch-over. The inventory step often shrinks the list.