Is BizTalk really being discontinued?
BizTalk Server has reached the end of its lifecycle. Microsoft released the final major version in 2020 and has confirmed there will be no successor; mainstream support has already ended and extended support runs out in the second half of the decade. Practically speaking that means: no new features, a shrinking pool of specialists and growing pressure from newer operating systems, SQL Server versions and security requirements. The platform still runs reliably today – but planning a replacement now is far cheaper than being forced into one later.
What replaces BizTalk?
There is no single one-to-one successor, and that is a good thing. In most cases a combination fits best: lean .NET/C# integration services for orchestration and transformation, a message broker or event bus for asynchronous flows, and clean REST APIs as the contract between systems. Where it pays off, managed integration or workflow services can complement that. We choose the target architecture to match your real load, your operations team and your existing landscape – not the other way around.
Can a migration run without downtime?
Yes – that is precisely the point of a step-by-step approach. We migrate interface by interface and run the new and the old platform in parallel during the transition. Each flow is switched over only once it has been verified against production data, and a documented fallback to BizTalk stays available until everyone is confident. For most interfaces that means no perceptible interruption to the business.
How long does a BizTalk migration take?
It depends on the number and complexity of interfaces, not on a calendar promise. A focused assessment of two to four weeks gives you a reliable inventory and a phased plan with effort per interface. From there, simple landscapes can be migrated within a few months, while large, business-critical platforms are moved in planned waves over a longer period. You always migrate in value-delivering increments, never in one risky big bang.
Do our EDI/SAP integrations stay intact?
Yes. EDI partner connections, SAP integration (IDoc, BAPI, RFC) and established standards such as AS2, EDIFACT or X12 are exactly where our integration roots lie. We preserve the business logic and the partner agreements, rebuild them on a modern, maintainable foundation and validate every message against real production data before go-live, so your partners notice nothing but a cleaner, faster backend.