BizTalk is nearing its last support window. Your payment flows cannot wait for a crisis.

Move one critical message flow before BizTalk Server 2020 support ends. Assess its documents, partner rules and recovery corridor by corridor; automatic map conversion is not assumed.

BIZTALK SERVER 2020 · MIGRATION ASSESSMENT

Core value 6 of 7: Builds on existing standards — BPMN Engine and industry standards: ISO 20022, FIX, FpML, AL3/ACORD, HL7, EDI.

Move one critical message flow before BizTalk’s support window closes—without losing the document, partner rules or audit trail. BizTalk Server 2020 mainstream support ends April 11, 2028; extended support ends April 2030. For a bank, the real deadline comes earlier: when the people who understand a payment map or partner exception are no longer there to explain it. Assess one corridor while you still control the timetable; this is not an automatic conversion.

Support time is not migration time.

A support date is not a cutover plan. Banks and their systems integrators need time to find hidden dependencies, revalidate messages, test recovery, and secure approval. Wait until the last window and a controlled migration becomes a production incident.

2028

BizTalk Server 2020 mainstream support ends April 11 (Pacific time).

2030

Extended support ends in April 2030. Confirm the exact cutover time for your estate in Microsoft's lifecycle table.

Now

Inventory your hardest corridor while you can still choose the destination deliberately.

Sources: Microsoft lifecycle · Microsoft migration guidance. Azure Logic Apps is a migration option; placement depends on your estate's requirements.

A map is more than a file.

An orchestration may look stable until a partner sends the one exception nobody documented. The map, its schema, its trading-partner agreement and its recovery procedure are one operational contract. Capture that contract before the team that knows it disperses.

Banks and corporate treasury. Pick a real ISO 20022 payment or trade-confirmation flow. Trace each source field, validate the resulting message against the required schema and business rules, then reconcile what the receiving party acknowledged. A sample generator is not compliance certification.

Systems integrators and utilities. Your client cannot afford to discover undocumented partner behavior after cutover. Bring the BizTalk map, its failure cases and one representative message; determine what transfers, what must be rebuilt and who will own it. Automatic map conversion is not assumed.

Keep the process, the document and the evidence together.

CAPPZ offers a path to re-express a bounded message flow as wallet-held state and BPMN-governed work, with Replicator reconciling copies. Existing MQ and APIs can still carry messages. The destination is assessed corridor by corridor, not promised as a drop-in BizTalk replacement.

BizTalk maps and schemas → validated content

Preserve the source message and its transformation rules; test field-level fidelity and exceptions against real samples before moving traffic.

Orchestrations → governed BPMN

Rebuild the decision path as a reviewable process with explicit inputs, approvals and outcomes instead of assuming orchestration parity.

MessageBox and tracking → wallet copies and receipts

Evaluate Replicator copy reconciliation and event history against the estate’s recovery, retention and audit requirements.

One corridor. Four decisions.

Inventory the estate

Name the maps, schemas, adapters, orchestrations, trading partners and critical messages. Identify the corridors that cannot move to a general cloud.

Choose one corridor

Bring a real ISO 20022 payment or trade-confirmation flow and its existing transformation. Assess map reuse and translate the lifecycle into BPMN before committing to a migration.

Prove the copies

Run a paired-copy acceptance exercise: signed headers, missing-block pull, checksum receipts and a restart. Agree on retention, failure recovery and who owns each document.

Decide on evidence

Document what the pilot demonstrates, what still needs engineering, security review, operational support and an on-prem package. Then make a staged migration decision.

Bring one map, one message and one failure case.

Find out what a safe first corridor would take before the support window dictates the terms.