How to Migrate From Zapier to Activepieces in 2026: Cost Math, MIT Licence, Self-Host Path

Switching from Zapier to Activepieces can lower your monthly bill, but only if your Zaps have several steps and your volume is modest. Zapier bills each successful action step as a task, while Activepieces bills each flow run as one credit. This guide shows the arithmetic, explains what the MIT licence does and does not cover, and walks through a parallel-run migration.

TL;DR: should you switch?

Probably yes if your Zaps run three or more action steps and your volume is in the hundreds to low thousands of runs per month. Activepieces charges one credit per run, so a three-step flow costs one credit where Zapier would charge three tasks. For single-step Zaps the saving is small, so migrate for portability rather than price.

Three rules of thumb:

Multi-step Zaps at low volume: Activepieces usually wins on arithmetic.
Single-step Zaps: the price gap is small, so migrate only if you want to self-host or avoid lock-in.
Full vendor escape: self-hosting means you run a Docker host yourself.

Terminology. A task is Zapier’s billing unit, one successful action step. A credit is Activepieces’ billing unit, one flow run. Docker Compose is a tool that starts several linked containers from one config file, and it is the recommended way to self-host Activepieces.

Prerequisites

You need four things before you start: a Zapier account where you can read task usage, an Activepieces cloud account or a machine with Docker Compose v2, a list of every app your Zaps touch, and your real monthly volume of successful runs. Without the volume figure, the cost comparison is guesswork.

Zapier side: access to task usage history and the ability to pause Zaps without deleting them. Zapier’s task measurement doc explains what counts.
Activepieces side: a free cloud account or a self-host environment. The install overview covers both.
Inventory side: every trigger, action and app, and whether any step uses Zapier’s AI, Code or Paths features.
Volume side: monthly successful runs, not attempts, so you compare like with like.

How the two billing models work

Zapier meters work performed. Activepieces meters work triggered. That single difference drives every number below.

Zapier: tasks per successful step

Per Zapier’s task rates page, a standard action step costs 1 task and a Code step costs 1 task. The trigger costs nothing. Zapier’s built-in tools (Formatter, Paths, Filters, Delay, Looping, Sub-Zaps, Digests, Storage, Tables and Forms) cost 0 tasks. AI steps cost more: a standard model is 1 task, an advanced model 3 tasks and a premium model 5 tasks. Extended runtime costs 1 task per 30 seconds beyond your plan allowance.

Activepieces: credits per run

Per the Activepieces pricing page, a run costs one credit however many steps it has. AI steps are the exception: a fast-model step costs 2 credits, a smart-model step 10 and a frontier-model step 20. Agentic actions cost 1 credit each. On the Plus plan and above, bringing your own AI keys reduces every AI step to 1 credit, which is the detail most cost comparisons miss.

Where n8n fits in the comparison

If you are also weighing n8n, its pricing page bills per workflow execution rather than per step: Starter is $20/mo billed annually for 2.5K executions, and Pro is $50/mo billed annually for 10K executions. Its startup plan page lists a discount for small companies, and its Insights documentation explains how to count your own executions. Self-hosting n8n is covered in its installation docs. Our n8n vs Zapier vs Make comparison covers that model in more depth.

Dimension	Zapier	Activepieces	n8n
Billing unit	Task per successful action step	Credit per run, any step count	Execution per workflow run
Free tier	$0, 100 tasks/mo, two-step Zaps	$0, 1,000 credits/mo, unlimited flows, up to 5 users	Trial only on cloud
Entry paid plan	Professional from $19.99/mo	Plus $20/mo, 10,000 credits/mo	Starter $20/mo billed annually, 2.5K executions
Overage	Move to a higher task tier	$0.007 per credit on Plus and Team	Per n8n’s pricing
Self-host	No	Yes, Docker Compose or Helm	Yes, Community Edition
Licence	Proprietary	MIT core with an `ee/` carve-out	Fair-code

The worked cost example

Take one Zap with one trigger and three standard action steps, running 1,000 times a month. The numbers below are arithmetic from the published rates, not measured results.

Zapier: three successful actions per run, times 1,000 runs, equals 3,000 tasks a month. On Zapier’s pricing page, the allowance slider jumps from 2K to 5K tasks, so 3,000 tasks lands in the 5K tier. Zapier does not show that tier’s dollar price in the pricing extract we checked, so this guide does not state one. What is published: Free is $0 with 100 tasks, Professional starts at $19.99 a month and Team starts at $69 a month.

Activepieces: one credit per run, times 1,000 runs, equals 1,000 credits a month. That matches the Free plan’s 1,000-credit allowance, but the reset cadence needs checking. The pricing page lists Free credits as resetting daily in its comparison table, while its FAQ describes the 1,000 credits as a monthly allowance. Confirm which applies on the live page before you rely on the Free tier. Plus at $20 a month gives 10,000 credits, enough for ten times this volume.

What happens when you add an AI step

