There is a specific moment in the life of every Zapier-heavy company when the CFO opens the invoice, looks at the line for "Zapier Team — $499/month," and asks why nobody migrated this to n8n. That moment, almost always, lands somewhere around 60,000 tasks per month. Below that, Zapier is defensible. Above it, the arithmetic stops working and you have to explain yourself.

The Pipeline That Makes the Arithmetic Real

Let's pin this to a concrete workload. A ten-step pipeline running 200 times per day. The pipeline is a standard inbound-lead enrichment-and-routing flow you'd see at any SaaS company between Series A and Series C:

1. Trigger: webhook from a marketing form fires when someone fills out the "Request a Demo" form.
2. Step 2: normalize the payload — clean the email, strip tracking params from the URL, parse the company name out of free-text.
3. Step 3: call Clearbit (or Apollo or ZoomInfo) for firmographic enrichment — company size, industry, funding stage.
4. Step 4: look up the lead in Salesforce to detect existing contact or account.
5. Step 5: deduplicate logic — if the contact already exists and was contacted in the last 14 days, route to existing owner; otherwise continue.
6. Step 6: score the lead with an LLM call (Claude or GPT-4o or similar) using the enriched data and a scoring rubric.
7. Step 7: territory and round-robin assignment to a Sales Development Rep based on company size and region.
8. Step 8: create or update the lead/contact in Salesforce with all enriched fields and the assigned owner.
9. Step 9: post a formatted notification to the SDR's Slack channel.
10. Step 10: log the outcome to a Postgres analytics warehouse for downstream reporting.

Each step counts as one "task" or "operation" or "execution" depending on the platform's counting model. Some platforms (Zapier) count branches and filters as separate tasks. Some (Make) count every module call. Some (n8n) count the workflow execution as one unit regardless of how many nodes ran.

Volume: 200 runs/day × 30 days = 6,000 runs/month. Steps per run: 10. So:

• Zapier task count: 6,000 × 10 = 60,000 tasks/month. Some filters or paths may count too, conservatively call it 60,000-65,000.
• Make operation count: approximately 6,000 × 10 = 60,000 operations.
• n8n execution count: 6,000 executions (one per run, regardless of node count).

This is a real, common, defensible workload. It is not exotic. Every well-funded B2B SaaS in 2026 has something like it. And it is precisely at this volume that the platform cost diverges by an order of magnitude.

The Zapier Price Tag at 60,000 Tasks

Zapier's pricing in 2026 (verified against their published page, May 2026):

• Free tier: 100 tasks/month. Useful for the first three personal zaps and nothing else.
• Professional: $19.99/month for 750 tasks. Scales up to 2,000 tasks at this tier.
• Professional, larger task tiers: 5,000 tasks ~$73/month, 10,000 tasks ~$133/month, 20,000 tasks ~$193/month, 50,000 tasks ~$398/month.
• Team: starts at $499/month for 50,000 tasks. Includes shared zaps, premier support, advanced admin. Larger tiers scale into the thousands per month.
• Enterprise: custom, typically starts $1,500+/month with SSO, audit, SCIM.

For our 60,000-task workload, Zapier requires a Team-tier plan with at least 75,000 tasks. The list price in May 2026 is roughly $599-$799/month, depending on annual vs monthly billing and whether your account is on grandfathered pricing. Annualized: $7,200-$9,600/year.

Add Premium app fees (some connectors like Salesforce, Webhooks by Zapier, Code by Zapier, Looping by Zapier require Team tier or higher anyway), and you're committed.

The n8n Cloud Pro Price Tag for the Same Workload

n8n's pricing model counts executions, not tasks. The 10-step pipeline running 6,000 times/month is 6,000 executions, not 60,000.

• n8n Cloud Pro: $60/month for 10,000 executions. Our workload at 6,000 executions fits comfortably under the cap.
• Annualized: $720/year.

Same workload. Same ten steps. Same 6,000 runs. n8n: $720/year. Zapier: $7,200-$9,600/year. The ratio is 10-13x. The CFO can do this math in their head.

The Self-Hosted n8n Price Tag for the Same Workload

