Point it at your BizTalk files. Get back a deployable Azure project, a gap analysis, and a migration report. 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. 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.
main.bicep
Azure deployment template
Production-ready Bicep. 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 Stage 1+2 analysis on the client’s BizTalk export before the kickoff call. Get the complexity score and gap analysis in seconds — enough to write a SOW and identify blockers before you’ve billed a single hour.
Stage 1+2 analysis runs completely free — no license key required.
Get a 3-day trial key with full Standard access. No credit card, no commitment.
Export from BizTalk Administration Console: right-click your application → Export → MSI file to get your .odx, .btm, and .btp files. Then right-click again → Export → Bindings to save BindingInfo.xml. Put everything in one folder and point the tool at it.
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.
Full Standard access. No credit card required.
We’ll reach out when full licenses are available.