Stack Scorecard

Guide · sticky residue

What does not migrate between Zapier, Make, and n8n

Name what sticks before you switch. Totals are not published yet. Self-hosted is a separate lane. This page does not add new scores.

Expect this to stick, or don’t assume it migrates

Sticks

Expect this to stick if…

You are leaving Zapier, Make, or n8n — or leaving Notion, Airtable, or Superhuman Docs. Logins, run history, leftover quota, schedules, webhook URLs, and who can edit stay on the old tool. Steps that only exist in one tool stay behind. Hub formulas, buttons, automations, and Packs do not arrive as a running app.

Don’t assume

Don’t assume it migrates if…

You downloaded a JSON, CSV, PDF, or Markdown dump. Field names look the same. The product was renamed — Coda is now Superhuman Docs; that is a new name, not a move. You still need to know whether the job is worth automating — that is What’s worth automating. You want to run both copies — that is How to run old and new automation side by side. You still need to name the hub — Name one system of record for small-team ops. This page lists residue. It does not rank products.

A stick-or-don’t-assume check for one move.

  • You are about to move a Zap, Make scenario, n8n workflow, or a hub.
  • You need what sticks: logins, history, one-tool steps, Packs, and who owns the job.

Live scorecard

Read more

What this page tells you. Help a small team name what does not migrate when switching a hub or an automation — sticky residue, not a rank. Exports are not interchangeable. Logins, history, and one-tool steps must be rebuilt. A CSV is not a running hub. There is no one-click migration. Then run both copies before you switch — this page does not reprint that checklist. It does not reprint the pass-or-defer audit or the name-the-hub read. Dated list prices live on the picker after a pass. It adds no score cells.

GuideSome scores not shown yetVendor pages accessed 2026-09-17Live scorecard

Coda is now Superhuman Docs (Jul 2026). Source: Superhuman — What’s changing: Coda becomes Superhuman Docs.

This page is not a switch checklist

The question here is what stays behind. How to run the old job and the new job at the same time lives on How to run old and new automation side by side. Whether the process is ready lives on What’s worth automating. Whether the hub is named lives on Name one system of record for small-team ops. What to watch on the meter lives on How to meter automation. When a run fails, name the class on When automations fail. Which product to use lives on Which automation tool for small teams. This page does not reprint those reads. It does not rank tools. It does not add new scores.

This page also skips a list-price table. The question is what sticks — not which plan to buy. After a pass, dated official list prices live on the picker. This page does not claim you will save money, and it does not invent a monthly dollar from a /500 score.

What sticks when you switch

These items stay on the old tool. Rebuild them on the new tool. Then run both copies — this page does not reprint that checklist.

  • Exports. Vendor JSON, CSV, PDF, and Markdown are not interchangeable. Same-product import is still a backup, not a cross-tool move.
  • Auth tokens. Logins, API keys, and OAuth secrets. Recreate them on the new tool.
  • Run history. Zap runs, Make scenario history, and n8n executions stay where they ran.
  • Proprietary nodes and apps — plus custom nodes and code. A Zapier-only app, a Make module, or an n8n node type the new tool does not have.
  • Schedules and webhook URLs. Re-enable the new tool. A rebuilt trigger gets a new URL.
  • Org permissions and ownership. Users, roles, sharing, and team folders. Re-bind access on the new tool.
  • Billing meters. Zapier tasks, Make credits, and n8n executions are different units. Leftover quota does not convert.
  • Hub residue. Notion, Airtable, and Superhuman Docs dumps are files. Formulas, buttons, automations, and Packs do not arrive as a running app.

This page names the live scorecard. It adds no cells and does not change rankings.

Hub residue — Notion, Airtable, Superhuman Docs

A dump is not a running hub. Name the object people will edit tomorrow on Name one system of record for small-team ops — this page does not reprint that read. Coda became Superhuman Docs on 8 Jul 2026. A new name is not a rebuild.

Dump

Notion

Notion can export a page or database as PDF, HTML, or Markdown and CSV. You can also export workspace content. Notion says you cannot instantly recreate your workspace by reuploading that dump. Views do not all come along — a database export is the current view or the default view.

Source: Notion — export your content · accessed 2026-09-17

CSV

Airtable

Airtable can download a grid view as CSV on web and desktop. That is one view, not a full base as one file. Each table needs its own CSV. Attachments are not the base — they travel as names and short-lived URLs. Linked records, interfaces, and automations do not arrive as a running hub.

Source: Airtable — getting started with views (CSV export) · accessed 2026-09-17

Stay-or-move after the rename lives on Coda is now Superhuman Docs — stay, or move to Airtable / Notion?. Object picks live on Notion vs Airtable for small-team ops hubs · Notion vs Superhuman Docs (formerly Coda) for small-team wikis and docs · Airtable vs Superhuman Docs (formerly Coda) for small-team ops hubs. See the workspace scorecard.

There is no one-click migration

Make blueprints, n8n workflow JSON, and Zapier Zap JSON are not interchangeable. An export is a backup inside one product. Crossing tools means rebuild the job. There is no one-click Make ↔ Zapier ↔ n8n import. Do not paste a Make .json into Zapier or n8n and expect a working job. The same is true in every other direction.

