Your integration estate has a deadline. Your maps deserve a plan.

BizTalk Server 2020 support ends in 2028–2030. Assess one ISO 20022 or trade-confirmation corridor, its maps, orchestration and document recovery with CAPPZ Replicator.

Support time is not migration time.

Banks and complex enterprises need time to document dependencies, validate maps, test recovery and secure an approved operating model. Waiting until the support deadline turns a controlled corridor migration into an emergency change.

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.

Keep the document close to the process.

BizTalk joined maps, orchestration and transport around a central hub. CAPPZ Replicator explores another pattern: wallet-held documents and their provenance, with peer-path copy reconciliation and BPMN-governed lifecycle steps. Existing MQ and APIs can still carry bytes.

Banks and corporate treasury. Investigate ISO 20022 payment generation and validation in a specific workflow; map each source field and require schema, business-rule and reconciliation evidence. A sample message generator is not a blanket compliance certification.

Utilities and systems integrators. Map operational exchanges, partner interfaces and failure handling. Bring one client corridor and an existing BizTalk map to establish what can be reused; resident map import and a supported air-gap package are assessment goals, not shipped promises.

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 and one message.

We will scope what it would take to move the corridor without losing its history.