How Workflow Migration Agent Maps and Scores Each Step

Your sales team has 47 deals in the proposal stage. 12 have not had contact in 5+ days. Three have gone completely dark. Which ones are at risk — and which ones just have a slow procurement process? A rep answering this question manually checks Notion, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 30–60 minutes per cycle of triage before any follow-up happens.

The cost is not just time — it is revenue leakage. Deals slip because signals were missed. Pipeline reviews rely on data that was accurate two days ago. Scoring criteria drift between team members, and the CRM becomes a lagging indicator rather than an operational tool. Workflow Migration Agent automates the workflow migration workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Three Agents. Full Analysis. Before You Start Building.

The Workflow Migration Agent pipeline runs 3 agents in sequence. The Cartographer pulls data from Notion, and The Briefer delivers the output. Here is what happens at each stage and why it matters.

• The Cartographer (Reasoning (Tier 1)): Maps each source step to its n8n equivalent.
• The Estimator (Reasoning (Tier 1)): Scores migration complexity 1–10 across four criteria: step count, native node availability, custom logic requirements, and data transformation depth.
• The Briefer (Reasoning (Tier 1)): Generates the Migration Intelligence Brief: executive summary, step-by-step mapping table, incompatibility flags, recommended build sequence, and effort estimate.

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• 19-node n8n workflow (.json) — you own it
• 3 tested agent system prompts (ITP-validated)
• Error handling matrix (18 failure modes documented)
• Dependency matrix with ITP-measured costs
• README with sample curl commands
• Zapier + Make.com auto-detection

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Workflow Migration Agent adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Workflow Migration Agent execution flow.

Step 1: The Cartographer

Tier: Reasoning (Tier 1)

The pipeline starts here. Maps each source step to its n8n equivalent. Zapier triggers, actions, and filters are matched to n8n-nodes-base.X counterparts with a confidence rating. Unsupported steps are flagged with recommended workarounds.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Estimator

Tier: Reasoning (Tier 1)

Scores migration complexity 1–10 across four criteria: step count, native node availability, custom logic requirements, and data transformation depth. The Migration Workload Score tells you exactly how long the build will take before you start.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 3: The Briefer

Tier: Reasoning (Tier 1)

This is the final deliverable — what lands in your inbox or dashboard. Generates the Migration Intelligence Brief: executive summary, step-by-step mapping table, incompatibility flags, recommended build sequence, and effort estimate. Structured JSON output — ready to hand to your engineering team.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

The Researcher costs more than the Judge — web search injects 30K-40K tokens into context. Actual cost: $0.125 vs our initial estimate of $0.064. Nearly double. That experience is why every published cost figure comes from ITP measurements, never from back-of-envelope math.

— ForgeWorkflows Engineering

All values below are from ITP testing — not estimates, not projections. Measured across 20 test workflows spanning Zapier and Make.com.

The primary operating cost for Workflow Migration Agent is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Workflow Analysis: $0.092/workflow analysis (ITP-measured avg, $0.045–$0.148 range). This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour for a sales ops analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is Under $1/month for typical use, depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 18/20 PASS (90%). These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

9 files. Workflow, prompts, error handling, and complete documentation.

When you purchase Workflow Migration Agent, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• LICENSE.md — License terms
• README.md — Setup and configuration guide
• dependency_matrix.md — Third-party service dependencies
• error_handling_matrix.md — Error handling reference
• system_prompts/briefer.txt — Briefer system prompt
• system_prompts/cartographer.txt — Cartographer system prompt
• system_prompts/estimator.txt — Estimator system prompt
• workflow_migration_agent_v1.json — n8n workflow (main pipeline)

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Workflow Migration Agent is built for Revops, Operations teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a revops or operations function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Zapier or Make.com account (export only)
• You have API credentials available: Anthropic API
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not auto-generate an n8n workflow JSON
• Does not connect to Zapier or Make.com APIs
• Does not require n8n to be running at migration analysis time

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not auto-generate an n8n workflow JSON

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not connect to Zapier or Make.com APIs

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not require n8n to be running at migration analysis time

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Workflow Migration Agent bundle is designed for the following tools: n8n, Zapier (export only), Make.com (export only). Here is the recommended deployment path:

1. Step 1: Export your workflow. Export your Zapier Zap or Make.com scenario as JSON.
2. Step 2: POST to webhook. Send the export JSON to the Workflow Migration Agent webhook endpoint.
3. Step 3: Receive Migration Intelligence Brief. Get back a complete step mapping, MWS complexity score, and recommended migration sequence.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Workflow Migration Agent product page for full specifications, pricing, and purchase.