Add one fast-model AI step to each run. On Activepieces that is 1 credit for the run plus 2 credits for the AI step, or 3 credits per run and 3,000 credits a month, still inside Plus’s 10,000. On Zapier, the same flow is 3 tasks for the three standard actions plus 1 task for a standard-model AI step, or 5 tasks for an advanced model, which sits in the same 5K tier.

Two caveats. Zapier counts only successful actions, so a failing Zap costs less than the table implies. Activepieces charges per run, so a failing flow still uses a credit.

What “MIT” really covers

Activepieces’ LICENSE file applies the MIT Expat licence to content outside the packages/ee/ directory and packages/server/api/src/app/ee. Those enterprise directories are covered by their own licence, documented in packages/ee/LICENSE. The accurate statement is “MIT core, not the whole repository.”

For a non-developer, that means the automation core you self-host is open source, and the enterprise features are separately licensed. The distinction matters only if you plan to fork or resell the product. It does not change what you can run on your own server.

Step-by-step migration

Activepieces has no one-click export from Zapier, so you rebuild each Zap as a flow. Start with your highest-volume Zap, because that is where you will see the savings first.

Inventory your Zaps. For each one, write down the trigger, every action, every app and its monthly successful-run count from your Zapier task usage.
Check app coverage. Activepieces lists 760+ apps in its docs. Mark each app as supported, partly supported or missing.
Plan the gaps. For a missing app, use the HTTP piece or a webhook against that app’s API. Pieces are open-source TypeScript, so you can read how the existing ones are built.
Set up Activepieces. Either create a cloud account, or run the quick install from the install page: curl -fsSL https://get.activepieces.com | sh. The install needs Docker Compose v2 and uses port 8080 by default. The Docker Compose self-host guide covers PostgreSQL, Redis and the first login. Docker’s own Compose documentation explains the underlying tool.
Rebuild your highest-volume Zap first as one trigger plus its steps. Do not rebuild everything at once.
Test with sample data. Run the same input through the Zapier Zap and the Activepieces flow, then compare the outputs.
Run both in parallel for one to two weeks. Track credit use on Activepieces and task use on Zapier, then compare against the cost table above.
Pause the Zap rather than deleting it, and export your Zapier task usage history before you change plans.
Downgrade or cancel Zapier once the parallel run matches your expectations.

Expected output

After these steps you should have one production flow in Activepieces handling your highest-volume automation, a side-by-side output check against the Zap it replaces, a credit-use figure you can extend to your other Zaps, and a written decision to stay, go hybrid or migrate fully.

Troubleshooting

Three problems come up most often.

Runs stop on the Free plan. Once Free credits are used up, runs wait until the next reset. Check the reset cadence on the pricing page, then either move to Plus or reduce run frequency.
An app is missing. Use the HTTP piece or a webhook against the app’s API, as described in the docs.
The self-host install fails. Confirm Docker Compose v2 is installed, check that port 8080 is free, and confirm PostgreSQL and Redis are running. The install overview lists the prerequisites.

Next steps

If you want a second self-hostable option, compare the Zapier to n8n migration guide, which uses a different licence and billing model. If you are still learning what counts as a task, read the Zapier getting-started guide first. Our Activepieces review covers the wider product, but its pricing may be out of date, so check the live pricing page before deciding.

FAQ

Is Activepieces really free?

The Free plan costs $0 and includes 1,000 credits, unlimited flows and up to five users, on cloud or on-prem hosting. The pricing page describes the credit reset differently in two places, so confirm the cadence before you depend on it. Paid plans start at $20 a month for 10,000 credits.

Is all of Activepieces MIT-licensed?

No. The LICENSE file applies MIT to the core, and the enterprise ee/ directories are covered by a separate licence. For self-hosting the core, that is usually enough. It matters more if you plan to fork or resell.

Can I export my Zaps from Zapier automatically?

No. Activepieces does not offer a one-click import, so you rebuild each Zap as a flow. Inventory first, rebuild the highest-volume Zap first, and run both systems in parallel before you cancel anything.

What is the catch with one credit per run?

Ordinary steps add no credits, because the run is the unit. AI steps are different: a fast model costs 2 credits, a smart model 10 and a frontier model 20, and agentic actions cost 1 credit each. Bringing your own AI keys on Plus and above reduces each AI step to 1 credit.

Verdict

Switch to Activepieces if your Zaps have three or more steps, your volume is in the low thousands of runs a month and every app you need is supported or reachable through HTTP or a webhook. Stay with Zapier if you rely on apps Activepieces does not cover, need enterprise governance today or cannot run a Docker host. The main cost of switching is rebuild time, not licence terms.

How This Guide Was Built

This guide is based on official documentation, pricing pages and the project’s source licence. We did not run the tool hands-on. We fetched the pages on 2026-10-12 and checked each external link for a working response. The worked cost example is arithmetic from the published rates and is labelled illustrative. Where Activepieces’ pricing page describes the Free credit reset differently in two places, we say so instead of choosing one.

ToolBrain — tool reviews, LLM comparisons, and AI workflow guides

Cross-links automatically generated from NoCode Insider.