BizTalk end of life
BizTalk Server End of Life: Plan Your Migration
BizTalk Server 2016 leaves extended support on 11 January 2027, and BizTalk Server 2020 is the final version, supported until April 2030. If BizTalk still runs your payments, orders or partner integrations, now is the time to decide where they go next.
The challenge
What changes when support ends
No more security fixes, and auditors and regulators in banking and insurance treat unsupported middleware as a finding. BizTalk ties you to specific Windows Server, SQL Server and Visual Studio versions, so the whole stack ages together. Upgrading to BizTalk 2020 buys time until 2030 (with paid extended support for non-security fixes from 2028), but it is the last version: the migration still has to happen.
Our solution
A phased migration, planned on facts
We inventory your BizTalk estate, recommend the target platform that fits it, and move interfaces in planned waves while BizTalk keeps running. No big-bang cutover: BizTalk is switched off only when the last interface runs on the new platform.
BizTalk replacement options
MuleSoft, Azure Logic Apps or Apache Camel?
Azure Logic Apps
Microsoft's named successor to BizTalk. Fits when you are Azure-first, most endpoints are Microsoft products, and your team already works in Azure.
MuleSoft Anypoint
Fits when you connect many non-Microsoft systems (core banking, SAP, Salesforce, partners), need full API management and reuse, or must run on-premises or across clouds with Runtime Fabric.
Apache Camel
Fits when you want open source with no runtime licences and have a Java team to own the platform.
Fixed-price package
The BizTalk Migration Assessment
From €7,500
Fixed scope, delivered remotely in 2–3 weeks
The decision usually turns on five questions: your Azure footprint, the share of non-Microsoft endpoints, API management needs, the licensing model you prefer, and your team's skills. The assessment answers them for your estate and gives you the number before you commit.
Who it is for
- Teams on BizTalk Server 2016 facing the January 2027 deadline
- Teams on BizTalk 2020 planning the move before 2030
- Organisations choosing between Logic Apps, MuleSoft and open source
What you receive
- A complete inventory of your BizTalk estate, with a complexity score per interface
- A target-platform recommendation with the reasoning behind it
- A migration plan in waves, including the pilot interface
- An effort and cost estimate for the migration itself
The journey
How a phased BizTalk migration works
Step 1
Inventory
Applications, orchestrations, maps, pipelines, adapters, business rules, schedules and message volumes.
Step 2
Pattern mapping
Each BizTalk artefact mapped to its target equivalent; for MuleSoft: flows, DataWeave transformations, connectors and API policies.
Step 3
Pilot
One representative interface migrated end to end and running in production.
Step 4
Waves
The remaining interfaces grouped by risk and dependency and moved in planned releases.
Step 5
Decommission
BizTalk switched off once the last interface runs on the new platform.
Why Leadex
Why Leadex Systems for your BizTalk migration
Integration delivery since 2008, with offices in the UAE, Saudi Arabia, Germany and Cyprus.
Platform-neutral advice
We assess Logic Apps, MuleSoft and Apache Camel and recommend the one that fits; most of our own delivery is MuleSoft.
Certified MuleSoft team
10 certified MuleSoft architects and 70+ MuleSoft certified developers, plus Apache Camel delivery for teams that prefer open source.
Banking and payments experience
Payment and banking integrations in production, where downtime and audit findings are not an option.
Known cost up front
A fixed-scope assessment that ends with an effort and cost estimate for the migration.
References
Integration projects we run in production
SWIFT payment integrations
- 3× faster onboarding of new payment corridors
Western Union integration
- International payouts in minutes, not days
Legacy systems connected to Salesforce
- Core systems exposed through MuleSoft APIs
BizTalk support dates: Microsoft lifecycle pages for BizTalk Server 2016 and 2020, and Microsoft's BizTalk Server product lifecycle update (published in Pacific Time).
Frequently asked questions
When is BizTalk Server end of life?
BizTalk Server 2016 extended support ends on 11 January 2027. BizTalk Server 2020, the final version, has mainstream support until 11 April 2028 and extended support until 9 April 2030 (Microsoft lifecycle, Pacific Time).
Is BizTalk Server being discontinued?
Yes. Microsoft has said BizTalk Server 2020 is the final version and names Azure Logic Apps as its successor. No new BizTalk version is planned.
Can we simply upgrade to BizTalk Server 2020?
Yes, and it is supported until April 2030. But it is the final version, so an upgrade postpones the migration rather than replacing it. If you upgrade, plan the migration in parallel.
What is the best BizTalk replacement?
It depends on your estate. Azure Logic Apps fits Azure-first, Microsoft-heavy landscapes; MuleSoft fits many non-Microsoft systems and strong API management needs; Apache Camel fits open-source preferences with a Java team. The assessment compares them for your interfaces.
Do we have to rebuild every interface?
The logic, message formats and partner agreements carry over; the implementation is rebuilt on the target platform. The assessment shows which interfaces are simple to move and which need redesign.
Can BizTalk and the new platform run side by side?
Yes. That is how a phased migration works: interfaces move one wave at a time, and BizTalk is switched off only at the end.
How long and how much does a BizTalk migration take?
It depends on the number and complexity of interfaces. The assessment, from €7,500, ends with a plan in waves and an effort and cost estimate, so you know both before you commit.
Next step
Request a BizTalk migration assessment
Tell us roughly how many BizTalk applications you run and your target date. A senior architect replies within one business day.
- A reply from a senior architect within one business day
- A first view of your options and the 2027 / 2030 deadlines
- A fixed-scope assessment proposal