How to Move One Zap From Zapier to Make, Step by Step

By Published On: November 16, 2026

To move one Zap from Zapier to Make, write down every step of the Zap, build a Make scenario that does the same steps in the same order, connect each app again, test it on a test record, run it beside the Zap on live records, and turn the Zap off once the results match. This guide walks through those steps with a new-hire onboarding Zap as the example.

Key takeaways

  • Pick one Zap with a clear owner and steady volume for your first move, not your most complex one.
  • Write the Zap down step by step before you open Make, including Filter, Formatter and Paths steps.
  • Use an instant trigger, such as a webhook, wherever the app offers one, because Make counts every trigger check as a credit.
  • Test on a test record first, then run the scenario beside the Zap on live records.
  • Turn the Zap off the same day you switch the scenario to live, so nothing runs twice.

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

Get 10,000 Free Actions on Make

Which Zap should you move first?

Move a Zap that runs every week, has one owner and touches no more than three or four apps. A new-hire onboarding Zap is a good first move for most HR teams: it runs enough times to test, the owner knows what correct output looks like, and a mistake shows up the same day.

The example Zap in this guide does four things:

  1. Trigger: a new entry on the new-hire form.
  2. Formatter: change the start date to the format the HRIS expects.
  3. Action: create the employee record in the HRIS.
  4. Action: send the new hire a welcome email, and create an onboarding task for the manager.

Step 1: How do you write the Zap down before you rebuild it?

Open the Zap in the Zapier editor and copy each step into a document: the app, the event, every field that is filled in and where its value comes from. Note any Filter conditions and Paths rules word for word. Zapier’s account export holds the same workflow data in a file called Zapfile.json (Zapier Help Center: export your account data), and the export is a useful backup of the record.

Also note two numbers from Zap history: how many times the Zap ran last month and how many of those runs failed. They tell you what to expect from the scenario and what it costs on Make.

Step 2: How many Make credits will the scenario use?

Count one credit for every module that runs, trigger included. Make’s Help Center says a trigger module runs once to check for new data and that check is one operation, and one operation equals one credit by default (Make: operations, Make: credits). The Router and error handler modules do not count (Make pricing FAQ).

The example Zap uses 3 Zapier tasks per run, because Zapier does not count the trigger or the Formatter step. In Make it uses 5 credits per run: the form trigger, the date format step, the HRIS record, the welcome email and the manager task. At 250 new hires a month, that is 1,250 credits, which fits Make Core’s 10,000-credit tier at $16 a month on monthly billing or $12 a month on annual billing, read November 13, 2026 from Make’s pricing page. The same 750 Zapier tasks cost $29.99 a month on monthly billing or $19.99 a month on annual billing on Zapier Professional, read the same day from Zapier’s pricing page.

The date format step can move into the HRIS module itself, by formatting the date right in the field mapping. That drops the scenario to 4 credits per run.

Step 3: How do you build the scenario in Make?

Create a new scenario and add the modules in the same order as the Zap.

  1. Trigger: add the form app’s “new entry” trigger. If the form tool can send a webhook, use Make’s custom webhook trigger instead, copy the webhook address Make gives you, and paste it into the form tool’s webhook settings. A webhook runs the scenario the moment an entry arrives and uses no credits while it waits.
  2. Date format: map the start date into the HRIS module with Make’s date functions, or add a step that sets the format, so the HRIS gets the date the way it expects.
  3. HRIS record: add the HRIS module that creates an employee, and map each field from the form.
  4. Welcome email: add your email app’s send module and map the new hire’s name, email and start date.
  5. Manager task: add your task app’s create module and map the manager, the due date and the new hire’s name.

Point the HRIS, email and task modules at test destinations first: a test employee, your own inbox and a test project.

Step 4: How do you connect each app?

Make asks for a connection the first time you add a module for each app. Apps with a login screen, such as Google Workspace or Microsoft 365, need the account owner to sign in and click Allow. Apps that use an API key need the key pasted into the connection. Zapier’s connections do not carry over, so line up the people who own each login before you start building.

Use the same accounts the Zap used. A welcome email sent from a different address, or a task created under a different user, is a change your team notices.

Step 5: How do you add error handling?

Add an error handler to every module that calls an outside app. For the HRIS module, set it to retry a few times and then alert HR if the record still fails, so a new hire never goes missing. Make’s error handler modules do not use credits (Make pricing FAQ).

Decide who gets the alert and what it says: the new hire’s name, the step that failed and a link to the run in Make.

Step 6: How do you test the scenario?

Use Make’s Run once button, then submit a test entry on the form. Check each module’s output in the scenario, then check each destination:

  • The test employee exists in the HRIS with every field filled in and the start date in the right format.
  • The welcome email arrived with the right name, date and sender.
  • The manager task exists with the right owner and due date.

Then test the edge cases the Zap handles: a blank optional field, a name with an apostrophe, and any entry the Zap’s Filter step skips.

Step 7: How do you cut over from the Zap?

Switch the HRIS, email and task modules from the test destinations to the live ones and turn the scenario on. Turn the Zap off the same day. If the form posts to a webhook, move the form to the Make webhook address at the same moment, so every new entry goes to exactly one place.

Watch the first week of live runs in Make’s scenario history and compare them against the new hires HR expected. Leave the Zap off but not deleted until the scenario has a clean week.

Expert Take

The first Zap sets the pattern for every one after it, so we pick it on purpose. A mid-volume HR workflow with one owner gives the team a fast, visible win and a template: write the Zap down, count the credits, build, connect, test, cut over. By the third or fourth workflow, the team knows exactly what a finished move looks like, and the rest of the account goes faster.

Frequently asked questions

How long does it take to move one Zap to Make?

For a four-step Zap with apps Make already supports, the build and first test fit in an afternoon. The side-by-side run takes longer, because it waits for enough live records to compare.

Can I keep the Zap running while I build the scenario?

Yes. Build and test the scenario against test destinations while the Zap keeps running, and turn the Zap off only when you switch the scenario to live.

Why does the Make scenario use more credits than the Zap uses tasks?

Make counts the trigger and its built-in data tools, and Zapier counts neither. Make’s lower price per credit still makes the monthly bill smaller in every example we priced.

Do I need to delete the Zap after the move?

No. Turn it off and keep it until the scenario has run cleanly for a week, then delete it if you want a clean account.

Where 4Spot fits

4Spot Consulting is a Make Certified Partner. We move HR and legal workflows from Zapier to Make one at a time, with error handling and a side-by-side test before each Zap turns off. Read what breaks in a move and how to plan for it, compare every Zapier and Make price tier, start a free Make account, or contact 4Spot Consulting to plan your first 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.