SAP Integration Suite and PI/PO migration
Integration is where SAP projects most often break. We design integration architecture, build interfaces on SAP Integration Suite, and migrate PI/PO landscapes before mainstream maintenance ends in 2027.
The 2027 deadline for PI/PO
SAP Process Integration and Process Orchestration 7.5 reach the end of mainstream maintenance on 31 December 2027, in step with the rest of SAP Business Suite 7. Extended maintenance runs to the end of 2030 at extra cost and without new features. SAP's successor is SAP Integration Suite on BTP, with the Edge Integration Cell for customers who need integration to run inside their own network.
A PI/PO landscape built over fifteen years can hold hundreds of interfaces, many of them undocumented and some no longer used. Migration is a good moment to find out which ones still matter.
How we migrate PI/PO
01Inventory and assessment
We extract the interface catalogue, run SAP's migration assessment to classify each integration by effort, and check message volumes to find the interfaces nobody uses any more.
02Target architecture
Cloud Integration tenants per environment, Edge Integration Cell where data must stay on-premise, API Management for exposed services, and naming, error handling and monitoring standards.
03Migration waves
Interfaces grouped by partner, business process and risk. The migration tooling in Integration Suite handles supported patterns; the rest are redesigned, often as simpler API or event flows.
04Parallel run and cutover
Old and new flows compared on real messages, partners switched over in agreed windows, and PI/PO decommissioned once nothing runs through it.
Integration services
- Cloud Integration
- iFlows with mapping, routing and transformation, adapters for SAP and non-SAP systems, Groovy scripting where needed, and proper exception handling and alerting.
- API Management
- API proxies, policies, rate limits and a developer portal for internal and partner APIs, including S/4HANA OData services exposed safely to outside consumers.
- Event-driven integration
- S/4HANA business events published through SAP Event Mesh or Advanced Event Mesh, so downstream systems react in near real time instead of polling.
- B2B and EDI
- Trading Partner Management and Integration Advisor for EDIFACT, X12 and other formats, with AS2 connectivity to customers, suppliers and carriers.
- Integration architecture
- An integration strategy using SAP's Integration Solution Advisory Methodology, so each new interface uses the right pattern instead of the one the last developer knew.
- Classic SAP integration
- IDocs, ALE, BAPIs, RFCs, SOAP and REST services and the Application Interface Framework for monitoring, which remain part of most landscapes.
Explore the SAP practice
S/4HANA and ERP transformation
Platform, AI and data
- SAP Business Technology Platform
- SAP Business AI and Joule
- Integration Suite and PI/PO migration
- Data and analytics
- SAP Fiori and UX
- ABAP and clean core development
Finance and revenue
Supply chain, manufacturing and assets
People, spend and customers
Plan the next step with us
Share what you're working on. We'll tell you how we'd approach it and who would do the work.