Hi all,
I built migrate-to-n8n, a free, MIT-licensed converter. You give it a Make blueprint or a Zapier export and get
an n8n workflow you can import, plus a report on every step.
Each step lands in one of three groups:
- converted: runs after import, you only reconnect credentials
- review: converted, with one named thing to check (a formula with no exact n8n twin, a sheet written by
column letter) - manual: no safe automatic equivalent. The step stays in place, disabled, with a sticky note on what to do,
so the workflow still imports and keeps its connections
It handles routers and filters, iterators and aggregators, Make error handlers, schedules, webhooks and
formulas. {{formatDate(1.date; "DD.MM.YYYY")}} becomes
{{ DateTime.fromISO(String($('Webhook').item.json.body.date)).toFormat('dd.LL.yyyy') }}.
Today 135 Make modules and 98 kinds of Zapier steps convert automatically; the full list is in the README.
I tested it on 1,432 public Make blueprints and 148 Zapier zaps from GitHub. 83% of Make steps and 71% of Zapier
steps convert or need one check, and none of the generated workflows fails the checks n8n runs on import.
The test suite also imports 347 workflows into real n8n 2.44 and 1.123 and runs some of them through their
webhooks to compare the answers with Make.
Try it with Node.js 22+:
npx migrate-to-n8n convert my-scenario.blueprint.json
It also runs as an MCP server (it is in the official MCP Registry), so you can ask Claude, Cursor or VS Code to
“convert this to n8n”, and it can upload the result to your n8n instance as an inactive workflow. Your files
never leave your computer.
GitHub: GitHub - kotiniiqq/migrate-to-n8n: Convert Make and Zapier automations into n8n workflows, with a report of what to check. MCP server + CLI. · GitHub
npm: https://www.npmjs.com/package/migrate-to-n8n
If a step of yours lands in “manual” and you think it should convert, open an issue with the module name.
That tells me which apps to add next.