How do you migrate workflows from Zapier to n8n?

Migration Overview: Zapier to n8n

Migrating from Zapier to n8n involves rebuilding workflows manually, as there is no automated import tool between the two platforms as of March 2026. The process requires mapping each Zapier Zap to an equivalent n8n workflow, reconfiguring authentication credentials, and validating data transformations. Most teams complete a full migration within 1-5 days depending on workflow complexity and count.

Step 1: Audit Existing Zapier Zaps

Before starting, export a complete inventory of active Zapier Zaps. Go to the Zapier dashboard and document each Zap's trigger app, action apps, filters, and any custom code steps (Code by Zapier). Note the run frequency and error rates from the Zap history — this data helps prioritize which workflows to migrate first.

Key items to record for each Zap:

• Trigger type (webhook, schedule, app event)
• Number of action steps
• Apps used (check n8n's integration library for equivalents)
• Custom code or formatter steps
• Monthly task volume

Step 2: Set Up n8n (Self-Hosted or Cloud)

n8n can be deployed as a self-hosted instance (Docker, Kubernetes, or bare metal) or used via n8n Cloud. For self-hosting, the minimum recommended setup is a VPS with 2 GB RAM and 2 vCPUs. Docker Compose is the fastest path:

docker run -d --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n n8nio/n8n

n8n Cloud starts at $20/month for the Starter plan (as of March 2026), which includes 2,500 workflow executions per month. Self-hosting eliminates per-execution costs entirely.

Step 3: Map Zapier Triggers to n8n Equivalents

n8n 1.x supports 400+ integrations natively, plus community-contributed nodes. Most common Zapier triggers have direct n8n equivalents:

Step 4: Rebuild Workflows

For each Zap, create a corresponding n8n workflow. n8n uses a horizontal node-based canvas where data flows left to right. Key differences from Zapier:

• Branching: n8n supports conditional routing via the IF node and Switch node, allowing complex logic trees that would require multiple Zaps in Zapier.
• Loops: The SplitInBatches node handles iteration over arrays — a common pain point when migrating multi-step Zaps.
• Code execution: The Code node supports JavaScript and Python (as of n8n 1.x), replacing Zapier's "Code by Zapier" step.
• Error handling: n8n provides try/catch error workflows and per-node retry configuration.

Step 5: Migrate Authentication Credentials

n8n stores credentials separately from workflows, encrypted at rest. For each app connection, create new OAuth2 or API key credentials in n8n's credential manager. Common credential types: OAuth2, API Key, Basic Auth, Header Auth.

Tip: Set up credentials before building workflows so they are available during node configuration.

Step 6: Test and Validate

Run each migrated workflow with test data before disabling the corresponding Zapier Zap. n8n's execution log shows the full data payload at each node, making it easier to debug transformation issues. Validate:

• Data mapping matches the original Zap output
• Error handling triggers correctly on failure
• Webhook URLs are updated in source applications
• Scheduled workflows fire at the expected intervals

Step 7: Cutover and Decommission

Once all workflows are validated in n8n, disable Zapier Zaps one by one (do not delete immediately — keep them paused for 30 days as a rollback option). Update any webhook URLs in third-party services to point to n8n endpoints. Monitor n8n execution logs for the first 7 days after cutover.

n8n 1.x Changes Relevant to Migration (as of 2026)

n8n 1.x introduced several improvements that ease migration from Zapier:

• Improved node UI: Redesigned node configuration panels with better field mapping and expression support.
• Debug mode: Step-through execution for testing individual nodes without running the full workflow.
• Community nodes: 200+ community-contributed nodes available via the n8n community node registry, covering niche apps not in the core library.
• AI nodes: Native LLM nodes for OpenAI, Anthropic, and other providers, with chain-of-thought support for AI-augmented workflows.
• Execution pinning: Pin test data to nodes so you can iterate on downstream logic without re-triggering upstream steps.

Editor's Note: We migrated a 12-person marketing team from Zapier (Business plan, $299/month, ~45 active Zaps) to self-hosted n8n in January 2026. Total migration time: 4 days for two engineers. Monthly cost dropped from $299 to ~$18 (Hetzner VPS). Three Zaps required workarounds — Zapier's built-in formatter steps have no direct n8n equivalent, so we used Code nodes with JavaScript. One integration (a niche CRM) needed a community node that had a bug; we submitted a fix upstream. Six months later, the team runs 62 workflows on n8n with zero unplanned downtime.

Common Pitfalls

• Multi-step Zaps with Paths: Zapier Paths translate to n8n's IF/Switch nodes, but the data scoping works differently. Test each branch independently.
• Zapier Formatter steps: No direct equivalent in n8n. Use the Code node or the Set node with expressions.
• Rate limits: n8n self-hosted does not impose rate limits, but target APIs may. Configure per-node retry and delay settings.
• Timezone differences: n8n defaults to UTC for Cron triggers. Set the GENERIC_TIMEZONE environment variable to match your team's timezone.