Make to n8n migration

Make to n8n migration at a fixed price per scenario.

Move Make scenarios to n8n for a fixed $450 per standard scenario: module and router mapping, duplicate and failure tests, one-writer cutover and a rollback point.

Start with your customers

What do people need to know before they choose you?

Your customers need clear answers and an easy next step. We review the information they see, fix the gaps, and check what changes.

From a question to an enquiry

  • 01Scenario inventory
  • 02Router and iterator mapping
  • 03n8n rebuild
  • 04Duplicate and failure tests
  • 05One-writer cutover
01

The short answer.

A Make to n8n migration rebuilds each scenario in n8n and proves it behaves the same before the Make scenario is switched off. Marsen does this for a fixed $450 (USD, excluding tax) per standard scenario: one trigger, an agreed number of modules and connected apps, and no bulk data migration. Larger scenarios are quoted after a short review call.

  • Fixed price: $450 per standard scenario
  • Scenario inventory, including routers, filters, iterators, aggregators and error handlers
  • Written module and branch map you approve before the build
  • n8n workflow rebuilt and tested
  • Cutover with one active writer and a rollback point
  • Handover note: owner, credentials, alerts and recovery
02

Why a Make blueprint cannot be imported.

Make exports a scenario as a blueprint file. It is a useful reference, but n8n uses a different workflow format and different node behaviour, so nothing runs by importing it. Each module is rebuilt: routers become IF or Switch branches, iterators and aggregators become n8n's item handling or Loop and Aggregate nodes, Make's data stores become a database or n8n's own data tables, and error-handler routes become explicit retry and error-workflow logic. Make also processes bundles one at a time where n8n passes arrays of items between nodes, which is the most common source of subtle differences, so the map step checks it deliberately.

03

A worked example: a lead-routing scenario.

A typical scenario watches a form, looks up the contact in a CRM, uses a router to send high-value enquiries to a sales channel and everything else to a shared inbox, and logs each enquiry in a Google Sheet. In n8n, the form posts to a webhook in test mode first. A lookup checks for an existing contact; a Switch node replaces the router; the CRM write uses a stable submission ID so a repeated delivery does not create a duplicate; and the sheet row runs only after the CRM write succeeds. The same test submissions are replayed through both versions and the CRM, channel and sheet results compared. On cutover day the Make scenario is turned off, the form is pointed at n8n, the first live submissions are checked, and the scenario is kept, switched off, for an agreed rollback window.

  • Before: form → Make (router) → CRM, Slack, Google Sheets
  • After: form → n8n webhook → deduplicated CRM write → Switch → Slack or inbox → Sheets
  • Tests: valid, duplicate, invalid input, CRM temporarily unavailable
  • Cutover: switch off scenario, repoint form, verify first live records
04

The six steps.

Every migration follows the same steps as Marsen's Zapier migrations, and you approve the map before anything is built.

  • 1. Inventory: export the blueprint and list connections, routers, filters, schedules and owners
  • 2. Map: module-by-module and branch map; you approve it
  • 3. Rebuild: create the n8n workflow and reconnect credentials with least privilege
  • 4. Test: normal, duplicate, invalid and failure inputs against a test destination
  • 5. Cut over: one active writer, first live records checked
  • 6. Hand over: runbook, alert route, credential owner and rollback window
05

When to stay on Make.

Make's visual scenarios and operations-based pricing suit many teams well. Move when operation costs have grown with volume, when you need code, direct API access or self-hosting for data-control reasons, or when you are consolidating automations onto one platform with a technical owner. If moving does not save money or reduce risk, we will say so on the first call.

Clear from
the first conversation.

We agree the work, the cost, and how we’ll check progress together.

A little more clarity

Good questions.
Straight answers.

Talk to our team
How much does a Make to n8n migration cost?

A standard scenario is a fixed $450 (USD, excluding tax). Scenarios with many modules, routers or historical data to move are quoted after a short review call.

Can n8n import a Make blueprint?

No. The blueprint documents the scenario, but n8n uses a different format. Each module, router and error handler is rebuilt and tested in n8n.

What replaces Make routers and iterators in n8n?

Routers become IF or Switch branches. Iterators and aggregators map to n8n's item handling, Loop and Aggregate nodes. Because n8n passes arrays of items between nodes, the map step checks every place where Make processed one bundle at a time.

Will I lose data during the switch?

The cutover is planned so only one system writes at a time, the first live records are checked, and the Make scenario is kept switched off but intact during an agreed rollback window.

Do you also migrate from Zapier?

Yes. Zapier to n8n migration has the same fixed price of $450 per standard workflow.

A practical next step

Tell us what
you want to improve.

Book a call

You don’t need a technical plan to start a conversation.