How to Migrate Your Zapier Workflows to n8n in a Weekend

AI is moving fast and most people are falling behind. 

The Rundown AI keeps you ahead of the curve. 

It's a free AI newsletter that keeps you up-to-date on the latest AI news, and teaches you how to apply it in just 5 minutes a day.

Plus, complete the quiz after signing up and they’ll recommend the best AI tools, guides, and courses — tailored to your needs.

Sign up to start learning.

Most AI tools are a trade — your data for intelligence. Norton Neo breaks that deal. Powerful built-in AI, anti-fingerprinting, VPN, and ad blocking come standard. No setup. No add-ons. No compromises. Search, summarize, and write with AI that works inside your browser and stays there.

Browse Smarter, Stay Private

The hardest part of migrating from Zapier to n8n is not the technical rebuild — it's convincing yourself to start. The zaps are working, the business depends on them, and "if it ain't broke" is a very seductive argument when you're busy.

Here's the process that removes the fear. It runs in parallel with your existing Zapier setup, tests everything before you cut over, and gives you a rollback path at every step.

The migration node chain:

| Step | Tool | What it does |

|------|------|-------------|

| Audit | Zapier Dashboard | Export list of all active zaps with step counts |

| Triage | Spreadsheet | Classify by complexity and business criticality |

| Environment | VPS + Docker | Stand up n8n if not already running |

| Rebuild | n8n | Recreate each workflow, simple first |

| Test (shadow mode) | n8n + Zapier | Run both in parallel, compare outputs |

| Credential migration | n8n Settings | Move OAuth connections one app at a time |

| Cutover | Zapier | Disable zap after n8n version confirmed stable |

Step by step:

1. Audit your Zapier account

Export a full list from Zapier Dashboard → My Zaps → export. Classify each one: Simple (2–3 steps, no conditional logic), Medium (4–6 steps, some filtering), Complex (multi-path, custom code, delay steps). Start rebuilding Simple ones first — they're fast wins and they teach you n8n's patterns without pressure.

2. Set up n8n in shadow mode

Before rebuilding anything, configure n8n's output to write to a test table in Baserow rather than the real destination. A migration-mode toggle: when MIGRATION_MODE = true, all workflow outputs are redirected to the test table. You can verify output shape and data quality without touching production systems.

3. Credential mapping

Zapier credentials don't export — they're stored in their system and re-authorised per connection. In n8n, go to Settings → Credentials → New for each app you use. The good news: n8n uses standard OAuth flows for most major apps, so reconnecting Slack, Gmail, Sheets, and Notion takes 5 minutes each. Keep a credential mapping doc: Zapier connection name → n8n credential name.

4. Trigger equivalents

Most Zapier triggers map cleanly:

- Zapier "New row in Google Sheets" → n8n Google Sheets Trigger (poll mode)

- Zapier "Webhook" → n8n Webhook node (same concept, more control)

- Zapier "Schedule" → n8n Schedule Trigger with cron expression

- Zapier "New email in Gmail" → n8n Gmail Trigger

The one that's genuinely harder in n8n: Zapier's "New item in RSS feed" is simpler to configure than n8n's equivalent. You'll need a cron-triggered HTTP Request to the RSS URL and a Code node to parse it. Not difficult, just more nodes.

5. Shadow testing

Run both the Zapier zap and the n8n workflow for 7 days simultaneously. Compare outputs in your test Baserow table. If they match, you're ready to cut over. If they don't, you have a concrete diff to debug against.

6. Cutover

Disable the Zapier zap (don't delete it — keep it for 30 days as a fallback). Enable the n8n workflow. Monitor for 48 hours. If stable, delete the zap and reclaim that slice of your Zapier task budget.

Total weekend time for a typical 10-zap account: 6–8 hours including testing.

[Contabo](https://contabo.com) VPS — the boring, cheap infrastructure choice

You don't need a premium VPS for n8n. You need something reliable with enough RAM to run Docker Compose comfortably. Contabo's €6.99/month VPS handles n8n, Postgres, Redis, and Caddy without breaking a sweat at typical solo operator workloads.

Price: €6.99/month for 4 vCPU, 4GB RAM, 100GB NVMe SSD, unlimited traffic (fair use). The €12/month tier (8GB RAM) is worth it if you're running multiple resource-intensive workflows or storing significant execution history.

The honest tradeoff: Contabo's support is slow and their uptime SLA is 99.6% — below the 99.9% standard from premium providers like Hetzner or DigitalOcean. In practice, I've had two brief outages in 14 months, each under 20 minutes. For non-critical automation infrastructure, this is fine. If your workflows are revenue-critical (payment processing, client-facing automations with SLAs), pay the extra €5/month for Hetzner's better reliability and support response times. Contabo is for the budget-conscious operator who can tolerate occasional brief interruptions.

n8n's import tool is underrated — blog.n8n.io

You can import workflow JSON directly into n8n from the UI or via API. The GitHub Gists pattern — storing workflow JSON in a public Gist and importing from URL — is the cleanest way to share and version-control your automations. Start doing this from day one of your n8n setup.

OAuth token management across tools — oauth.net

Every migration involves reconnecting OAuth apps. The thing nobody tells you: OAuth tokens expire silently in many tools, and the workflow just fails without explanation. In n8n, test your credentials every 30 days. The built-in credential test button is there for a reason — use it.

The case for mono-VPS architecture — rachelbythebay.com

A persuasive argument for running everything (n8n, Baserow, Postgres, Redis) on one well-provisioned VPS rather than splitting across cloud services. Simpler networking, predictable costs, easier backups. This is exactly what I run. The counterargument — you have one point of failure — is valid but overstated for solo operators who aren't running revenue-critical systems with SLA requirements.