Migrations
Moving from Make to n8n
Teams usually make this move for self-hosting, code steps or cost at high volume. The scenarios rebuild cleanly if you plan the order.
Last reviewed 14 November 2026
Move from Make to n8n when you need workflows on your own infrastructure, when scenarios lean on custom code, or when credit use at high volume costs more than per-execution pricing. Rebuild each scenario as an n8n workflow, run both for a week or two, then deactivate the scenario. Stay on Make if a non-technical team edits the flows and nobody would own an n8n server.
Who this is for
Teams with high-volume Make scenarios, a developer or technical operations lead, and a reason to control where workflows run.
Signs it is time to move
- Credits run out before month end because of large iterators
- Scenarios rely on many custom JavaScript or HTTP workarounds
- Clients or auditors ask where data is processed
- You want workflows in version control alongside your code
What it costs on each side
Make counts credits per module run, so a scenario that loops over 500 rows uses credits for each row at each module. n8n Cloud counts one execution per workflow run, and self-hosted n8n has no per-run fee. For loop-heavy work the gap can be large.
| Item | Make | n8n |
|---|---|---|
| Entry pricing | Free plan with 1,000 credits a month; paid plan prices were not shown on the page when we checked | Starter, €20 a month billed annually for 2,500 workflow executions; a self-hosted edition is published on GitHub |
| What is counted | Credits per module run | Executions per workflow run |
| Self-hosting | Not offered | Yes |
Sources: Make pricing (checked 14 November 2026); n8n pricing (checked 14 November 2026). Vendor prices change, so check the live page before deciding.
The migration plan, step by step
- 01
Inventory
Export scenario blueprints and list each with its schedule, credit use and owner.
- 02
Map
Map Make modules to n8n nodes, routers to IF and Switch nodes, and iterators to n8n’s item handling, which loops by default.
- 03
Rebuild
Rebuild with error workflows and retry settings. Keep each workflow small enough that one person can read it.
- 04
Parallel run
Run n8n against a test destination while Make stays live and compare outputs.
- 05
Cut over
Move webhooks and schedules over one scenario at a time and turn the scenario off for 30 days before deleting it.
- 06
Monitor
Route failures to a named owner, review executions weekly, and lower the Make plan once the last scenario is off.
Risks and how we avoid them
| Risk | How we avoid it |
|---|---|
| Make’s item-by-item iterators behave differently from n8n’s batch handling, so totals come out wrong. | Compare counts and sums in the parallel run, scenario by scenario. |
| A self-hosted server with no owner. | Use n8n Cloud or put the instance under a care plan with backups and updates. |
| Data stores in Make holding state the flows depend on. | Export data stores first and move them to a table in Postgres or Supabase. |
What we do and what it costs
We start with the $500 audit, which lists every scenario and gives one fixed price for the move, credited to the build. Workflow builds start at $1.5k. For ongoing changes, the Automation team plan is $999 a month.
Questions
Can Make blueprints be imported into n8n?
Not directly. The blueprint JSON is a useful spec for the rebuild, and each scenario is rebuilt as an n8n workflow.
Where do Make data stores go?
Usually to a table in Postgres or Supabase that n8n reads and writes, which also makes the data easier to report on.
Will our team still be able to edit workflows?
Yes, n8n has a visual editor. It assumes a little more technical comfort than Make, so we hand over with a short training session and notes.
Related: Make, n8n, n8n vs Make vs Zapier, SmartSuite and Make automation, Supabase, Automate service, comparisons. All migrations.
We will tell you whether the move pays before you start
The audit lists what you run today, ranks it by cost and risk, and ends in one fixed price for the migration, credited to the build.
Book a discovery call
