Infovira – Connect. Integrate. Innovate.

SAP PO and BizTalk migration, including the parts the tools can’t move.

We move SAP Process Orchestration to SAP Integration Suite, and BizTalk Server to SAP Integration Suite or Azure Integration Services. The standard interfaces go fast with SAP’s migration tool and Microsoft’s new AI-assisted Migration Agent, currently in preview. We specialise in the rest: custom code, complex mappings, long-running processes and B2B partners.

Get a free migration snapshotHow the snapshot works

AI-assisted, specialist-verified. Free snapshot first, fixed prices after. Based in Alberta, working across Canada.

Tool-assistedSpecialist rebuildAgent-ready through MCP
under 100days until BizTalk Server 2016 support ends
over 400days until SAP PO mainstream maintenance ends

BizTalk Server 2016 extended support ends on 11 January 2027, and SAP PI/PO 7.5 mainstream maintenance ends on 31 December 2027. BizTalk Server 2020, the final release, leaves mainstream support in April 2028, and SAP’s optional extended maintenance runs to 2030 at a premium fee. With budget approvals, testing and cutover windows, most landscapes need to start now.

Get a free snapshot

What an assessment shows you

Every interface sorted into a category, with the path we take for each one. Switch between an SAP PO and a BizTalk example.

Run the SAP PO scanner on your own exports →

Run the BizTalk scanner on your own bindings →

Migration assessmentExample client, 140 PO interfaces
Sample interfacesSAP category and our path
Sales orders to S/4HANAIDoc, graphical mappingReady to migrateMigration tool
Customer master to CRMSOAP, XSLT mappingReady to migrateMigration tool
Material master syncABAP proxy, value mappingAdjustment requiredTool, then adjust and validate
Work orders to field appREST, Java mappingAdjustment requiredJava mapping wrapped or rewritten in Groovy
Supplier invoicesEDI, partner profilesEvaluation requiredRebuilt in Trading Partner Management
Payroll file to bankSFTP, encryption moduleEvaluation requiredAdapter module redesigned
Full landscape result
  • 81 ready to migrate
  • 38 adjustment required
  • 21 evaluation required

Three services, one partner for your integrations

We start with the migration you have to do, keep your interfaces healthy once they’re live, and help you connect AI to the systems your business runs on.

First

Migrate

Move off SAP PI/PO or BizTalk Server, starting with a free snapshot. AI speeds up the inventory, documentation and code conversion. Senior specialists check every result and take on the interfaces the tools can’t convert.

How we migrate
After go-live

Monitor

A monthly service that watches every interface and alerts the right people in plain business language. AI groups similar errors and suggests the likely cause, and common fixes are applied only with your approval.

How monitoring works
Next

Connect AI

Let AI assistants and agents read and act on SAP and other core systems safely, with the permissions, limits and audit trail your security team expects.

How we connect AI

SAP PO to SAP Integration Suite: every aspect covered

Moving from SAP Process Orchestration to SAP Integration Suite is more than converting flows. These are the ten areas in SAP’s migration guide, plus two we add from experience, and how we handle each one. SAP’s tooling does the standard work; we take on the rest.

  • Tool-assisted SAP or partner tooling does most of the work; we adjust and verify
  • Infovira-led Rewritten or redesigned by our specialists
  • Infovira advisory Planning and advice from our team

Plan

Know what you have and decide what happens to it

Interface migration strategy

For each interface, decide whether to migrate as is, adjust, redesign or retire, and choose the migration approach that fits your landscape.

Infovira advisory

Scenario and object assessment

A full inventory of integration scenarios, channels, mappings and modules, checked against what Cloud Integration supports today, starting with our free SAP PO readiness scanner.

Tool-assisted

Directory API extraction

Bulk extraction of Integration Directory objects through PO’s APIs, so large landscapes are catalogued in days rather than weeks.

Infovira advisory

Migrate

Move what converts, rebuild what doesn’t

ABAP proxy interfaces

Proxy interfaces defined in the Enterprise Services Repository, reconnected to Integration Suite with endpoints and sequencing checked.

Tool-assisted

Value mappings

Value-mapping groups moved across and validated, so code lists and key conversions behave exactly as before.

Tool-assisted

Java mappings

Java mappings reused through a Groovy wrapper or rewritten in Groovy, and user-defined functions and lookups adapted, with unit tests that prove the output matches.

Infovira-led

B2B interfaces

