Point it at your BizTalk files — orchestrations, maps, pipelines, bindings. In under 5 minutes, get back a deployable Azure Logic Apps Standard project with workflow.json, gap analysis, and a quality-scored migration report. Supports 30+ adapters and all 18 Hohpe & Woolf enterprise integration patterns. No deep Azure expertise required.
npm install -g biztalk-migrate · node 20+
Node.js 20+ and npm. No Azure SDK, no Python environment, no complex setup.
Point it at your BizTalk export folder or MSI file. Your artifacts never leave your machine.
Everything in that folder deploys directly to Azure Logic Apps Standard.
workflow.json
Your migrated Logic Apps workflow
Every orchestration shape mapped to its Logic Apps equivalent. Stateful, quality-scored, deployment-ready.
connections.json
Azure service connections
Service Bus, Storage, SFTP, SQL — every adapter mapped to its Logic Apps connector.
host.json
Runtime configuration
Logic Apps Standard runtime settings, pre-configured for production workloads.
arm-template.json
Azure deployment template
Production-ready ARM template. One az deployment group create provisions everything.
migration-report.md
Gap analysis + effort estimates
What migrates automatically, what needs manual work, and how many days each gap takes. Share with your client before touching Azure.
Quality Scoring — Every Workflow Graded 0–100
Target Grade B or higher before handing off to a customer. The tool tells you exactly what to fix if the score is lower.
↗ Adapters: FILE, FTP, SFTP, HTTP, SOAP, Service Bus, SQL, SMTP, Event Hubs, Azure Blob, IBM MQ, SAP, EDI/X12/EDIFACT/AS2
↗ Receive shape → trigger (type maps to adapter)
↗ Decide shape → If / Switch action
↗ While loop → Until action (condition auto-inverted)
↗ Transform + XSLT maps → Transform action
↗ Delay shape → Delay action
↗ Terminate shape → Terminate action
↗ Scope + exception handling → Scope + FAILED runAfter branch
↗ Call Orchestration → child Workflow action
↗ Sequential Convoy → Service Bus sessions
↗ Parallel actions → concurrent runAfter chains
WCF-NetNamedPipe
No Azure equivalent. Architectural redesign required — HTTP, Service Bus, or Azure Relay.
MSDTC atomic transactions
No 2-phase commit in Azure. Saga/compensation pattern required.
WCF-NetTcp (binary TCP)
Wrap in Azure Functions or redesign as HTTP REST.
MessageBox pub/sub
Redesigned as Service Bus Topics + Event Grid.
The migration report categorizes every component: direct mappings, partial mappings, and gaps requiring redesign. You’ll know exactly what needs attention before writing a line of JSON.
The migration report tells you exactly which enterprise integration patterns your BizTalk application uses, whether they migrate automatically, and what needs redesign before you touch Azure.
Content-Based Router
If / Switch action
Message Translator
Xslt / Data Mapper action
Message Filter
Condition + terminate branch
Request-Reply
Request trigger + Response
Wire Tap
Parallel ServiceProvider send
Dead Letter Queue
Scope + FAILED runAfter
Claim Check
Azure Blob pass-through
Message Enricher
HTTP call-out + Compose
Sequential Convoy
Service Bus sessions
Splitter
ForEach (concurrency: 1)
Aggregator
ForEach + Array variable
Scatter-Gather
Parallel actions + collect
Composed Msg Processor
ForEach + Switch + aggregate
Parallel Convoy
SB subscriptions + state store
Suspend with Retry
Until loop (no native Suspend)
Process Manager
Stateful + child Workflow
Message Broker
SB Topics + Event Grid
Compensation
Saga / undo workflows
Run the estate command across the client’s entire BizTalk export before the kickoff call. Get complexity scores, wave assignments, and effort estimates for every app in seconds — enough to write a SOW and identify blockers before you’ve billed a single hour.
Estate analysis runs completely free — no license key required.
Estimates based on typical BizTalk migration consulting engagements. Run biztalk-migrate estate against your real apps for exact numbers.
Your Environment
Mixed: some simple orchestrations, some complex — typical enterprise estate
⚠ These are estimates based on typical engagements.
Days/orch: Simple=4d · Mixed=12d · Complex=25d
Maps: 1d each. Source: BizTalk migration consulting benchmarks.
Manual Migration Cost
Low estimate (0.8×) — High estimate (1.2×)
BizTalk License Cost Until Oct 2028
Every month you delay, you pay for a platform you'll have to leave anyway.
Total Cost of Doing Nothing
Manual migration + remaining BizTalk license spend
↳ Get your actual numbers
Outputs real complexity scores, wave assignments, and effort estimates for every app in your estate — not guesses.
Join the waitlist to be first in line for access.
BizTalk Migrate was built by Jon Levesque, a former executive at Microsoft and DocuSign with deep roots in enterprise integration. After watching teams spend 6–18 months manually migrating single BizTalk applications — writing Logic Apps JSON by hand, reverse-engineering binding files, and discovering MSDTC gaps in production — he built the tool he wished existed.
The October 2028 BizTalk mainstream support deadline is real. Extended patches run to 2030. But every month you wait is another month of mounting technical debt on a platform Microsoft has stopped investing in. The enterprises Jon has worked with don't have time for a manual process that takes a team of developers 18 months per wave.
BizTalk Migrate exists to compress that timeline. An experienced consultant can size an estate of 50 orchestrations in a single morning. A migration wave that used to take 18–24 developer-days can be reduced to days of review and deployment.
Background
Contact
me@jonlevesque.comPackage
npm install -g biztalk-migrate
There are open-source BizTalk tools. They're a great starting point for a developer experiment.
They're not what you stake a production migration on.
e.g. BizTalkMigrationStarter (MIT)
Structural translation only — parses shapes and emits JSON. No AI reasoning, no semantic understanding of what the migration actually means.
No quality scoring — you don't know if the output is deployable until you try to deploy it.
Windows-only — .NET Framework 4.7.2 required. Doesn't run on Mac or Linux CI pipelines.
No support — GitHub issues, community PRs. Nobody to call when the output breaks in prod at 2am.
MIT licensed — fine for experimentation. Not appropriate for billable client deliverables or regulated environments.
No gap analysis, no report — outputs JSON and stops. No migration spec, no remediation guidance, no effort estimate.
biztalkmigrate.com
AI-enriched migration — Claude reasons about your orchestrations, translates XLANG/s expressions, resolves mapping gaps, and produces semantically correct workflows — not just shaped JSON.
A–F quality grading — every output is scored against 6 dimensions. You know it's deployment-ready before you touch Azure.
Cross-platform — TypeScript/Node.js. Mac, Windows, Linux. Runs in any CI pipeline. No .NET Framework, no Visual Studio.
Commercial support — direct email, SLA-backed. Consultants can resell it. Enterprises can rely on it.
Complete deliverable — migration report (MD + HTML), gap analysis, architecture recommendation, ARM/Bicep templates, full VS Code workspace, deployment scripts. Not just a workflow.json.
0 bytes of your BizTalk data leaves your machine — 100% local processing. Only license validation touches the network.
We respect open-source work — free tools help the community and we've learned from them. But migrating enterprise BizTalk estates is a regulated, billable, career-defining activity. Use the right tool for the job.
Two options. Option A (easiest): Export the MSI directly from BizTalk Administration Console (right-click your application → Export → MSI file) and pass it straight to the tool with --from-msi ./MyApp.msi — no manual extraction needed. Option B: Extract the MSI yourself, then right-click → Export → Bindings to also save BindingInfo.xml, put everything in one folder, and use --dir ./your-folder.
No. 100% local processing. Your .odx, .btm, .btp, and BindingInfo.xml files are parsed entirely on your machine. Only license validation makes a network call — your BizTalk artifacts never leave your environment.
Node.js 20+ and npm. That’s it. No Azure CLI required to run the migration (you’ll need it to deploy the output). No Python, no .NET SDK, no Visual Studio.
Logic Apps Standard (single-tenant). Always stateful workflows — required for BizTalk migration scenarios involving long-running transactions, message correlation, and run history. The Bicep template provisions everything at the correct tier.
The tool handles these gracefully. WCF-NetNamedPipe and MSDTC distributed transactions have no direct Logic Apps equivalent — the migration report flags them as requiring redesign, estimates the effort, and describes the recommended pattern (Azure Relay, Saga/compensation). The tool generates the surrounding workflow correctly and clearly marks the gaps. You’ll know exactly what needs human attention before touching Azure.
BizTalk Migrate is a Node.js CLI tool (npm install -g biztalk-migrate) that automates the migration of Microsoft BizTalk Server applications to Azure Logic Apps Standard. It works in three stages: UNDERSTAND — parses .odx orchestrations, .btm maps, .btp pipelines, and BindingInfo.xml bindings; DOCUMENT — generates a gap analysis and architecture recommendation; BUILD — uses AI reasoning via Claude to generate a deployable Logic Apps Standard project with workflow.json, connections.json, ARM/Bicep templates, and a quality score. The entire process runs locally on your machine in under 5 minutes.
Manual BizTalk migration typically costs $1,500–$2,000 per person-day, with a single application taking 15–30 person-days for a mixed-complexity estate. That's $22,500–$60,000 per application before Azure infrastructure costs. BizTalk Migrate compresses most of that work to hours of review and deployment configuration per application. Use the ROI calculator on this page to enter your own staff rate, application count, and remaining BizTalk license cost to calculate your specific business case.
Yes. BizTalk Migrate runs on Windows, macOS, and Linux. It requires Node.js 20+ and npm — nothing else. The migration analysis and output generation work on any platform. You do not need a Windows machine, a BizTalk Server installation, or a .NET SDK to run the tool. This makes it suitable for consulting engagements where the consultant uses a Mac and the client runs Windows infrastructure.
Full Standard access. No credit card required.
We’ll reach out when full licenses are available.