No native importer moves workflows between n8n and Make; scenarios are rebuilt by hand.
At the cloud entry tier, yes: Make's Core is $12/mo for 10,000 credits against n8n Starter's $20/mo for 2,500 executions, but not if you were running n8n's free self-hosted edition.
The catch is the billing unit. n8n counts a full run as one execution, while Make bills credits for the actions inside each scenario, so a ten-step workflow that runs often burns credits much faster than the headline suggests. Pull a month of run counts for your busiest workflows before you pick a plan, and cut steps that only reshuffle data. Rebuild error handling on purpose too, since every scenario is rebuilt by hand, and a flow with no failure alert can sit broken for weeks before anyone notices. If your team is non-technical and the self-hosted server was a chore, Make's no-code builder is worth the trade.
My read of the verified data on this page, checked against vendor sources on September 23, 2026. Disagree or spot an error? Tell Bill
Most buyers only budget for the new subscription. This estimates the hidden labor, data-cleanup, and retraining cost of actually making the switch.
Estimate assumes: 1 hour of data-mapping/cleaning labor per 2,000 records, a blended $75/hr ops rate, tiered migration & cleaning tooling fees, and 4 hours of retraining per seat at a $45/hr fully-loaded rate.
$12/mo against $20/mo.
Built for business users, not just developers.
A larger library than n8n’s cloud tiers.
You lose n8n’s free self-hosted option and its execution-based (not per-step) billing — Make has no self-hosted tier at all.
| Step | What you do |
|---|---|
| 1Export your data | Export scenarios/workflows, documents/templates, or tickets/contacts as applicable from the old tool. |
| 2Create your Make account (Core plan) | Create your Make account (Core plan) and rebuild your first scenario using its visual builder. |
| 3Rebuild your scenarios | Recreate each workflow as a Make scenario using its visual builder. |
| 4Reconnect integrations | Reconnect any apps, channels or connectors the new tool needs. |
| 5Test with a real workflow before rolling out | Run one real case through the new tool end to end. |
| 6Cancel the old plan | Once the new tool is handling real work cleanly, cancel the old subscription. |
What this path doesn’t do for you:
n8n’s free self-hosted Community Edition and code-step flexibility have no Make equivalent — Make runs cloud-only.
| Plan | n8n | Make |
|---|---|---|
| Pricing basis | Full executions | Credits per action |
| Entry price | Starter $20/mo (2,500 executions) | Core $12/mo (10,000 credits) |
| Self-hosting | Free, open-source Community Edition | Not offered |
| Audience | Technical/developer teams | No-code, business users |
Standard list prices checked on each vendor’s pricing page on September 23, 2026.
| Capability | n8n | Make |
|---|---|---|
| Self-hosting | Free, open-source | Not offered |
| Billing | Full executions | Credits per action |
| Price | $20/mo (2,500 executions) | $12/mo (10,000 credits) |
Going the other direction, or want the full comparison first?
Read the Make vs n8n comparison Switching from Make to n8n instead?Security, offline and access rules that differ between n8n and Make. Rows where both tools are the same (4) are left out; the full side-by-side is on each tool’s page: n8n, Make.
| What changes | n8n (today) | Make (after) |
|---|---|---|
| ISO/IEC 27001 | Not published | Certifiedsource |
| Two-factor authentication | Yessource | YesEnforcement: Enterprisesource |
| Admin audit log | YesEnterprise (log streaming to your own tools)source | YesEnterprisesource |
| Data residency choices | EUsource | US, EUsource |
| Encryption | Cloud: AES-256 at rest (Azure server-side encryption, FIPS 140-2); traffic encrypted in transitsource | AES-256 full-disk encryption at rest (AWS KMS keys); TLS 1.2/1.3 in transitsource |
| Self-hosting option | Yessource | Not published |
| Mobile apps | Not published | iOS, Androidsource |
No. n8n saves each workflow as a JSON file (Workflow menu → Download), but Make has no importer for that format, so you rebuild each scenario by hand in Make’s visual builder, using the exported file as your reference.
On Make’s cloud plan, yes at entry — but you lose n8n’s free self-hosted option if you were using it.
Generally, yes, for non-technical users — it is built as a no-code, business-user-first tool.
No native importer exists between Make and n8n; workflows are rebuilt by hand in the new tool’s builder, or via a third-party conversion service.
Every pricing fact, rating, AI billing model and switching guide we hold on each tool, on one page, with the date each figure was last verified.
Prices on this page were recorded from each vendor’s own pricing page on the date shown at the top of the page. Vendors change pricing often — check the live source before you buy.
Every figure is also in our open dataset (JSON and CSV, CC BY 4.0), with its source page and verification date. See how we research pricing.
Cite this page: HelpCompare, “Switching from n8n to Make”, helpcompare.com/n8n-to-make-migration/ (updated ).
Source links on this site are checked every month; last check . How sources are checked.
Plain-language guides: the steps, what to check before you buy, common mistakes, and every tool it takes with verified prices.
Verified prices costed for your team size, a check against your must-have requirements, the questions to settle before you sign, and a source for every figure. Print it, or paste it into an email to whoever approves the spend.
Built for the leader who owns the selection, answers for the spend, drives the rollout, and lives with the results. HelpCompare covers the whole decision, not just the first step.