A rebuilt job can still look on while the write is wrong. Name the class on the failure taxonomy before you rewrite the flow. A green history icon is not the write — when automations look fine. Name who owns reconnects and 2am on who should own your automations.

What you must rebuild

Each category is a rebuild, not an import. The switch steps stay on How to run old and new automation side by side — this page does not reprint that checklist.

Exports — a backup, not a move

Same-product export can move a job inside one vendor. Crossing tools, there is no file to import. Rebuild the trigger, the mapping, and the write.

  • Rebuild. Recreate the job on the new tool. Do not treat a downloaded JSON as a one-click migration.
  • Make blueprints are .json, below 2 MB, and clipboard copy exists.
  • n8n editor JSON may include credential names and IDs — clean that file before you share it. CLI packages (.n8np) stay inside n8n and are Preview.
  • Zapier import and export are JSON, on Team or Enterprise. Import is not available during a free Zapier trial.

Sources: Make — blueprints · n8n — export and import · Zapier — import and export Zap workflows · accessed 2026-09-17

Credentials — recreate every connection

Auth tokens do not travel. A connection name in an export is not a working secret.

  • Rebuild. Create each connection on the new tool and test it before you run both copies. Auth failure is a reconnect job — name the class first.

Logins do not travel

Connections

Make

Blueprints include modules, settings, and mapped values. Users still need to create connections for their accounts after importing the blueprint.

Source: Make — connect an application · accessed 2026-09-17

Secrets stay

n8n

Exported workflow JSON includes credential names and IDs — clean that file before you share it. HTTP Request nodes may contain authentication headers when imported from cURL. n8n packages: credential secrets never travel. A credential file holds ID, name, and type only.

Source: n8n — export and import · accessed 2026-09-17

Metadata only

Zapier

After import, turn Zaps on and test app connections. Reconnect any connection that is no longer active. A connections CSV never includes credentials, API keys, or other sensitive authentication data.

Source: Zapier — export app connections · accessed 2026-09-17

Run history stays on the old tool

A history export is not a new-tool import. Zapier can export up to 5,000 Zap runs at a time as CSV or JSON. That file is Zapier history. It does not become a Make scenario run or an n8n execution.

Make keeps scenario history on the History tab — run status, timestamps, operations count, and a CSV of those details. n8n packages do not carry executions or execution history. n8n says a package is not a full backup: no execution data travels.

  • Rebuild. New-tool history starts empty. Keep the old history as the audit trail. A green new-tool icon is not the write — when automations look fine.

Sources: Zapier — export your Zap history · Make — scenario history · n8n — packages · accessed 2026-09-17

Proprietary nodes, apps, and code stay behind

Make blueprints, n8n workflow JSON, and Zapier Zap JSON are not interchangeable. There is no one-click migration. n8n packages stay inside n8n, are Preview, and fail the import if the target instance does not have a node type the workflow uses.

An app listed only in Zapier’s directory has no Make module or n8n node to import into. Zapier help publishes 9,000+ apps. Make publishes 3,000+. That gap is a rebuild, or a reason to stay. Catalog sizes are published directory facts, not a score.

Custom nodes and code are the same job. Zapier Code, Make HTTP, and n8n Code or HTTP Request are not one runtime. Rewrite the step on the new tool, or stay if there is no equivalent. Do not invent a converted list of nodes.

  • Rebuild. Recreate each proprietary app, custom node, and code step. If the new tool has no match, that job is a reason to stay — not a silent skip.

Zapier import and export are JSON, on Team or Enterprise. Import is not available during a free Zapier trial. Make imports must stay below 2 MB.

Schedules and webhook URLs do not keep firing

Inside one product, a blueprint or JSON may keep a schedule setting. Crossing tools, the new tool has no schedule to import. Re-set the interval and turn the job on.

  • Rebuild. Enable the new-tool schedule yourself. After a same-product Zapier import, turn Zaps on. Do not assume the old interval copied over.
  • A rebuilt trigger also gets a new URL — the source webhook does not move. Update every sender that POSTs to the old URL.
  • If both copies stay on and both write, you get duplicates. Decide who writes on the side-by-side check — this page does not reprint those steps.

Billing meters do not convert

A leftover Zapier task allotment does not become Make credits. Make credits do not become n8n executions. A Zapier task is a successful action step. A Make credit is usually one module action. An n8n execution is one full workflow run. Do not treat one task as one credit as one execution.

Full unit math: How to meter automation. This page does not invent an overage dollar or a monthly dollar.

Ownership and org permissions do not travel

n8n packages omit users, project members, roles, and sharing. Credential secrets and configuration stay behind. Data table rows, pinned data, workflow static data, and workflow version history do not travel either.

Zapier import lands Zaps in a new folder named “Imported Zap workflows - YYYY-MM-DD”. Unless you are the account owner or super admin, you can only export Zap workflows you own. Make connections are created in the new team; other people on that team can use them. Re-bind owners and sharing after the rebuild.

  • Rebuild. Name the new-tool owner before you switch. Re-bind roles, folders, and who can reconnect. An orphaned job has no way back — who should own your automations.

