Moving From Zapier to Make: What the Switch Involves

By Published On: November 16, 2026

Moving from Zapier to Make involves five jobs: list every Zap you run, export them, rebuild each one as a Make scenario, reconnect every app, and test each scenario side by side before you turn the Zap off. Nothing moves over by itself. Zapier gives you a file describing your Zaps, and the building happens in Make.

Key takeaways

  • A Zapier export describes your Zaps. It does not carry your app logins, so every app gets connected again in Make.
  • Start with an inventory: which Zaps are on, how many times a month they run, who owns them and what breaks if they stop.
  • Rebuild one workflow at a time and run it beside the Zap until the results match.
  • Count the cost before you move. Make counts the trigger as a credit; Zapier does not count it as a task.
  • Turn each Zap off only after its Make scenario has passed a test with live data.

What do you need to list before you move anything?

You need a list of every Zap that is turned on, what starts it, what it does and who depends on it. For HR and legal teams, that list usually includes new-hire onboarding, candidate follow-up, intake forms, document requests and calendar notices.

For each Zap, write down:

  • The trigger: the app and event that starts it, such as a new form entry or a new row.
  • Every action step, in order, including Formatter, Filter and Paths steps.
  • How many times it runs in a month. Zapier’s Zap history shows this.
  • The person who owns it, and what happens to the business if it stops for a day.
  • Every app account it logs in to.

Zaps that are off, broken or duplicated come off the list. A move is a good time to retire them instead of rebuilding them.

How do you export your Zaps from Zapier?

Zapier’s Help Center gives the path: click your profile icon, choose Settings, choose Security and data, and in the Data management section request an export of your account data. Zapier emails a ZIP file, and the Zapfile.json inside it “contains an export of all undeleted Zap workflows” with the input and output values for each step (Zapier Help Center: export your account data).

The export is a reference for the rebuild. It lists each Zap’s title, status and steps. In the exports we have worked with, it holds no app connections, so it cannot log in to anything on its own.

What does rebuilding a Zap in Make look like?

Each Zap becomes a Make scenario. The trigger becomes the first module, and each action becomes a module after it. Zapier’s Paths become a Make Router, and Zapier’s Filter becomes a filter on the line between two modules.

Some Zapier tools have no single matching module. Zapier Tables, Forms and Storage, for example, need a new home in Make, such as a Make data store, a form tool you already own or a Google Sheet. Decide where that data lives before you build.

Our guide to moving one Zap to Make, step by step walks through a full new-hire example.

Why do app connections have to be set up again?

Each platform holds its own logins to your apps, and the export does not carry them. In Make, you create a connection for each app the first time a module needs it.

Apps that sign in through a login screen, such as Google Workspace or Microsoft 365, need the account owner to click Allow. Apps that use an API key need someone with access to that key. Line up those people before the rebuild starts. A missing login holds up a scenario until the right person approves it.

How do you test before you turn a Zap off?

Run the Make scenario beside the Zap and compare the results on real records. Point the scenario at a test sheet, a test folder or a test contact first. When the output matches what the Zap produces, switch the scenario to the live destination and turn the Zap off on the same day so nothing runs twice.

Check three things on every test run:

  1. Every field arrives in the right place, with dates and phone numbers in the right format.
  2. Records that should be skipped are skipped.
  3. When an app is down, the error is caught and someone is told. Make’s error handler modules do not use credits (Make pricing FAQ).

How much does the move change your monthly bill?

For most HR and legal workloads, the bill goes down. A new-hire workflow with one trigger and three actions, run 1,000 times a month, costs $133.50 a month on Zapier Professional and $16 a month on Make Core, both on monthly billing, read November 13, 2026 from Zapier’s pricing page and Make’s pricing page.

Make counts the trigger as a credit, so count each workflow before you compare. Our worked pricing examples show the math, and the full price tables list every tier on both platforms.

Expert Take

Teams expect the hard part of a move to be the building. It is the inventory. Most accounts we look at have Zaps nobody remembers setting up, Zaps that fail every week without anyone looking, and two Zaps doing the same job. The rebuild goes fast once the list is clean. We spend the first part of every move deciding what not to bring over, and that decision cuts the build and the monthly bill at the same time.

Frequently asked questions

Can I import a Zapier export directly into Make?

No. The export describes your Zaps, and each Zap is rebuilt as a Make scenario by hand or with an AI assistant’s help.

Do my app logins move from Zapier to Make?

No. Every app is connected again in Make, and apps that use a login screen need the account owner to approve the connection.

Should I move every Zap at once?

No. Move one workflow at a time, test it beside the Zap, and turn the Zap off only after the Make scenario matches its results.

What breaks most when teams move?

Missing app logins, Zapier-only tools such as Tables and Storage, and triggers that behave differently. Our guide to what breaks in a move covers each one.

Try Make free for a month, with 10,000 free actions included.

Get 10,000 Free Actions on Make

Where 4Spot fits

4Spot Consulting is a Make Certified Partner. We build the inventory with you, rebuild each workflow in Make with error handling, connect your apps and test every scenario before a Zap turns off. Start a free Make account or contact 4Spot Consulting to plan your move.

If you would like us to handle this for you, we have this process dialed in.

About 4Spot Consulting

4Spot Consulting designs, builds, and supports automation for HR teams, recruiting desks, and law firms.

Free OpsMap™️ Quick Audit

One page. Five minutes. Pinpoint where your business is leaking time to broken processes.

Free Recruiting Workbook

Stop drowning in admin. Build a recruiting engine that runs while you sleep.

The Automated Recruiter by Jeffrey W. Arnold - Amazon #1 Best Seller

Ready to run the map on your business?

The OpsMap audit is free. You walk out with a written map either way.