Orchestrations are often the engine room of a BizTalk solution. They do far more than just pass data along. They route, transform, validate, retry, catch exceptions, and sometimes even embed critical business rules. So when it comes time to replace them, you are not just refactoring a workflow. You are unpicking the operational logic of your organisation. 

Whether you are moving to Azure Logic Apps, microservices, or another modern integration approach, replacing orchestrations requires more than just technical execution. It calls for a clear understanding, thoughtful decisions, and the right tools. 

Why BizTalk Orchestrations Are So Complex 

At first glance, orchestrations can appear simple. They are visual, structured, and often look like flowcharts. But underneath, they typically include: 

• Long running transactions and state persistence 

• Custom retry logic and compensation steps 

• Business rules embedded in code or decisions 

• Tight coupling to on-premise systems or databases 

• Interdependencies with ports, maps, and pipelines 

The result is a solution that works, but one that is difficult to move without risking disruption to critical processes. If you are not already familiar with how BizTalk orchestrations work, it is worth revisiting their role before attempting to modernise them. 

 👉 https://learn.microsoft.com/en-us/biztalk/core/orchestrations 

The Common Missteps 

When planning to replace BizTalk orchestrations, many organisations fall into a few traps: 

• Assuming they are just flows 

 Modern tools are powerful, but if you treat orchestrations like simple data pipelines, you might overlook hidden logic and system dependencies. 

• Migrating without reviewing architecture 

 Orchestrations often solved older problems. Rebuilding them exactly can lead to unnecessary complexity in the modern world. 

• Mixing logic and plumbing 

 Transport handling, retries, and error control are often blended with core business rules. These should be separated before you rebuild. 

• Skipping proper testing 

 Orchestrations often touch many systems at once. You need robust test cases and user scenarios to verify every path still works. 

What Can Replace Them 

There is no single right answer. The best approach depends on what the orchestration is doing and what your future architecture looks like. 

Here are some common options: 

• Azure Logic Apps 

 Best for event-driven flows and system integration using out-of-the-box connectors. Can support both stateful and stateless patterns. 

• Durable Functions 

 Great for coded orchestration with state management. Ideal for chaining steps, handling retries, and supporting more advanced control. 

• Microservices 

 Breaking logic into individual services allows for easier scaling and ownership, though it brings its own coordination challenges. 

• Hybrid approaches 

 Many organisations start by moving specific use cases while keeping BizTalk in place for more complex flows during the transition. 

👉 https://learn.microsoft.com/en-us/azure/logic-apps/biztalk-server-migration-approaches 

A Note on BizTalk 2020: Upgrading May Not Be the Easy Option 

Some organisations consider upgrading to BizTalk Server 2020 as a stepping stone. However, it’s important to understand: 

• Upgrading will often require hardware upgrades to support the necessary Windows Server and SQL Server versions. 

• Finding the right Microsoft Partner to configure a 2020 environment can be difficult and expensive. 

• Microsoft is gradually shifting focus away from BizTalk, making it harder and more costly to source experienced professionals and support. 

How to Tackle the Change 

• Map out every orchestration 

 Know what each one does, what systems it touches, and how business logic is applied. 

• Split technical handling from business rules 

 This makes it easier to build services or workflows that are focused and maintainable. 

• Choose the right model 

 Are you orchestrating events, managing long-running flows, or calling external systems? Let the scenario guide your solution. 

• Pilot before going all in 

 Start with lower-risk orchestrations, apply your new pattern, test it thoroughly, then roll out with confidence. 

Orchestrations are powerful, but they are not built for the future. Replacing them is a chance to modernise your integration landscape. That only works if you take the time to do it properly. 

If you want help assessing where to start or how to reduce the risks, get in touch with our team to talk through your options. 

📩 Let’s talk about how we help teams unravel legacy orchestrations and rebuild with clarity. 

 🩺 Not ready to commit? Try our BizTalk Health Check 

 We assess your current estate, flag orchestration complexity, and guide your next steps. 

 👉 https://arrt.uk.com/is-your-integration-ecosystem-fit-for-the-future/