Guide · switching
Switching from Zapier to Make — when the rebuild is worth it
You already have a Zapier book. This page is whether rebuilding it as Make scenarios is worth the work. Totals are not published yet. Self-hosted is a separate lane. A score is not a reason to rebuild every Zap. This page does not add new scores.
Use this page if the book is already Zapier
Use
Use this page if…
You are on Zapier and weighing Make. You want when the rebuild is worth it, what to expect for credentials and for Zaps becoming scenarios, and the period when both stay on. The next step after a yes is Parallel-run one job before you switch.
Skip
Skip if…
You only want the unit dictionary — Tasks vs credits vs executions. You only want free-tier cliffs — When free isn’t enough. You are on an n8n path — When n8n Cloud is the right pick or When n8n self-host is worth it. You want the full trio pick and you do not have a Zapier book — Which automation tool for small teams. This page does not rank products.
A use-or-skip check for a Zapier book moving toward Make.
- You already run Zaps and you are weighing a move to Make.
- You need what happens to logins and to each Zap, and how to run both before you cut over.
Partner signup. We may earn a commission. Rankings are not sold.Try MakeParallel-run one job before you switch
Read more
What this page tells you. When a team already on Zapier should rebuild that book on Make, what a Zap and a login do not become, and how to keep the Zap on while one scenario is compared. Companion to Make vs Zapier, When Make is the right pick, What does not migrate, and Parallel-run one job before you switch. This page does not reprint those reads. It does not invent a monthly dollar. It publishes no annual savings. It does not add new scores.
GuideSome scores not shown yetVendor pages accessed 2026-09-30Affiliate · pc=stackscorecardLive scorecard
This page is a Zapier book, not a second compare
The question is whether the Zaps you already run are worth rebuilding as scenarios. It is not a fresh pick between Make and Zapier — that is Make vs Zapier. It is not the dictionary of tasks, credits, and executions. It is not the free-plan cliff. It is not an n8n move. A Make book moving to n8n is Switching from Make to n8n. A Make book moving to Zapier is Switching from Make to Zapier. An n8n book moving to Zapier, with Cloud and self-host kept apart, is Switching from n8n to Zapier. It is not the four-question trio pick for a team that does not already have a Zapier book. Criterion scores are not a reason to rebuild every Zap this week. This page does not add new scores. It is not a second ranking.
If the Zaps still write the right rows and the people who own them will not map modules, stay. Honest cases: When Zapier is still the right pick. If the job is a canvas plus a credit meter, the choose-Make read is When Make is the right pick.
When the rebuild is worth it
Worth the rebuild means operator time, not a cheaper bill. Count the same job in Zapier tasks and Make credits before you treat a switch as savings. Same job, three meters · Tasks vs credits vs executions. This page does not claim you will save.
Worth it
Someone will map the scenario
In Make, everything you build is a scenario. Modules are the building blocks. A standard scenario is a series of non-AI modules that follow fixed rules. If someone on the team will draw that canvas — a sheet row, then Slack, then a branch — and keep the matching Zap on until the writes match, the rebuild can be worth it.
Worth it
The apps exist on Make, or you will use HTTP
Make’s pricing page lists 3,000+ apps on Free and 3,000+ standard apps in the plan table. Zapier’s pricing page says Zapier connects 9,000+ apps. If the connector you need is on Make, rebuild that Zap. If Make has no app for it, Make’s connection help says you can use the HTTP app. If the job depends on an app only Zapier lists, and nobody will maintain HTTP, stay on Zapier.
Not yet
Do not rebuild for a bill you have not counted
A Zapier task is any successful action that runs in Zapier. Only successful actions count. Make credits replaced operations as the billing-unit name. By default, 1 operation equals 1 credit for non-AI apps. One task is not one credit. If you cannot name the job in both units, do not switch because a plan name sounds smaller.
Not yet
Do not rebuild if history or a login has to travel
Zap history and Zapier connections do not become a Make scenario. If the reason to move is “bring the last year of runs with us,” that file does not import. What else sticks is on What does not migrate. This page does not reprint that list.
Source: Make — what’s a scenario · Make — pricing · Zapier — pricing · Zapier — how task usage is measured · Make — credits · Make — connect an application · accessed 2026-09-30
What a Zap becomes on Make
Expect a rebuild, not a file drop. Zapier’s import and export article (updated 29 May 2026) says import and export only support JSON. You download Zap workflows from Settings, then Security and data. After a Zapier import you turn the Zaps on and test app connections. Imported Zaps land in a folder named Imported Zap workflows plus the date. Unless you are the account owner or super admin, you can only export Zaps you own. The article lists Free, Professional, and Team. The title also names Team or Enterprise. Import is not available during a free Zapier trial. That path moves Zaps between Zapier accounts. It does not create a Make scenario.
Make export is a blueprint .json file: scenario modules, module settings, and mapped values. Import is three dots, then Import blueprint, in the Scenario Builder. Make recommends a new scenario before you import, because importing into an unsaved scenario drops those unsaved edits. The imported blueprint must be below 2 MB. You can also copy the blueprint JSON to the clipboard and paste it on another Make canvas. None of that reads a Zapier JSON file.
So the expectation is: one Zap becomes one scenario you build or adapt. The trigger becomes the first module. Each later action becomes another module. Fields are mapped again. A standard scenario is the usual small-team start. An AI scenario or an AI agent scenario is a different Make type — do not assume a Zap’s AI step lands as the same module.
Source: Zapier — import and export Zap workflows · Make — blueprints · Make — what’s a scenario · accessed 2026-09-30
Credentials do not travel
Make’s blueprint warning is direct: users still need to create connections for their accounts after importing the blueprint. A connection is how a scenario reaches a third-party app. You create it in the Scenario Builder when you add a module. Some apps are a login grant. Others ask for an API key, client id, or client secret. Make keeps two types: standard connections, and dynamic connections, which Make calls an Enterprise-level feature. Afterward, Credentials in the left sidebar is where you verify, reauthorize, edit, or delete a connection. Editing a connection replaces the old details. Make says you have to provide all the credentials required to create the connection again, because Make does not keep the original connection data.
Zapier’s connection export does not fill that gap. The export is a CSV of metadata: connection id, app, title, owner email, status, and similar fields. The article says the export never includes credentials, API keys, or other sensitive authentication data. The page lists Enterprise under available plans, and the before-you-begin note says the account owner on any plan, or a super admin on Team or Enterprise, can start it. Either way, the file is an audit list. It is not a Make connection.
Plan the overlap around that fact. Name who will log in to each app on Make and who still owns the Zapier connection until the Zap is off. A Zap that still runs is not a Make connection.
Source: Make — blueprints · Make — connect an application · Zapier — export app connections · accessed 2026-09-30
Run both before you turn the Zap off
The parallel-run period is one critical job, not the whole account. Keep that Zap on. Rebuild it as one scenario. Create the Make connections. Compare the writes for the same trigger window — the row, the message, and what happens when a required field is missing. Then turn that Zap off. Leave the Zap intact until the scenario has handled a real run, so you can turn the scenario off and leave the Zap on if the writes do not match.
Do not move every Zap on the same day. Zapier and Make do not publish a required number of days for that overlap. This page does not invent a required number of days. The checklist — which job, what to compare, how to go back — is Parallel-run one job before you switch.
Zap history does not shorten that period. Zapier can export up to 5,000 Zap runs at a time, as CSV or JSON, emailed to the Zapier account (article updated 29 May 2026). That file is history. It is not a blueprint, and it does not become scenario history on Make.
Source: Zapier — export your Zap history · Zapier — import and export Zap workflows · accessed 2026-09-30
Plan names and meters (dated)
Official list pages only: Make — pricing · Zapier — pricing, accessed 2026-09-30. This table names the plan and the meter. Monthly and annual dollar bills are an em dash. Make’s page lists Free, Core, Pro, Teams, and Enterprise with a credit slider — it does not publish one fixed monthly or annual dollar we are copying here. Zapier’s page does publish dollars. This page does not reprint them. It does not claim you will save. It publishes no annual savings.
Unit names, same access date. Zapier: A task is any successful action that runs in Zapier. Only successful actions count (help article updated 21 August 2026). Make: credits are the currency you buy and consume to use Make. Credits replaced operations as the billing-unit name. For non-AI apps, 1 operation equals 1 credit (credits article updated 30 Sep 2026). The Make pricing page also says each module action in a scenario counts as one credit.
Swipe sideways on a narrow screen.
| Plan | Meter | What the list page names | Monthly | Annual | Date checked |
|---|---|---|---|---|---|
| Make Free | Credits | 1,000 credits/month. No time limit on the Free plan. 15-minute minimum interval between runs. 3,000+ apps. | — | — | 2026-09-30 |
| Make Core | Credits | Everything in Free, plus unlimited active scenarios. | — | — | 2026-09-30 |
| Make Pro | Credits | Everything in Core, plus priority scenario execution. | — | — | 2026-09-30 |
| Make Teams | Credits | Everything in Pro, plus teams and team roles. | — | — | 2026-09-30 |
| Make Enterprise | Credits | Everything in Teams, plus custom functions and enterprise app integrations. | — | — | 2026-09-30 |
| Zapier Free | Tasks | 100 tasks/mo. Two-step Zaps. 15 min polling. | — | — | 2026-09-30 |
| Zapier Professional | Tasks | Multi-step Zaps. Filters and paths. | — | — | 2026-09-30 |
| Zapier Team | Tasks | Shared app connections. Shared Zaps and folders. | — | — | 2026-09-30 |
| Zapier Enterprise | Tasks | Custom plan arranged with Zapier Sales. Not a fixed public tier on the page we read. | — | — | 2026-09-30 |
Zapier Free, Professional, and Team are the self-serve plan levels on zapier.com/pricing. Enterprise is arranged with Zapier Sales. Higher Zapier task tiers exist on that page and are not copied here. Make extra-credit dollars are not listed as a fixed figure on the primary pricing page.
Scoring status
Scoring status
The live card is Make vs n8n vs Zapier. Totals are not published yet. This page does not add new scores.
Rules: How scoring works.
Try Make
Sources
Primary vendor pages. Access date for every citation on this page: 2026-09-30. Plan names stay as published. Dollar bills stay off this page.
- Make — what’s a scenario · accessed 2026-09-30
- Make — blueprints · accessed 2026-09-30
- Make — connect an application · accessed 2026-09-30
- Make — credits · accessed 2026-09-30
- Make — pricing · accessed 2026-09-30
- Zapier — import and export Zap workflows · accessed 2026-09-30
- Zapier — export app connections · accessed 2026-09-30
- Zapier — export your Zap history · accessed 2026-09-30
- Zapier — how task usage is measured · accessed 2026-09-30
- Zapier — pricing · accessed 2026-09-30
FAQ
When is switching from Zapier to Make worth the rebuild?
When someone will map modules on a canvas, the apps you need are on Make or you will use Make’s HTTP app, and you can keep each Zap on while one scenario is rebuilt and compared. It is not worth it when nobody will draw the scenario, the app is only on Zapier, you need Zap history inside Make, or the only argument is a cheaper bill you have not counted in tasks versus credits. This page does not claim a savings figure.
Can I import a Zap into Make?
No. Zapier export is Zapier JSON, for another Zapier account, from Settings, then Security and data. Make import is a blueprint JSON of scenario modules, module settings, and mapped values. Those files are not interchangeable. There is no one-click Zap-to-scenario import. Rebuild the trigger and the later modules, then map the fields again.
Do Zapier logins or API keys move to Make?
No. Make says users still need to create connections after importing a blueprint. Zapier’s app-connection export never includes credentials, API keys, or other sensitive authentication data. It is metadata only. Recreate each connection in Make’s Scenario Builder. Manage them under Credentials.
What should I expect a Zap to become?
A scenario. In Make, everything you build is a scenario, and modules are the building blocks. A standard scenario follows fixed rules. You recreate the trigger and each action as a module. Imported blueprints must stay below 2 MB. You still create the connections yourself.
How long should Zapier and Make both stay on?
Long enough to compare one critical job on the same trigger window: the Zap stays on, the scenario is rebuilt, the writes match, then that Zap turns off. The vendors do not publish a required number of days. This page does not invent one. Do not move every Zap on the same day. The checklist is Parallel-run one job before you switch.
Does Zap history become Make scenario history?
No. Zapier can export up to 5,000 Zap runs as CSV or JSON and email that file to the Zapier account. That file is Zapier history. It is not a Make blueprint and it does not become scenario history.
Does this page publish a monthly bill?
No. It names plan names and meters only. Monthly and annual dollar cells are an em dash. Make’s pricing page lists Free, Core, Pro, Teams, and Enterprise. Zapier’s pricing page lists Free, Professional, Team, and Enterprise. This page does not copy dollar bills and publishes no annual savings.
Does this guide score Make, n8n or Zapier?
No. Totals are not published yet.
Affiliate disclosure
Make is a live partner signup (pc=stackscorecard) and is marked affiliate; we may earn a commission. Zapier stays an official-site URL with UTM only — no invented IDs. Zapier has no Stack affiliate. Rankings are not sold. Policy: Affiliate disclosure · Disclosures.