The short answer
- Moving from Make Core to n8n costs $1,316 more in the first year, after setup and upkeep time (Stackcut's model: modeled, not measured).
- n8n's community migration guide moves 1 partly; 2 things stay behind. What moves
- 4 public accounts of making this switch: 4 switched. Read them
- Switching help: n8n's official Make-vs-n8n comparison page closes with an offer of migration help: 'n8n's team can help migrate existing workflows to a more flexible, scalable platform.' No eligibility rules, scope, or pricing terms are stated on the page. n8n.io
What Make and n8n cost
List prices from each vendor's pricing page, as stored in the Stackcut catalog. Each price links its source.
| Plan | Billed monthly | Billed yearly (per month) | What you get |
|---|---|---|---|
| Make Core | $12/mo | not shown | 10,000 credits/mo; unlimited active scenarios; 1-minute interval |
| Make Pro | $21/mo | not shown | 10,000 credits/mo; priority execution, custom variables |
| Make Teams | $38/mo | not shown | 10,000 credits/mo; team roles and templates |
- Make free plan: 1,000 credits/month, 2 active scenarios, 15-minute minimum interval make.com
- n8n free plan: Self-hosted Community edition is free n8n.io
n8n's plans aren't in the Stackcut catalog yet; check n8n's own site.
Moving from Make to n8n
What n8n's importer carries over, what it leaves behind, and any help it offers switchers.
To n8n
Community guide migromat.com · Tools: migromat
Moves: Scenario structure: modules, routers, filters, schedules, iterators and field mappings (partial). migromat.com
Doesn't move: Connection credentials and API keys (Make's blueprint export excludes them); Steps with no n8n equivalent — these are flagged for manual work. migromat.com
Watch out for:
- Make's blueprint export contains no credentials or API keys migromat.com
- Output is a draft for review, not a finished migration — the converter flags steps needing a human migromat.com
- Only Zapier and Make.com sources are supported migromat.com
Community guide jservo.com · Tools: n8n self-hosted (Docker), Make blueprint export
Moves: Flow logic (triggers, modules, routers, filters, iterators) (partial). jservo.com
Doesn't move: Connection credentials; Webhook endpoints; Make 'bundles' processing semantics (n8n uses item arrays, which changes loop behavior). jservo.com
Watch out for:
- A forgotten webhook is the single most common cause of 'my automation stopped working' after migration jservo.com
- Make passes 'bundles' between modules while n8n passes item arrays, changing how loops behave jservo.com
- There is no one-click importer — every workflow is rebuilt by hand jservo.com
Switching help: n8n's official Make-vs-n8n comparison page closes with an offer of migration help: 'n8n's team can help migrate existing workflows to a more flexible, scalable platform.' No eligibility rules, scope, or pricing terms are stated on the page. n8n.io
From each destination's own migration docs and switching pages, plus community write-ups where no official guide exists, each checked against its page. Confirm terms on the linked page before you rely on an offer.
People who moved from Make to n8n
4 public accounts of leaving Make: 4 switched. Summaries are ours; each links the original, and each was checked against its page before it appeared here.
An individual poster says he switched from Make to n8n because code nodes plus Claude save hours every week; the same post pushes n8n's referral program and Hostinger hosting referrals to clients, so it doubles as affiliate marketing. LinkedIn
An HN commenter in the May 2025 n8n Show HN thread says they switched from Make to n8n because it is open source, runs locally without limits, and has JavaScript/Python code nodes; the one downside they flag is polling-based triggers versus Make's instant connectors. Hacker News
A developer's lessons-learned account of moving Make scenarios to n8n: audit by complexity, rebuild module-by-module, test in parallel, then add error handling and queue-based scaling; the author discloses Scalevise sells Make-to-n8n migrations. DEV Community
Agency case study: a ~60-employee B2B SaaS running ~40 Make scenarios (lead routing, onboarding emails, billing notifications, Slack alerts) consolidated into ~18 n8n workflows in the client's own cloud, with the agency claiming predictable costs and fewer silent failures in the first three months. Goodspeed
FAQ
Is n8n cheaper than Make?
Modeled, not measured: moving from Make Core to n8n costs $1,316 more in the first year, after setup and upkeep time at $50/hour. It depends on your plan, seats and usage. the math
Can I move my Make data to n8n?
n8n's community guide moves: Scenario structure: modules, routers, filters, schedules, iterators and field mappings. It doesn't move: Connection credentials and API keys (Make's blueprint export excludes them); Steps with no n8n equivalent — these are flagged for manual work. migromat.com
Does n8n help people switch from Make?
n8n's official Make-vs-n8n comparison page closes with an offer of migration help: 'n8n's team can help migrate existing workflows to a more flexible, scalable platform.' No eligibility rules, scope, or pricing terms are stated on the page. n8n.io
Keep reading
Check your own stack
Get your free stack audit
Stackcut finds every software subscription in your inbox and shows what to cancel, what to pay per use, and what AI can replace, with a spec and a cost for each. Your stack audit is free and takes about 2 minutes.
Or ask your agent
Connect the Stackcut MCP server (https://stackcut.io/mcp, no API key) and ask: “We pay for Make. Should we move to n8n?”
find_alternatives({"vendor": "Make"})