If you're already self-hosting n8n on a $15/month VPS (see Lesson 2 for the break-even), this workload runs at marginal cost zero. Total infrastructure: $180/year, plus the ~32 hours/year of operational attention. At a $100/hour ops cost, that's $3,200 of attention plus $180 of infra = $3,380/year.

Self-hosted is cheaper than Zapier, even when you fully account for ops time. The savings narrow versus Cloud Pro because n8n Cloud Pro is already so cheap, but versus Zapier Team, self-host is dramatically cheaper.

The Make Price Tag for Completeness

Make's operation pricing for 60,000 operations:

• Make Core ($9/month, 10,000 ops): insufficient for this volume.
• Make Pro ($16/month, 10,000 ops with priority + more features): insufficient.
• Make Teams ($29/month, 10,000 ops with team features): insufficient.
• Higher Make tiers: 100,000 ops ~$57/month, 500,000 ops ~$148/month, 1M ops ~$272/month (approximate 2026 pricing — Make's per-op cost is dramatically lower than Zapier).

For 60,000 ops, Make's appropriate tier is around the 100,000-ops bucket at ~$57/month, $684/year. Slightly cheaper than n8n Cloud Pro. Roughly 10-15x cheaper than Zapier Team.

The Side-by-Side Arithmetic

Same 10-step pipeline, 200 runs/day, 6,000 runs/month, 60,000 task-equivalent events:

• Zapier Team (75K tasks): ~$599-$799/month, $7,200-$9,600/year
• Make (100K ops): ~$57/month, $684/year
• n8n Cloud Pro (10K executions, fits 6K): $60/month, $720/year
• n8n self-hosted ($15 VPS + 32 hr/yr ops): $180 infra + $3,200 ops = $3,380/year

Zapier is the most expensive by a factor of 10-14x over Make and n8n Cloud Pro. Self-hosted is somewhere in the middle once you price in operational attention.

The 60,000-task threshold is the threshold at which the choice of platform becomes a six-figure decision over a three-year horizon. Zapier Team at $599/month is $21,564 over three years. Make Pro at $57/month is $2,052. The delta is $19,512 — for the same workflow, the same uptime, the same results.

The Moment the CFO Asks "Why Didn't You Migrate?"

This moment, in our experience, comes within three months of the company crossing the 50,000-task tier on Zapier. The trigger is usually one of three events:

1. The annual subscription renewal lands on the CFO's desk. $9,000+ for "automation tooling" raises questions that $1,200 didn't.
2. The CFO is benchmarking SaaS spend against peer companies and a peer at a CFO summit mentions running their automation on n8n for "basically free."
3. Engineering is asked to integrate something new and notices the existing Zapier surface area, asks about the alternatives, runs the same arithmetic you just read, and brings it to leadership.

The question lands on whoever owns automation. Often that's the RevOps lead or the Marketing Ops lead or the Founder. The defensible answer has three parts:

1. "Zapier was the right choice when we started" — connector coverage, no-code, fast time-to-value at the time when volume was 2,000 tasks/month and the tradeoff was net positive.
2. "Here's the threshold we hit" — 60,000+ tasks where the per-task arithmetic flips against us by 10x.
3. "Here's the migration plan" — a specific, sequenced, cost-justified plan to move the high-volume workflows to Make or n8n while keeping the low-volume, niche-connector workflows on Zapier.

The indefensible answer is "we've always used Zapier." That answer signals you haven't done the arithmetic. The CFO did.

Why the Migration Isn't Trivial (and Why It's Still Worth It)

Migrating a 10-step Zapier zap to n8n or Make is not a copy-paste. The migration has three real costs:

1. Re-implementation effort

Each zap has to be rebuilt in the target platform. For a 10-step zap, that's typically 2-4 hours of work — read the existing zap, map each step to a target-platform module, recreate the data transformations, set up the trigger, test against staged data, deploy. For 10 zaps of that complexity, budget 20-40 hours.

2. Credential and connection setup

Every connected app needs to be re-authenticated in the new platform. OAuth flows, API keys, webhook endpoints. For 15-20 SaaS apps across your zaps, this is another 4-8 hours of administrative work — often gated by waiting for app-admin approvals.

3. Verification and dual-run