After you know what sticks

Residue is named. Use the sibling that owns the next job — without treating this page as a ranking.

Open the side-by-side check

Primary CTA stays the live scorecard. This button is the next read after residue is named.

How this sits on the scorecard

The live card is Make vs n8n vs Zapier. Totals are not published yet.

Workspace card. Live card: Notion vs Superhuman Docs (formerly Coda) vs Airtable. Different criteria.

When-to-pick copy lives on Make vs n8n vs Zapier — when to pick each. Pair reads: Make vs n8n · Make vs Zapier · n8n vs Zapier. Scoring rules: Methodology.

Open the live scorecard When to pick each

Product links

Official

n8n

Official site: n8n · no affiliate ID · not a partner mark

Official

Zapier

Official site: Zapier · no affiliate ID · not a partner mark

Hub sites named for residue only. Official: Notion · Airtable · Superhuman Docs (formerly Coda) · no affiliate ID.

Sources

Primary vendor export, history, connection, hub-dump, and unit pages. Access date for every citation on this page: 2026-09-17. Totals are not published yet. We do not invent a cross-vendor import path, a converted list, or an overage dollar.

FAQ

What does not migrate between Zapier, Make, and n8n?

Exports are not interchangeable. Logins, run history, and steps that only exist in one tool must be rebuilt. Custom nodes and code, schedules, webhook URLs, leftover quota, and who can edit stay on the old tool. Make blueprints omit connections. Zapier connection export is metadata only. n8n packages omit credential secrets, executions, users, project members, roles, and sharing. There is no one-click migration. Rebuild one job, then run both copies.

Can I import a Zap into Make or n8n?

No. Zapier export is Zapier JSON. Make blueprints and n8n workflow JSON are not interchangeable with it. n8n packages are Preview and stay inside n8n. There is no one-click Zapier → Make or Zapier → n8n import. Rebuild the job on the new tool, compare the writes, then switch. See How to run old and new automation side by side before you switch.

Do logins or API keys move with an export?

No. Make says users still need to create connections after importing a blueprint. Zapier’s connection export never includes credentials, API keys, or other sensitive authentication data. n8n packages ship credential ID, name, and type only — credential secrets never travel. Editor JSON may include credential names and IDs; clean that file before you share it.

Does run history move to the new tool?

No. Zapier can export up to 5,000 Zap runs as CSV or JSON — that file is Zapier history, not a Make or n8n import. Make scenario history stays on the History tab. n8n packages do not carry executions or execution history, and n8n says a package is not a full backup.

Do custom nodes or Code steps migrate?

No. A Zapier-only app, a Make module, or an n8n node type the new tool does not have stays behind. n8n packages fail the import if the target instance lacks that node type. Zapier Code, Make HTTP, and n8n Code or HTTP Request are not one runtime. Rewrite the step, or stay if there is no equivalent.

Do schedules or webhook URLs keep firing on the new tool?

No. Crossing tools, the new tool has no schedule to import. Re-set the interval and turn the job on. A rebuilt trigger gets a new URL — the source webhook does not move. If both copies write, you get duplicates. Decide who writes on How to run old and new automation side by side before you switch.

Does ownership or who can edit travel with the export?

No. n8n packages omit users, project members, roles, and sharing. Zapier import lands in a new folder named Imported Zap workflows; unless you are the account owner or super admin, you can only export Zaps you own. Re-bind owners and sharing on the new tool. Name who owns reconnects on Who should own your automations.

Does a hub export become a running Notion, Airtable, or Superhuman Docs app?

No. Notion can export PDF, HTML, or Markdown and CSV, and says you cannot instantly recreate a workspace by reuploading that dump. Airtable can download a grid view as CSV — not a full base as one file. Superhuman Docs (formerly Coda) can copy/paste, download a table CSV, export a page PDF, or dump owned docs as.txt and.csv. Formulas, buttons, automations, and Packs do not arrive as a running app. Name the hub on Name one system of record for small-team ops.

Did the Coda rename migrate my doc to a new product?

No. Coda became Superhuman Docs on 8 Jul 2026. Superhuman says existing docs, tables, Packs, automations, formulas, and Maker billing stay. That is a new name, not a rebuild, and not a one-click move to Notion or Airtable. See Coda is now Superhuman Docs — stay, or move to Airtable / Notion?

How do I switch without a surprise?

This page names what sticks. It does not reprint the side-by-side checklist. Keep the old job on. Rebuild one job on the new tool. Compare rows, messages, and the failure path. Then switch. See How to run old and new automation side by side before you switch. If the hub is unnamed, stop on Name one system of record for small-team ops.

Affiliate disclosure

Product links on this page: n8n, Zapier, Notion, Airtable, and Superhuman Docs (formerly Coda) stay official-site URLs with UTM only — no invented IDs. Make Partner (pc=stackscorecard) is live elsewhere on the site and is not the primary call here. Rankings are not sold. Wordmarks are not partnership marks. Policy: Affiliate disclosure · Disclosures. Commissions do not move a score, a weight, or a pricing cell.