EDI and AS2 partners and agreements rebuilt in Trading Partner Management, or moved directly to Cloud Integration where partners rarely change, with your partners kept informed.

Infovira-led

NW BPM processes

System-centric processes rebuilt as integration flows in Integration Suite, and user-centric processes with human tasks moved to SAP Build Process Automation, following SAP’s guidance.

Infovira-led

Java proxies

Java proxy applications running on PO’s Java server, which are easy to miss in an assessment, re-hosted before PO is switched off and reconnected through Integration Suite.

Infovira-led

Interface design and implementation

Flows that can’t be migrated, such as custom adapter modules and complex routing, redesigned or built new the Integration Suite way.

Infovira-led

Prove and modernize

Show it works, then make it better

Test automation

Real production messages replayed through PO and Integration Suite until the outputs match, using SAP-recommended partner tools such as Int4 and Figaf.

Tool-assisted

Modernization recommendations

OAuth and certificate security, reusable APIs, event-driven patterns, and migrated flows made agent-ready as governed APIs and MCP tools.

Infovira advisory

Areas follow SAP’s migration guide for SAP Process Orchestration, plus two we add from experience: NW BPM processes and Java proxies.

Free tool

Moving SAP PO to SAP Integration Suite? Scan your exports now.

Drop your Integration Directory export, and your ESR export if you have it, into our scanner. In seconds you see every interface sorted into a migration category, the risks we find and a rough effort range. It runs in your browser, so nothing is uploaded, and no SAP tenant or connection is needed.

Run the free scanner

BizTalk Server to SAP Integration Suite: every aspect covered

BizTalk Server 2016 support ends on 11 January 2027. BizTalk Server 2020 is the final release: Microsoft expects to stop selling it in March 2027, and mainstream support ends in April 2028. If your business runs on SAP, we take BizTalk to SAP Integration Suite, so your SAP and non-SAP interfaces end up on one platform built for SAP. If few of your interfaces touch SAP, Azure Integration Services is the better home, and the assessment shows you which way each interface should go.

Option 1

SAP Integration Suite

The right home when BizTalk mainly moves data in and out of SAP.

  • Built for SAP. Native IDoc, RFC, OData and SOAP connectivity to S/4HANA and ECC through the Cloud Connector, with no WCF-SAP adapter or SAP .NET connector left to maintain.
  • One platform instead of two. Your BizTalk and SAP PO interfaces land in the same place, with one team, one set of skills and one support model.
  • SAP’s strategic platform. It is where SAP puts its prebuilt integration content, B2B (Trading Partner Management), API Management and Event Mesh, and it fits RISE with SAP and a clean core.
  • On premises when needed. Edge Integration Cell runs flows inside your network for ground-to-ground traffic and data residency.
Option 2

Azure Integration Services

The better fit when few of your BizTalk interfaces touch SAP. Logic Apps for workflows, API Management for APIs, Service Bus for messaging and Azure Functions for custom code. Logic Apps can reuse compatible XSLT maps and schemas, and its hybrid deployment model runs workflows on your own servers when data must stay on premises.

  • Tool-assisted SAP, partner or Infovira tooling does most of the work; we adjust and verify
  • Infovira-led Rewritten or redesigned by our specialists
  • Infovira advisory Planning and advice from our team

Plan

Know what you have and decide what happens to it

Interface migration strategy

For each BizTalk application, decide whether to migrate as is, adjust, redesign or retire, and confirm SAP Integration Suite is the right home, or Azure where SAP plays no part.

Infovira advisory

Application and artifact inventory

Every receive port, send port, orchestration, map, schema, pipeline and business rule catalogued from your bindings and assemblies, starting with our free BizTalk readiness scanner.

Tool-assisted

Connectivity and protocol check

Adapters, endpoints and certificates mapped to Integration Suite adapters and the Cloud Connector, including Azure Service Bus connections still relying on protocols Microsoft has retired.

Infovira advisory

Migrate

Move what converts, rebuild what doesn’t

SAP connections

WCF-SAP IDoc and RFC ports replaced by the IDoc and RFC adapters, with one shared inbound flow for IDocs from SAP and the partner profiles in SAP updated to match.

Tool-assisted

Schemas and maps

XML schemas and XSLT maps reused in message mappings or XSLT steps. Custom functoids and helper .NET code rewritten in Groovy with the same behaviour, and every map retested against BizTalk’s output.

Infovira-led

Orchestrations

