BizTalk Migrate — Overview

How It Works

Point the tool at a folder of BizTalk artifacts — or pass the MSI export directly. The three-stage engine parses, reasons, and builds a deployable Azure project automatically.

UNDERSTAND — Parse

Reads every .odx, .btm, .btp, and BindingInfo.xml. Extracts every shape, adapter, map, port binding, and enterprise integration pattern into a structured model.

DOCUMENT — Analyze

Runs gap analysis against 50+ known BizTalk-to-Logic Apps deltas. Generates an architecture recommendation, complexity score, wave assignment, and per-component migration specification.

BUILD — Generate

Produces a complete, deployable Logic Apps Standard project: workflow, connections, ARM templates, XSLT maps, unit test scaffolding, and a human-readable migration report.

What You Get

workflow.jsonMigrated Logic Apps workflow — stateful, quality-scored

connections.jsonAzure service connections for every adapter

arm-template.jsonProduction-ready ARM deployment template

arm-parameters.jsonARM parameters — fill connection strings, deploy

host.jsonLogic Apps Standard runtime settings

local.settings.jsonApp settings template (Key Vault references)

Artifacts/Maps/Converted XSLT / Data Mapper LML maps

Artifacts/Schemas/Original XSD schemas, copied for reference

tests/Workflow test specs + MSTest scaffold

migration-report.md/htmlGap analysis, effort estimates, actionable fix list

Quality Scoring

Grade	Score	Meaning
A	≥ 90	Deployment-ready
B	75–89	Ready to deploy
C	60–74	Review before production
D/F	< 60	Structural issues — report lists fixes

Why It's Defensible

Migration intelligence is server-side

The reasoning layer — shape mappings, adapter tables, expression translation rules, pattern library — lives in a Cloudflare Worker as encrypted secrets. The npm package contains the client pipeline only. Customers cannot extract the methodology.

⏱

Hard deadline, mandatory market

October 2028 mainstream end-of-support, 2030 extended security patches — no new features, no bug fixes after that. Every BizTalk deployment must migrate regardless. Customers buying extended support simply bought more time — the migration engagement still happens, making the market window larger, not smaller.

∑

Estate multiplier for consultants

A single consultant seat covers an entire client portfolio. Each engagement produces a reusable estate report that becomes the SOW. One license, many billable engagements.

Acquisition Considerations

What transfers

Full TypeScript source, proxy Worker source + KV secrets, npm package, domain, Cloudflare Pages site, GitHub repo, documentation corpus

IP location

Migration reasoning layer in Cloudflare Worker secrets (encrypted at rest). Client pipeline in TypeScript. Reference docs in docs/reference/ (not published to npm)

Tech stack

TypeScript / Node 20 / ESM. Cloudflare Workers (proxy). Vitest (tests). VS Code extension. MCP server (34 tools). GitHub Actions CI.

Integration paths

CLI, VS Code extension, GitHub Actions, MCP server (Claude Desktop / Copilot). All surface the same pipeline. White-label ready.

Distribution

npm global install. VS Code marketplace. GitHub Actions workflow. MCP protocol (Claude, Copilot, any MCP client).

Revenue model

License key per seat (Free / Standard / Premium). Key validation via proxy API. Keys stored in Cloudflare KV — transferable with Worker.

Adapter & Feature Coverage — Auto migrates fully Review migrates with caveats Redesign flagged, path explained in report

FILE / Azure Blob FTP & SFTP HTTP & SOAP WCF-BasicHttp Service Bus SQL Server SMTP Event Hubs IBM MQ / MQSeries SAP (IDocs, BAPIs, RFCs) EDI X12 / EDIFACT / AS2 XSLT / BizTalk Maps (.btm) Decide → If / Switch While loops Delay / Terminate Call Orchestration Sequential Convoy Parallel Actions Local Code Functions (C# stubs) Scope / Error Handling Listen shapes Correlated Receives WCF-WSHttp BRE (Business Rules Engine) Flat File pipelines WCF-NetNamedPipe MSDTC Atomic Transactions MessageBox Pub/Sub WCF-NetTcp

License Tiers

Capability	Free	Standard	Premium
Parse + complexity score	✓	✓	✓
Gap analysis + architecture recommendation	✓	✓	✓
Estate assessment (portfolio, wave planning)	✓	✓	✓
Generate workflow.json, connections, ARM, tests	—	✓	✓
Full deployable Logic Apps Standard package	—	✓	✓
Greenfield NLP (design from plain English)	—	—	✓
50+ pre-built integration workflow templates	—	—	✓

Deployment & Integration Options

CLI npm install -g biztalk-migrate

Run from any terminal. Mac, Windows, Linux. Pass --dir or --from-msi directly.

VS Code Extension

Command Palette migration flow with folder picker, live progress, and gap analysis dashboard panel.

GitHub Actions

Included CI workflow. Add license key as a repo secret — outputs Logic Apps package as a build artifact.

MCP Server

Connects to Claude Desktop or VS Code Copilot via Model Context Protocol. 34 tools, 8 resources, guided prompts.

Capability	Microsoft Starter	BizTalk Migrate
Generate workflow.json from .odx	~	✓
Gap analysis with severity + mitigation	✗	✓
Quality score + Actionable Fix List	✗	✓
ARM template + connections.json + local.settings	✗	✓
C# expression translation + Local Code Function stubs	✗	✓
Estate assessment across entire BizTalk portfolio	✗	✓
Microsoft's own commitment to the tool	Open-source starter only — not a supported product	Commercial product, active development

Common Questions

Doesn't Microsoft already have something for this?

Microsoft ships an open-source console app they describe as a "starter" — explicitly not a supported product. It produces a rough workflow JSON with no quality scoring, no gap analysis, no ARM templates, and no estate assessment. BizTalk Migrate is the commercial-grade tool built for production handoff.

What happens to BizTalk customers after October 2028?

Microsoft is selling extended product support from 2028 through 2030 for customers who miss the mainstream deadline. Security patches only — no bug fixes, no new features. This extends the migration window and the addressable market. Customers buying extended support still need to migrate; they've just bought more time to do it properly.

How does it handle complex orchestrations with C# code?

Inline C# expressions are translated where possible using a built-in expression engine. When a direct translation isn't feasible, the tool generates a Local Code Function stub — a pre-wired .cs file with the correct Logic Apps Standard scaffolding — so a developer pastes in the business logic rather than rebuilding the plumbing from scratch.

Where does the migration intelligence live? Can it be extracted?

The reasoning layer — shape-to-action mappings, adapter tables, XLANG/s expression rules, 50+ gap definitions — lives as encrypted secrets in a Cloudflare Worker proxy. The npm package contains only the client pipeline. Customers and competitors cannot extract the methodology from the published package.

Is the output actually deployable, or does it need significant rework?

Every generated package is quality-scored 0–100 before delivery. Many applications score Grade A (≥ 90) automatically — meaning the workflow.json, connections, and ARM template deploy without modification. Where gaps exist, the migration report's Actionable Fix List tells the developer exactly what to change and why, mapped line-by-line to the generated files.

What's the right entry point for a consulting engagement?

Run biztalk-migrate estate against the client's full BizTalk export folder before the first meeting — no license key required. It returns application inventory, complexity scores, wave assignments, and effort estimates across the entire portfolio in seconds. Enough to scope a SOW before you've billed a single hour.