Best practice is to dual-run the old and new workflows for 1-2 weeks, comparing outputs, before cutting the old workflow off. This catches subtle differences in error handling, retry semantics, and edge-case behavior that you didn't notice on day one. Dual-run costs you double execution count on both platforms during the window.

Total migration cost for a 10-zap portfolio: roughly 40-80 hours of effort, plus dual-run platform overhead. At $100/hour that's $4,000-$8,000 of one-time migration cost.

The payback period

At our 60,000-task example, Zapier is ~$7,200-$9,600/year and n8n Cloud Pro is $720/year. Annual savings: $6,500-$8,900. Migration cost: $4,000-$8,000. Payback period: 6-15 months.

Anything above 18 months of expected continued use makes the migration a clear win on arithmetic alone. Below 18 months, it's a closer call. The threshold is real but it's worth running the specific math for your specific situation.

The Hybrid Migration Strategy (Highest ROI)

The naive migration plan says "move everything off Zapier." That's almost always wrong. The high-ROI plan is hybrid:

Step 1: Inventory by task volume

Run a 90-day task report from Zapier. Rank your zaps by tasks consumed. The Pareto distribution will be sharp — typically 2-3 zaps consume 70-80% of your tasks, and 30-50 zaps consume the rest.

Step 2: Migrate only the top zaps

Migrate the high-volume zaps to Make or n8n. These give you the bulk of the cost savings. A 70% cut on a $599/month Zapier bill yields ~$420/month of savings from migrating 2-3 zaps. The remaining low-volume zaps stay on Zapier where their cost is small and the connector friction is highest.

Step 3: Right-size the Zapier plan

With the high-volume zaps gone, your Zapier task consumption drops from 60K to 15-20K. Downgrade from Team ($499+/month) to the appropriate Professional tier (~$133-$193/month). The remaining Zapier bill is for what Zapier is genuinely best at: niche connector coverage, friendly UX for small workflows.

Step 4: Establish operational discipline

Now you're running two platforms. Document which platform owns which workflows. Standardize secrets management. Make sure observability covers both. The operational overhead of two platforms is real but bounded — see Lesson 2 for the on-call discussion.

The hybrid arithmetic

For the 60,000-task example, hybrid migration:

• Top 3 zaps moved to n8n Cloud Pro: $60/month for that platform.
• Remaining low-volume zaps stay on Zapier Professional (10K tasks): $133/month.
• Total monthly: $193/month, $2,316/year.
• Versus Zapier Team alone: $599-$799/month, $7,200-$9,600/year.
• Annual savings: ~$4,900-$7,300.

And you've kept the connector coverage and easy-handoff UX of Zapier for the workflows where those properties are most valuable.

When Zapier Is Still the Right Answer at 60,000 Tasks

There are scenarios where staying on Zapier Team is defensible even at 60,000 tasks:

1. Your team has zero engineering capacity and the migration cost of $4,000-$8,000 of someone's time exceeds two years of Zapier-vs-alternative savings. This is rare but real for very small ops teams.
2. Most of your tasks come from niche connectors that don't exist on Make or n8n. Moving the zaps means losing the connector. A Zapier connector to a niche regional CRM that has no n8n equivalent may be worth the premium.
3. Your usage is volatile and seasonal — Zapier's task pooling and ease of plan changes is genuinely valuable if your volume swings 5x between seasons. n8n's fixed plans are less forgiving.
4. You're inside an enterprise IT structure where Zapier is on the approved-vendor list and Make/n8n aren't. The procurement cost of getting alternatives approved may exceed the cost difference. Worth pushing on but not always worth fighting.

If none of these apply, you should be migrating. If at least one applies, you can defend the status quo to the CFO with a specific argument.

The 90,000-Task Tipping Point Inside Zapier Itself

Inside Zapier's own pricing, there's a second tipping point at around 90,000-100,000 tasks where the Team-tier price starts approaching what Enterprise might cost with negotiation. At that point:

• You can negotiate with Zapier's sales team for an Enterprise contract with volume discount.
• You can migrate.
• You should at least price both options.

The lesson here is that the 60,000 threshold isn't the last call. There's a second call at 90,000-100,000, a third at half a million if you ever get there. Each tier change is a forcing function to revisit the build-vs-buy question.