Redesigned as integration flows rather than copied shape by shape: routers, splitters and multicasts for routing, JMS queues for reliable and ordered delivery, and exception subprocesses for error handling.

Infovira-led

Pipelines and custom components

Custom pipeline components rewritten as Groovy scripts or replaced with standard integration flow steps.

Infovira-led

Business Rules Engine policies

Every rule documented in plain language, then rebuilt as value mappings, Groovy logic or SAP Build Process Automation decisions, depending on who maintains it.

Infovira-led

EDI and trading partners

X12, EDIFACT and AS2 agreements, parties and certificates moved to Trading Partner Management and Integration Advisor, with your partners kept informed.

Infovira-led

Prove and modernize

Show it works, then make it better

Test automation

Real production messages replayed through BizTalk and the new integration flows until the outputs match field by field.

Tool-assisted

Operations and monitoring

Integration Suite monitoring and alerting set up to replace the BizTalk Administration Console, tracking and BAM, so your support team isn’t left blind after cutover.

Infovira advisory

Agent-ready APIs and MCP tools

Migrated flows exposed as governed APIs and MCP tools through SAP Integration Suite’s MCP Gateway, so AI agents can use them with the same controls as any other system.

Infovira-led

Areas follow our BizTalk to SAP Integration Suite migrations. If you choose Azure, the same areas apply with Logic Apps, Service Bus and an Integration Account, following Microsoft’s migration guidance.

Does your BizTalk talk to Azure Service Bus? Microsoft ended support for the Service Bus SBMP protocol on 30 September 2026, and BizTalk’s SB-Messaging adapter has relied on it. Microsoft has published guidance for BizTalk Server 2020 customers on switching to AMQP; we know of no equivalent fix for BizTalk Server 2016. We check this in every free BizTalk snapshot, and our free scanner flags it in seconds.

Free tool

Moving BizTalk to SAP Integration Suite? Scan your bindings now.

Drop a BizTalk bindings export into our scanner. In seconds you see your interface count, an iFlow estimate, the risks we find and a rough effort range. It runs in your browser, so nothing is uploaded.

Run the free scanner

Migration services: start free, finish with a clean cutover

Each stage stands on its own, so you can stop after the free snapshot or the assessment, use us for the hard interfaces only, or have us run the whole migration. The same services cover SAP PO and BizTalk Server.

Start here, free

Free migration snapshot

Send us a basic export of your landscape and we’ll send back a short written snapshot. No cost, no obligation, and no access to your systems.

  • SAP PO: your interface list, or the report from SAP’s Migration Assessment if you’ve run it
  • BizTalk Server: a list of your BizTalk applications, or an export of your bindings
  • Back from us: interface counts by likely category, the top risks we see, and a rough effort range
  • A 30-minute call to walk you through it

On SAP PO? Get an instant result with the free PO scanner, then send it to us for the written snapshot.

BizTalk moving to SAP Integration Suite? Get an instant result with the free scanner, then send it to us for the written snapshot.

Freeno obligation
5 business daysafter we receive your export

Retirement assessment

When you’re ready to commit budget: every interface catalogued and scored for complexity and business risk, a clear split of tool-ready versus specialist work, the target architecture, and migration waves with an effort estimate.

2–4 weeks, fixed price quoted from your snapshot

Custom interface migration

We handle what the tools can’t convert: custom adapter modules, BPM processes and complex Java mappings in PO; complex orchestrations and custom pipeline components in BizTalk; and B2B scenarios on both. Priced per interface by complexity.

Testing, cutover and hypercare

Real production messages replayed through old and new platforms until the results match, then a planned, low-risk cutover with hypercare after each go-live.

AI documentation pack

AI reads your old mappings, XSLT, Java code and orchestrations and produces plain-language specifications and test cases, reviewed by our specialists. Useful even before you migrate.

After go-live

Make it agent-ready

Expose the migrated flows as governed APIs and MCP tools, so AI agents can use them with per-user identity, rate limits and a full audit trail. We set this up on SAP Integration Suite’s MCP Gateway or Azure API Management, depending on where your flows run.

How we connect AI

How a migration runs

The same five phases on every project, so you always know what is done and what is next. Then one more step turns your new platform into something AI agents can use.

  1. Assess

    Start with the free snapshot, then catalog and score every interface and agree the target platform.

  2. Plan waves

    Group interfaces by risk and business area, starting with low-risk wins.

  3. Migrate

    Tool-convert the standard scenarios and rebuild the custom ones.

  4. Prove

    Replay real messages through old and new until the outputs match.

  5. Cut over

    Switch over wave by wave, with hypercare after each go-live.

  6. Make it agent-ready

    Expose the migrated flows as governed APIs and MCP tools.

