After Microsoft confirmed that BizTalk Server 2020 is the final release, many organizations asked the same question: “Do we need to migrate off BizTalk now?”
The short answer is no.
The more important answer is: you need to decide this yourself.
Because after the lifecycle announcement, staying on BizTalk is no longer a default state. It is an explicit choice, and every choice has consequences.
Staying on BizTalk can still be a valid choice
Let’s be clear: moving away from BizTalk immediately is not always the right decision.
Staying makes sense when:
- Your BizTalk environment is stable and low-change
- Integrations are mature and well understood
- Regulatory or validation constraints make changes expensive
- BizTalk mainly supports legacy systems already scheduled for replacement before 2028 or 2030
- You are already actively documenting and planning, thus not postponing
In these scenarios, BizTalk can continue to do what it does best: reliable message-based integration.
There is no technical cliff edge.
But staying on BizTalk comes with conditions
The moment you decide to stay, certain rules apply.
If BizTalk remains in your landscape:
- It should not grow
- It should not become the integration platform for new initiatives
- It should not be the place where future architecture decisions are anchored
Staying is acceptable. Expanding is not.
This is the line many organizations miss.
Clear signals that it’s time to move
For many organizations, the decision is/was already tipping away from BizTalk.
You should assume BizTalk is no longer the right long-term platform if one or more of the following apply:
1. Your integration landscape is still evolving
If you are:
- Introducing new SaaS applications
- Migrating ERP or core systems to the cloud
- Adopting APIs or event-driven patterns
Then BizTalk increasingly becomes a workaround platform instead of an enabler.
2. You are still building new BizTalk integrations
Every new pipeline, orchestration, map, or adapter is an investment in a platform with no future roadmap.
And let's be clear: that is no longer a neutral architectural choice.
3. Skills availability is becoming fragile
BizTalk expertise is not being replenished at the same rate it is disappearing. Developers and architects have most likely already moved on and keep BizTalk as a way to keep their client base.
For those who have not moved on, there is a risk new development is not built with modern tools in mind. Effectively making you pay twice: once for the development now, and due to not being able to migrate the existing tooling, paying again for new development on a successor later on.
When knowledge becomes scarce, change becomes risky — even if the platform itself is stable.
4. You cannot clearly explain your exit strategy
If your answer to “How do we move away from BizTalk?” is vague or undefined, then staying is not a strategy — it is inertia.
The real shift: From “if” to “how”
After the lifecycle announcement, the conversation should no longer be: “Should we ever move away from BizTalk?”
Instead, the conversation becomes:
“How do we do this in a controlled, staged, and responsible way?”
That shift matters.
There is no single migration path
One of the most common mistakes organizations make is assuming there is a single “BizTalk replacement”.
There isn’t.
In practice, we see very different paths, for example:
- Keeping BizTalk temporarily while introducing a new integration platform next to it
- Migrating domain by domain
- Moving simple flows first, complex ones later
- Separating B2B, application integration, and eventing concerns
Each option comes with trade-offs in cost, risk, and speed.
What comes next
In the next article, we will:
- Lay out the main migration options we see in practice
- Explain when each option makes sense
- Introduce a decision matrix to help you choose a path that fits your organization
At this point, the goal is not to migrate faster.
The goal is to migrate deliberately and in a smart way.
Staying on BizTalk can still be a choice.
But not choosing a path forward is no longer one.
