Support deadline · SAP
SAP PI/PO end of support: your options and timeline
SAP PI/PO 7.5 mainstream maintenance ends at the end of 2027 (we count to 31 December 2027): 453 days remaining (SAP: Process Integration way forward (SAP blog), checked on 2026-10-03).
SAP PI/PO end of life comes in two steps. SAP describes Process Integration 7.5 as available "until 2027 on standard maintenance and 2030 for extended maintenance" (SAP: Process Integration way forward (SAP blog), checked on 2026-10-03), and extended maintenance for NetWeaver 7.5 runs to the end of 2030 at extra cost (SAP: NetWeaver maintenance strategy, checked on 2026-10-03). SAP names SAP Integration Suite as the logical successor.
Last updated . Figures are re-checked quarterly.
The PI/PO timeline
| Date | What happens | Source |
|---|---|---|
| End of 2027 | Mainstream maintenance for SAP PI/PO 7.5 ends. | (SAP: Process Integration way forward (SAP blog), checked on 2026-10-03) |
| End of 2030 | Extended maintenance for SAP NetWeaver 7.5, the platform PI/PO 7.5 runs on, ends; it carries a premium of two percentage points on the maintenance basis. | (SAP: NetWeaver maintenance strategy, checked on 2026-10-03) |
Your options
- Move to SAP Integration Suite. SAP calls Integration Suite "the logical successor for PI" (SAP: Process Integration way forward (SAP blog), checked on 2026-10-03).
- Assess first. The Migration Assessment capability in Integration Suite analyses your PI/PO interfaces for complexity, dependencies and effort; it supports PI/PO 7.31 SP28+, 7.40 SP23+ and 7.50 SP06+ (SAP: FAQ, migration from Process Orchestration to Integration Suite, checked on 2026-10-03).
- Convert with the Migration Tool. It converts integration artifacts such as mappings, communication channels and interface objects, but does not automatically convert user-defined functions to Groovy (SAP: FAQ, migration from Process Orchestration to Integration Suite, checked on 2026-10-03).
- Keep on-premises traffic on-premises. Edge Integration Cell runs integration flows inside your network; SAP says messages processed there "are only charged at 50%" (SAP: FAQ, migration from Process Orchestration to Integration Suite, checked on 2026-10-03).
- Move to a non-SAP integration platform. Worth pricing when most interfaces connect non-SAP systems.
How long it takes
SAP gives indicative durations: landscapes of up to 100 interfaces that are mostly lift-and-shift "commonly take 1–3 months"; up to 300 interfaces take three to six months; large landscapes can take more than a year (SAP: FAQ, migration from Process Orchestration to Integration Suite, checked on 2026-10-03). SAP describes two approaches: lift-and-shift with minimal functional change, or modernization toward API-led and event-driven patterns (SAP: FAQ, migration from Process Orchestration to Integration Suite, checked on 2026-10-03). Lift-and-shift is faster; modernization is the chance to retire interfaces nobody needs.
Measured against the deadline, the arithmetic is tight for large estates. A landscape of 300 interfaces at SAP's indicative pace needs three to six months of migration work, before testing with partners, cut-over windows and the year-end freezes many SAP customers observe. Starting a year ahead of the end of mainstream maintenance leaves room for one slipped wave; starting six months ahead does not.
Migration-readiness checklist
- Export the PI/PO interface list with sender, receiver, adapter type and message volume.
- Run the Migration Assessment, or record the same complexity data by hand.
- Flag interfaces using user-defined functions, Java mappings or BPM processes.
- Separate SAP-to-SAP, SAP-to-non-SAP and on-premises-only interfaces; each has a different target.
- Agree whether extended maintenance to 2030 is a fallback, and budget for it if so.
Disclosure: iPaaS Tools offers migration tooling and services, so we have an interest in this topic. We have no affiliation with, and are not endorsed by, any vendor named here; product names belong to their owners.