Know about a failed interface before your users do

Most interface failures are found by business users days later: missing orders, unpaid invoices, stale master data. Our monthly monitoring service watches every interface across your platforms and tells the right people what broke, in words they understand.

What your team sees today
MPL 5f3a…c91 FAILED  com.sap.it.rt.adapter.http.api.exception.HttpResponseException: An internal server error occured: Read timed out. The MPL ID for the failed message is…
What Infovira sends instead

12 work orders from the maintenance system didn’t reach S/4HANA this morning.

Likely cause
Receiver timed out during the 6:00 batch
Business impact
Field crews can’t see today’s jobs
Action
Retry queued, awaiting your approval
Sent to
Maintenance planning team, via Teams
  • One view across platformsSAP Integration Suite, PI/PO, Azure Logic Apps and BizTalk in a single dashboard, using each platform’s own monitoring APIs.
  • Alerts in business languageSent to the people who can act, by email, Microsoft Teams or ServiceNow, instead of a stack trace to a shared inbox.
  • AI-assisted triageSimilar errors grouped, likely causes suggested, and known fixes such as retries, certificate renewals and credential rotation applied with your approval.
  • Health reports and supportA monthly health report, certificate and capacity checks, and business-hours or 24/7 response.

Monthly subscription, priced by interface volume and support hours. Read-only access and client-hosted options are available for strict security requirements.

Let AI agents use SAP safely

Many AI pilots stall at the same point: they can’t be connected to core systems without security and audit risk. Most AI teams don’t know ERP data or integration security. That’s exactly what we know, and the integrations you’ve just migrated are the quickest way in: we expose them as governed APIs and MCP tools, so agents work through the same controls as every other system.

AI assistants and agents

  • Copilots and chat assistants
  • Custom agents
  • Automation tools

Governed gateway, set up by Infovira

  • Curated business actions
  • OAuth and per-user identity
  • Rate and action limits
  • Human approval for risky steps
  • Full audit logging
  • SAP Integration Suite MCP Gateway or Azure API Management

Your core systems

  • SAP S/4HANA and ECC
  • Workday, Salesforce
  • Legacy applications
Start here

AI integration readiness review

We map which systems and data your agents need, rate your APIs for readiness, and design the security model your risk team can sign off. Fixed price.

Agent gateway build

Your migrated flows and core APIs exposed to AI agents as curated MCP tools through SAP Integration Suite’s MCP Gateway or Azure API Management, with identity, limits and logging.

Starter use cases

One or two production agents, such as maintenance work-order lookup and creation, or invoice status queries.

Why work with Infovira

Our founder, Anish Thankachan, has spent more than 20 years building and running SAP integrations, and has led PO-to-Integration Suite migrations in energy, rail and the public sector. He has also led Azure Logic Apps delivery teams, so BizTalk customers work with someone who knows where their interfaces are going. The person who scopes your project is the person who does the work.

We’ve built what you’re migratingJava mappings, adapter modules and BPM processes are our home ground, not an escalation.
We use the tools, not fight themSAP’s and Microsoft’s migration tooling handles the standard work, so your budget goes to the hard parts.
We work alongside your partnersWe can lead a migration or join your system integrator as the specialist for custom scenarios.
One partner from migration to AIThe team that migrates your interfaces can monitor them afterwards and connect them to AI, without handing over to strangers.
Free to start, fixed prices afterThe snapshot is free, and assessments and interface rebuilds are quoted up front, so you can budget with confidence.

Questions we hear most

Don’t see yours? Ask it when you request your snapshot.

When does support for SAP PI/PO end?

Mainstream maintenance for SAP PI/PO 7.5 ends on 31 December 2027, in line with SAP NetWeaver 7.5. Extended maintenance to the end of 2030 is optional and comes at a premium fee. Older releases are already out of maintenance.

When does support for BizTalk Server end?

BizTalk Server 2016 reaches the end of extended support on 11 January 2027. BizTalk Server 2020 is the final release: Microsoft expects sales to end on 31 March 2027, and mainstream support ends in April 2028. After that, Microsoft plans optional, paid support to April 2030 as temporary migration cover, expected to exclude some capabilities. Older versions are already out of support.

