Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want to move my Make scenarios to n8n

Short answer

Make scenarios are rebuilt as n8n workflows, not imported, so the first job is an inventory of every scenario, its connections and what depends on it. n8n can be self-hosted, which adds a server to look after. Move one scenario at a time and keep the old one running until results match.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Make credits are running out and I was told to try n8n.
  • I have many scenarios and no list.
  • I use iterators and aggregators and wonder how they translate.
  • I am unsure whether to self-host.
  • I worry that orders will stop during the move.

Why does this happen?

  1. Scenarios are rebuilt

    Make and n8n are separate products with their own modules and settings, so each scenario is recreated as a workflow and tested on its own.

  2. Make's stored runs and error settings are duties to replace

    Make can store failed runs as incomplete executions and pause the scenario. After the move, that safety net has to be rebuilt in the new tool on purpose.

  3. Iterator and aggregator logic needs care

    In Make, outputs between an iterator and an aggregator are not available after the aggregator. A scenario built around that structure has to be understood before it is redrawn.

  4. Webhook addresses change and n8n hosting is yours

    n8n separates test and production webhook URLs, with the production one registered when you publish. Self-hosting means looking after the server.

What can I do about it today?

  1. List every scenarioName, trigger, schedule, apps, who relies on it, credits per month.
  2. Mark incomplete executionsResolve or note anything stuck in Make before starting.
  3. Rank by riskPayment, invoice and customer message flows go last.
  4. Keep Make switched onDo not turn scenarios off until the new workflow has been proven.
  5. Decide who looks after n8nName the person responsible for backups, updates and alerts.

When should I bring someone in?

  • Scenarios handle payments or customer data.
  • You plan to self-host with nobody to manage the server.
  • Scenarios use many iterators and aggregators.

How do I handle it?

  1. Inventory firstI map scenarios, connections, schedules and failure behaviour, and mark what must not be interrupted.
  2. Choose hosting deliberatelyHosted or self-hosted depends on who will patch, back up and monitor it.
  3. Rebuild and compareEach scenario is rebuilt, run in parallel on test data, and compared with Make's output.
  4. Switch one at a timeWebhooks are repointed and alerts verified before each old scenario is switched off.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I import a Make scenario into n8n?

I would not assume so. Plan to rebuild each one and compare results.

Will it cost less?

It depends on your run volume and on who looks after the server if you self-host.

What happens to my incomplete executions?

Resolve them in Make first, or they are left behind when the scenario is switched off.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.