All posts
Legacy Modernization

BizTalk Server Is Ending: Moving Integrations and EDI to AWS Before 2027 and 2030

By

October 25, 2026

7 min read

BizTalk Server 2016 and Host Integration Server 2016 end support on January 11, 2027. BizTalk 2020 is the last release, with extended support until April 2030. How BizTalk's pieces (orchestrations, adapters, maps, EDI, BAM) map to AWS services, and a migration order that does not stop the business.

BizTalk Server
EDI
Integration
Step Functions
AWS B2B Data Interchange
2027

BizTalk sits quietly in the middle of many companies, moving orders, invoices and EDI between systems that were never designed to talk. Microsoft has said BizTalk Server 2020 is the final version. Its mainstream support was extended to April 2028 and extended support runs to April 2030. BizTalk 2016 ends on January 11, 2027.

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

How BizTalk maps to AWS

BizTalk

On AWS

Notes

Orchestrations

Step Functions, or Lambda durable functions for code-first flows

Long-running, with retries and compensation

Message box, publish-subscribe

EventBridge, SQS, SNS

Content-based routing with EventBridge rules

File, FTP and SFTP adapters

AWS Transfer Family, S3 events

Transfer Family also supports AS2

SaaS and database adapters

AppFlow, Lambda, DMS for change data capture

Maps (XSLT)

Lambda transformations; Step Functions data transformations for simple cases

Existing XSLT can often be reused in Lambda

EDI (X12) parties and agreements

AWS B2B Data Interchange

Converts X12 to and from JSON or XML; trading partner profiles

BAM and tracking

CloudWatch, X-Ray, Step Functions execution history

Design tracking in from the start

The Microsoft path

Microsoft's successor is Azure Logic Apps with Azure Integration Services, and Microsoft provides migration tooling for BizTalk artifacts. If the rest of your estate is on Azure, that is the natural route. If it is on AWS, rebuilding on AWS services keeps the integrations next to the systems they connect, under one identity and network model.

Migration order

  1. Export every application, port, orchestration and map, and record message volumes per interface. A handful of interfaces usually carry most of the traffic.

  2. Delete interfaces with no traffic in the last year.

  3. Move simple file and message routing first. They are quick, low-risk and build the team's confidence with the new services.

  4. Move EDI partner by partner, running both paths in parallel and comparing outputs before cutting over.

  5. Leave the most complex orchestrations for last, and redesign rather than translate them; BizTalk-era workarounds rarely need to survive.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.