Should BizTalk move to Azure or SAP Integration Suite?

If your business runs on SAP, we recommend SAP Integration Suite. It connects natively to S/4HANA and ECC through IDoc, RFC and OData, it is SAP’s strategic integration platform, and it puts your BizTalk and SAP PO interfaces on one platform. Azure Integration Services is the better choice when few of your BizTalk interfaces touch SAP: Microsoft names Azure Logic Apps as BizTalk’s successor, and Logic Apps can reuse compatible XSLT maps and schemas. The assessment shows the split interface by interface.

What is the free migration snapshot?

A short written review based on an export you send us: your PO interface list or SAP Migration Assessment report, or your BizTalk application list or bindings. You get interface counts by likely category, the top risks we see and a rough effort range, plus a 30-minute call to walk through it. There’s no cost, no obligation and no access to your systems needed.

Can I check my SAP PO landscape myself?

Yes. Our free SAP PO readiness scanner reads your Integration Directory export, and your ESR export if you add it, in your browser. In seconds it sorts every integrated configuration into ready to migrate, adjustment required or evaluation required, and shows the main risks and a rough effort range. Nothing is uploaded and no SAP tenant is needed. Send us the result and we’ll turn it into your written snapshot.

Can I check my BizTalk landscape myself?

Yes, if you’re moving to SAP Integration Suite. Our free BizTalk readiness scanner reads a bindings export in your browser and shows your interface count, an iFlow estimate, the main risks and a rough effort range in seconds. Nothing is uploaded. Send us the result and we’ll turn it into your written snapshot.

Can’t we just use the vendors’ migration tools?

For standard scenarios, yes, and we recommend them: SAP’s migration tool for PO, and Microsoft’s Logic Apps Migration Agent (in preview) if BizTalk is moving to Azure. No vendor tool converts BizTalk to SAP Integration Suite, so for that move we use our own scanner, assessment and conversion tooling. SAP’s tool converts many interfaces, including some with Java mappings, but custom adapter modules and BPM processes aren’t migrated and must be redesigned. In BizTalk, complex orchestrations, custom pipeline components and EDI setups need the same specialist work. Those usually carry the most business risk, and the assessment tells you exactly how much of your landscape falls into each group.

Do we have to move everything to the cloud?

No. SAP Integration Suite’s Edge Integration Cell lets you design in the cloud and run integrations inside your own environment, which suits ground-to-ground scenarios and strict data residency needs. The same applies to interfaces moving off BizTalk, and if you choose Azure, Logic Apps’ hybrid deployment model does the same on your own servers. We’ll recommend the right mix in the assessment.

How do you use AI, and what happens to our data?

AI helps us read old mappings and code, draft specifications and test cases, and triage errors. A specialist reviews everything before it reaches you. Your code and messages stay in your environment or in AI tools you approve, and production data is never used without your agreement.

How long does a migration take?

It depends on how many interfaces you have and how much of them is custom. The assessment takes two to four weeks and gives you a realistic, wave-by-wave timeline before you commit to the full project.

Do you only work with SAP?

No. We migrate both SAP PO and BizTalk Server, and our monitoring covers SAP Integration Suite, PI/PO, Azure Logic Apps and BizTalk. We give platform-neutral advice on where each interface should run.

Can AI agents use our migrated integrations?

Yes. Both platforms now support MCP, the open standard AI agents use to call business tools. SAP Integration Suite’s MCP Gateway, announced at SAP TechEd 2025, exposes APIs and integration flows as governed MCP tools, and Azure API Management can expose APIs as MCP tools and govern MCP servers, including Logic Apps workflows (in preview). We set this up as part of your migration or afterwards, with per-user identity, limits and audit logging.

What access does monitoring need?

Read-only access to your platforms’ monitoring data is enough for alerts and reporting. Any fix is applied only with your approval, and we can run the service inside your own environment if your security policy requires it.

We already have a system integrator. Can you still help?

Yes. We often join existing teams as the specialist for the custom scenarios, so your partner can keep momentum on the standard work.

Get your free migration snapshot

Tell us which platform you’re moving off and roughly how many interfaces you have. We’ll reply within one business day with what to send, and return your snapshot within five business days of receiving it. Working on monitoring or an AI pilot instead? Use the same form, and we’ll tell you honestly where the risk is and whether we can help.

Email: contact@infovira.com, which comes straight to Anish

Your message is delivered through Formspree and used only to reply to you.