How to migrate from Zapier to Make
People move from Zapier to Make for one reason: far more automation volume per dollar. But there's no magic importer — you rebuild your workflows by hand. Here's how to do it without breaking things, the concept mapping you need, and the honest truth about the pricing that makes the units tricky to compare.
Prices checked Aug 2026 (annual billing) — confirm on both vendors' pricing pages. We earn a commission on Make and nothing on Zapier; the pricing math below is the actual reason to switch, not the disclosure.
First: there's no auto-importer
Set expectations up front — you can't export your Zaps and import them into Make. Migration is a manual rebuild, scenario by scenario. That's not as bad as it sounds if you go in order, and it's a good chance to prune the Zaps you no longer need.
The migration, step by step
- 1. Inventory every Zap — trigger, each action, filters, paths, Formatter steps, and its monthly task volume. This list is your migration plan.
- 2. Map the concepts to their Make equivalents (table below).
- 3. Rebuild one scenario at a time in Make's visual editor, re-authorising each app connection as you go.
- 4. Test each scenario with real data before you switch on its schedule.
- 5. Run both in parallel for a while, compare the outputs, then cut over and turn the Zap off.
Zapier → Make concept map
| Zapier | Make | Note |
|---|---|---|
| Zap | Scenario | The whole workflow |
| Trigger / Action step | Module | Each node in the flow |
| Task (billing unit) | Operation (metered as a "credit") | 1 module run ≈ 1 credit |
| Paths (branching) | Router | The router itself is free |
| Filter | Filter (between modules) | Free in both |
| Formatter | Built-in functions + Tools modules | No extra charge |
The pricing truth (read this before you estimate)
Zapier bills per task — each successful action. Triggers, and its Filter, Paths, Formatter and Delay tools, don't count. Entry: ~$19.99/mo (annual) for 750 tasks; free tier 100 tasks.
Make bills per operation (a module run, now metered as "credits") — and the meter runs faster than it looks: the trigger, every action module, and each pass of an Iterator all consume one. A Router and a Filter don't. Entry: ~$9/mo (annual) for 10,000 operations; free tier 1,000.
So Make's headline is far cheaper per unit, but a workflow that's "1 task" in Zapier can be several operations in Make. The honest way to compare: take your monthly Make estimate and multiply by your average modules per workflow — don't line up 750 tasks against 10,000 operations as if they're the same thing. Even after that adjustment, Make usually wins on volume-per-dollar, which is why it's worth the rebuild.
Gotchas that catch people
- · Re-authenticate everything. Connections don't transfer — you re-authorise every app (OAuth / API key) in Make from scratch.
- · Re-point your webhooks. Instant/webhook triggers get new Make URLs; update them at the source app.
- · Error handling is manual. Zapier auto-holds and replays failed tasks and emails you; in Make you build error handlers onto modules (they're free, but not automatic).
- · Watch the operations count. Iterators and per-item processing each cost an operation — aggregate where you can, or budgets blow past the estimate.
When not to bother
Stay on Zapier if a critical app has no Make module (verify first — the coverage gap is real), or if your volume is tiny enough to sit inside Zapier's free 100 tasks. The rebuild only pays off when your task volume is high enough that Make's per-operation pricing genuinely saves you money.
Frequently asked
Is there a tool that imports Zapier Zaps into Make?
No. There's no official one-click importer — migration is a manual rebuild, scenario by scenario. A few third-party services claim to help, but they're either paid human-rebuild agencies or tools that convert to a different platform (n8n), not a true Zapier-to-Make converter. Plan for a hands-on rebuild.
Is Make actually cheaper than Zapier?
Per unit, dramatically — Make's Core plan is ~$9/mo (annual) for 10,000 operations vs Zapier's ~$19.99/mo for 750 tasks. But the units aren't equal: a single Zapier 'task' (one action) often equals several Make 'operations' (each module run, including iterator passes, counts). Estimate honestly by multiplying your Make figure by your average modules per workflow — don't compare 750 to 10,000 directly.
Will all my apps be available on Make?
Not necessarily. Zapier's app catalogue is roughly three times larger than Make's, so a niche or older integration you rely on may not exist on Make (Make counters with more actions per app it does support). Check every app you use before you commit — a missing integration is the one thing that can block the whole migration.
Related
Some links here are affiliate links — we earn a commission on Make, at no extra cost to you, and it never changes the recommendation. See our Affiliate Disclosure.