Disclosure: some links in this article are affiliate links. If you buy through them, Sophrai may earn a commission at no extra cost to you. It never changes our rankings. Read our affiliate disclosure.
Short answer: there’s no one-click converter. You export your Zaps from Zapier as a reference, rebuild each one in n8n with the matching nodes, reconnect credentials, test with real sample data, and switch over one workflow at a time. This checklist walks through each step and the mapping from Zapier concepts to n8n nodes.
Why do teams migrate from Zapier to n8n?
Most teams move for cost and flexibility. Zapier bills every successful action step as a task, while n8n bills a full workflow run as one execution on Cloud and has no usage fee when self-hosted. Long, multi-step Zaps get expensive on Zapier; on n8n, extra steps don’t raise the bill.
Run your own numbers before you start: our free n8n Cost & Hosting Planner compares Zapier, Make, n8n Cloud and self-hosted n8n for your volume, and our cost breakdown shows the gap at 5k, 50k and 200k runs.
Can you import Zapier Zaps into n8n?
No, not as working workflows. Zapier exports Zaps as JSON in its own format, and n8n’s “Import from File” expects n8n workflow JSON. Treat the Zapier export as documentation: it lists each step and its inputs, which makes rebuilding faster and less error-prone.
Step 1: Inventory and export your Zaps
Export everything first, so you have a complete record even after you cancel Zapier. Zapier offers three exports, all under Settings > Security and data > Data management:
- Download my Zap workflows gives a JSON file of the Zaps you own (Zapier help). Account owners and super admins can export all users’ Zaps.
- Export my data emails a ZIP that includes
Zapfile.json, with the inputs and outputs of each step, plus links to your run history (Zapier help). - Zap History lets you download up to 5,000 runs at a time as CSV or JSON (Zapier help). Keep a sample of real runs for testing later.
Then build a simple inventory sheet with one row per Zap:
| Column | Why it matters |
|---|---|
| Zap name and owner | Who to ask when behaviour is unclear |
| Trigger app and event | Decides the n8n trigger node |
| Steps, paths, filters | Decides the n8n nodes and branches |
| Monthly task usage | Migrate expensive Zaps first |
| Webhook URLs used by other systems | Must be updated at cutover |
| Keep / merge / delete | Many teams find Zaps nobody uses |
Step 2: Map Zapier concepts to n8n nodes
Most Zapier building blocks have a direct n8n equivalent. Triggers become trigger nodes, actions become app nodes, Filters become an If node, Paths become a Switch (or If) node, Formatter becomes Edit Fields (Set) or a Code node, and Delay becomes a Wait node.
| Zapier | n8n |
|---|---|
| Trigger (app event) | App trigger node, or Webhook / Schedule Trigger |
| Action | App node, or HTTP Request for apps without a node |
| Filter | If node |
| Paths | Switch node (or several If nodes) |
| Formatter | Edit Fields (Set), Date & Time, or Code node |
| Delay | Wait node |
| Schedule by Zapier | Schedule Trigger |
| Webhooks by Zapier | Webhook node (receive) / HTTP Request (send) |
| Code by Zapier | Code node (JavaScript or Python) |
| Looping by Zapier | n8n processes item lists natively; Loop Over Items for batching |
One real difference: in n8n, a node runs once per incoming item by default. Where Zapier needed Looping, n8n often needs nothing extra. As one n8n community answer puts it, simple Zaps translate almost one-to-one, while Zaps with nested conditions take more work.
Step 3: Set up n8n and credentials
Decide where n8n will run before you rebuild anything: n8n Cloud or self-hosted. Then recreate each app connection as an n8n credential. Credentials never travel in workflow exports, so plan time to re-authorize every OAuth app.
- New to hosting? Compare options in n8n Cloud vs self-hosted.
- Self-hosting? Follow our Docker Compose guide and size the server with how much RAM n8n needs.
- Use separate credentials for testing where the app allows it, so test runs don’t touch live customer data.
Step 4: Rebuild, starting with the costliest Zaps
Rebuild in batches. Start with the two or three Zaps that use the most tasks, because they save the most money and teach you the patterns you’ll reuse. Merge related Zaps into one n8n workflow where it makes the logic clearer.
While rebuilding:
- Open the Zap’s steps from your export and recreate them node by node.
- Pin sample data from your exported Zap History so each node shows real fields.
- Add an Error Workflow so failures notify you instead of failing silently.
- Avoid deprecated nodes. If you follow older tutorials, check what n8n 3.0 removes, such as Function and Cron.
Step 5: Test and cut over without double runs
Test each workflow with sample data, then switch over one workflow at a time: turn the Zap off, publish the n8n workflow, and update any external webhook URLs. Never run both live on the same events, or leads and orders get processed twice.
n8n’s own migration advice (written for Cloud-to-self-hosted moves, but it applies here) lists the same checks: test each imported workflow before publishing, check sub-workflow and error-workflow references, update external webhook URLs, verify schedules and timezones, and coordinate the cutover so nothing runs twice (n8n Help Center).
Step 6: Monitor, then cancel Zapier
Watch executions for a full business cycle, at least a week, and compare outcomes with your old Zap History. Once every migrated workflow behaves, cancel or downgrade Zapier. Keep your exports archived in case you need to check how something used to work.
Zapier to n8n migration checklist
- Export Zap workflows, account data and a sample of Zap History.
- Build an inventory: trigger, steps, task usage, webhooks, keep/merge/delete.
- Choose n8n Cloud or self-hosted; set up backups if self-hosting.
- Recreate credentials; re-authorize OAuth apps.
- Rebuild the costliest Zaps first using the node mapping above.
- Add Error Workflows and test with real sample data.
- Cut over one workflow at a time; update webhook URLs.
- Monitor for a week, then cancel Zapier.
Frequently asked questions
Can n8n import Zapier Zaps directly?
Not as working workflows. Zapier exports Zaps as JSON (Zapfile.json), but that file uses Zapier’s own format, and n8n’s import expects n8n workflow JSON. Use the Zapier export as a reference and rebuild each Zap in n8n, then test it.
How do I export my Zaps from Zapier?
In Zapier, open Settings, then Security and data. In Data management, use Download my Zap workflows for a JSON file of your own Zaps, or Export my data for a ZIP that includes Zapfile.json. Account owners and super admins can export everyone’s Zaps.
What is the n8n equivalent of Zapier Paths and Filters?
Use the If node for a Filter-style yes/no check and the Switch node for Paths-style branching into several routes. Formatter steps usually become an Edit Fields (Set) node or a Code node.
How long does a Zapier to n8n migration take?
It depends on how many Zaps you have and how complex they are. Simple trigger-and-action Zaps are quick to rebuild; Zaps with many paths, formatters and custom code take longer. Migrate in batches, starting with the workflows that cost the most tasks.
Should I run Zapier and n8n at the same time during migration?
Yes, briefly, but never both live on the same events. Rebuild and test in n8n with test data, then turn the Zap off and publish the n8n workflow, so the same lead or order isn’t processed twice.
Sources
Zapier Help: Import and export Zap workflows; Zapier Help: Export your account data; Zapier Help: Export your Zap history; n8n Docs: Export and import; n8n Help Center: migrating workflows; n8n community thread. Read 26 October 2026. This is a documentation-based checklist, not a migration we ran for a client.
