How to migrate from Zapier to n8n
People leave Zapier for one of two reasons: the bill grew faster than the value, or customer data must not sit in a vendor cloud. Here is how to move without downtime.
Step 0. Check whether it is worth it
| Zapier | n8n self-hosted | |
|---|---|---|
| You pay for | tasks | the server |
| 10,000 operations/month | mid-tier plan | €5–20 VPS |
| 10× growth | bill scales with it | bill barely moves |
| Migration cost | — | one-off, about a week |
Below roughly €40–50 per month, do not bother: the migration costs more than a year of savings.
Step 1. Inventory
List every zap: what it does, how often it fires, which apps it touches. Typically a third turn out to be dead — written for a process that no longer exists. Those get switched off, not migrated.
Step 2. Stand up n8n
A €5 VPS, a domain and HTTPS — webhooks will not work without a secure endpoint — plus backups of the n8n database, which holds your workflows and credentials. That is our n8n setup service.
Step 3. Move one at a time
The rule: never switch off the old zap until the new workflow has run on real data.
- Rebuild the chain in n8n, node for node.
- Run on test data and compare against Zapier output.
- Run both in parallel for a day or two — duplicates in the CRM are expected and cleaned afterwards.
- Confirm no discrepancies, then disable the zap.
Start with a simple workflow, not the critical one: the first migration always surfaces details like date formats or the server timezone.
Traps worth knowing in advance
- Server timezone. Schedules fire at the wrong hour unless you set it explicitly.
- API rate limits. Zapier smoothed request rates for you; in n8n bulk runs need deliberate pauses.
- Silent failures. The classic beginner mistake is skipping error alerts. The workflow dies, nobody notices, leads disappear. Wire up a Telegram alert from day one.
- Updates are yours now. Every couple of months is a healthy rhythm.
Timelines
One simple workflow: a day. Ten production chains: about a week including tests and parallel running.
FAQ
Is there an automatic importer?
No — the node models differ. Logic is rebuilt by hand, which is not wasted effort: half the workflows get simpler on the way.
What about apps n8n has no node for?
Connect over HTTP to their API — the generic node does whatever the service supports. With no API at all, that scenario stays in Zapier.
Who owns the new workflows?
You do. They export to JSON and run on any server.
Send us your invoice and workflow list and we will quote the migration. Full service: n8n automation agency.
Read next
Self-hosted n8n: Docker setup and maintenance
What to prepare before installing, running n8n in Docker with PostgreSQL, HTTPS and webhooks, the encryption key, backups, updates and first-month mistakes.
How to choose an automation contractor
Seven questions to ask before signing, three signs of vendor lock-in, and what a serious proposal actually looks like.
Warehouse and marketplace automation: where to start
Step by step: one source of truth for stock, orders from every channel, shipping and tracking numbers. What takes a week and what needs an accounting system.