Three Real Migration Stories (Composites)

Story 1: The Series B SaaS that saved $80K over three years

A Series B B2B SaaS company crossed 70,000 Zapier tasks/month in early 2024. The RevOps lead, prompted by the CFO at quarterly review, audited the zaps and found 4 high-volume zaps consuming 55,000 of the tasks. They migrated those 4 to n8n self-hosted (the company had engineering capacity), kept ~25 low-volume zaps on Zapier Professional. Pre-migration cost: $599/month. Post-migration cost: ~$133 Zapier + ~$40 n8n hosting = $173/month. Annual savings: $5,112. Over three years and growing volume: $80K+. Migration effort: ~60 engineering hours, paid back in five months.

Story 2: The mid-market company that stayed on Zapier and justified it

A mid-market company at 65,000 Zapier tasks/month evaluated migration in 2025. Their workflow mix was unusual: most tasks consumed niche regional CRM connectors that Zapier supported but Make and n8n didn't. They estimated the cost of building those connectors as custom integrations on n8n at 200+ hours, plus ongoing maintenance. The migration arithmetic didn't pencil. They stayed on Zapier Team, negotiated a 15% discount with Zapier on annual commitment, and documented the rationale. The CFO accepted it because the analysis was specific and the alternative was costlier.

Story 3: The startup that migrated too late

A startup grew through 60K, 80K, 120K tasks on Zapier between 2023 and early 2026 without ever revisiting the cost. By the time the CFO flagged it, they were spending $1,800/month on Zapier — $21,600/year. The company had also added 50+ zaps in the meantime, making the migration substantially larger than it would have been at the 60K threshold. The migration ultimately took 200+ hours over a quarter, by which point they had paid Zapier roughly $40K more than they would have if they'd migrated when the threshold first hit. The lesson: revisit the platform cost annually, and don't let the operating cost run for years without an audit.

The CFO-Defensible Narrative

When the CFO asks why you're on Zapier Team, the answer should not be "we like Zapier." It should be:

"We chose Zapier in [year] for [specific reason — connector coverage, team skill, time-to-value]. As of [recent quarter], we've crossed [task threshold] where the per-task arithmetic against Make/n8n becomes [X]:1. We've evaluated migration. Here's the plan: [hybrid plan, payback period, specific actions, owner, deadline]. Net annual savings: [$Y]. Migration cost: [$Z]. Payback: [months]."

That narrative survives any CFO review. It's specific, arithmetical, and shows you've done the work. The narrative that doesn't survive is: "Zapier is fine."

Key Takeaways

• The 60,000-task threshold is real. At ~$599-$799/month on Zapier Team for that volume, you're paying 10-14x what Make or n8n Cloud Pro charges for the equivalent workload.
• A 10-step pipeline running 200 times/day = 60K tasks/month. This is a standard, defensible B2B SaaS lead-routing workload, not an exotic case.
• The platform arithmetic at this threshold: Zapier Team $7.2K-$9.6K/year; Make ~$684/year; n8n Cloud Pro $720/year; self-hosted n8n $3,380/year fully loaded.
• The CFO asks "why didn't you migrate?" within 3 months of crossing the 50K-task tier. The trigger is the renewal invoice, peer benchmarking, or engineering raising the question.
• Migration cost for a 10-zap portfolio is roughly $4K-$8K of effort. Payback period is 6-15 months at the 60K-task volume. Above 18 months of expected continued use, migration is a clear arithmetic win.
• Hybrid migration is the highest-ROI strategy. Migrate the top 2-3 high-volume zaps (capturing 70-80% of cost) to Make or n8n; keep the long-tail of low-volume zaps on Zapier Professional. Annual savings ~$4,900-$7,300 at the 60K-threshold example.
• Staying on Zapier is defensible in four specific scenarios: zero engineering capacity, niche-connector dependency, volatile/seasonal volume, or enterprise procurement lock-in. Otherwise migrate.
• The CFO-defensible narrative is specific and arithmetical: chose Zapier in year X for reason Y; crossed threshold Z; here's the plan with payback period. "We like Zapier" is not a narrative.