BizTalk has an end date. Your plan should too.
BizTalk Server 2020 mainstream support ends in April 2028 and extended support in April 2030. A well-run migration takes 12 to 18 months. We start with a fixed-price migration assessment and move your flows to Azure in low-risk waves.
Mainstream ends
Apr 2028
Extended ends
Apr 2030
- OrchestrationsLogic Apps
- MessageBoxService Bus
- Maps & schemasIntegration Account
- BAMAzure Monitor
- EndpointsAPI Management
- Mainstream support ends
- April 11, 2028
- Extended support ends
- April 9, 2030
- Typical migration
- 12–18 months
- Entry point
- Fixed-price migration assessment
BizTalk Migration
Why not lift-and-shift
Copying every orchestration moves your technical debt to the cloud.
Many flows are unused or duplicated and should be retired, not migrated.
Batch file drops can become APIs and events that Dynamics 365 and AI agents can use.
Monitoring and cost need to be designed up front, not discovered later.
At a glance
Migration assessment includes
- Inventory of applications, orchestrations, ports and dependencies
- Rationalization: retire, simplify, modernize
- BizTalk → Azure mapping for every component
- Target Azure Integration Services architecture
- Wave-by-wave migration plan with effort estimates
- Monitoring, alerting and cost model
Five steps, no big bang
- 1
Inventory
Every application and dependency, with real usage.
- 2
Rationalize
Retire, simplify, modernize.
- 3
Design
Azure reference architecture.
- 4
Migrate in waves
In parallel until each wave is proven.
- 5
Decommission
Switch off servers and licenses.
FAQ
Questions we often hear.
Where do BizTalk components go in Azure?+
Orchestrations → Logic Apps; MessageBox pub/sub → Service Bus topics; maps → Integration Account or Functions; BAM → Azure Monitor; endpoints → API Management. The assessment decides per flow.
Can we keep BizTalk running during the migration?+
Yes. Each wave runs in parallel with BizTalk until it’s proven, then the old flow is switched off.
Source for the dates?+
Microsoft Lifecycle policy for BizTalk Server 2020.
Contact
Let’s talk about BizTalk Migration.
A few lines about your systems and what’s not working is enough. We reply personally.
- 01We read every message personally.
- 02A 30-minute call to understand your context.
- 03A clear proposal, fixed scope whenever possible.