Last checked October 29, 2026
Move from Make to n8n
We earn commissions when you shop through the links below.
There is no scenario import. Rebuild the flows that run, and read n8n's Sustainable Use License before you host it for other people.
How long: About an hour for a two-step scenario. Much longer for a scenario with branches.
Take it out
Step 1
List the scenarios that ran this month
Open the history. Write down the trigger, each module, and the filter. Ignore the experiments.
Step 2
Note the credit-heavy steps
Make says that since August 27, 2025, most steps are one credit and some AI steps use more. Since November 6, 2025, extra credits cost 25 percent more than plan credits. Those are the steps worth rebuilding first, because they are the bill.
Step 3
Collect the logins
You will reconnect every app. Webhook URLs will change. Tell the other system the new URL.
Put it in
Step 1
Install n8n or use n8n Cloud
Docker is the simple way to run it yourself. n8n Cloud is the option with no server. The Community Edition is free for your own workflows. The Sustainable Use License is not an open-source license. You cannot resell hosting.
Step 2
Rebuild the trigger, then each step
Confirm a real event arrives. Add one action at a time. A missing Make module becomes an HTTP node or stays on Make.
Step 3
Replay a known input
Use a record you understand and confirm it lands in the same place.
Need a server? DigitalOcean is one simple option. Railway is another.
We are a DigitalOcean affiliate.
We may earn from this Railway link.
What you lose
The scenario file
Nothing imports. The canvas is similar. The file is not.
History
Old Make runs stay in Make. n8n starts a new log.
The app list
Make's catalog is larger. Plan on a gap for the odd SaaS step.
Keep the Make scenario on until the n8n workflow has run once on live data. Then turn the scenario off. The license note matches the Zapier to n8n guide.
Related
https://ditchly.co/migrate/make-to-n8n