Inventory first
In every migration, the real number of interfaces exceeded the assumed one. Without a catalogue with owners, volumes and criticality, every plan is too tight.
Insights · Integration
SAP PO is ending: what platform changes teach
SAP Process Orchestration is approaching the end of maintenance. We have been part of every generation change in SAP integration first-hand. Five lessons from that.
By Michele Mangieri · Updated
In short
Under SAP's maintenance strategy, mainstream maintenance for SAP Process Orchestration (SAP PO) 7.5 ends at the end of 2027, with extended maintenance until the end of 2030. The successor is SAP Integration Suite, in the cloud or with Edge Integration Cell in your own data centre. A migration starts with a complete inventory of interfaces, not with the technology.
Starting point
What is certain.
- Under SAP's maintenance strategy, mainstream maintenance for SAP PO 7.5 ends at the end of 2027, with extended maintenance until the end of 2030.
- The successor is SAP Integration Suite, in the cloud or with Edge Integration Cell in your own data centre.
- Check the dates that apply to your contracts in SAP's current maintenance overview. They can change.
Lessons
Five lessons from practice.
Do not copy everything 1:1
A platform change is the chance to retire legacy. Every interface is classified: keep, rebuild, replace or retire.
Gartner TIME explained →Start with pilots
A few typical scenarios first. They show which patterns hold, which adapters are missing and how long a scenario really takes.
Plan operations along
Monitoring, alerting, authorisations and transports decide everyday life after go-live. The operations concept belongs in the migration, not after it.
Strategy before technology
An integration strategy defines which patterns run on which technology. Otherwise every project decides anew.
SAP ISA-M explained →From our project work.
First the migration from SAP XI 2.0 to 3.0, in 2005 the replacement of the Business Connector, in 2007 the SAP PI 7.10 Ramp-Up in a landscape with 400 interfaces, in 2012 the introduction of SAP PI 7.31 in the Java-only edition, and from 2019 the migration from SAP PI/PO to SAP Cloud Integration at Berliner Stadtreinigung.
Want to know where your integration stands? To the Integration Readiness Review →
SAP, SAP PO, SAP Integration Suite and S/4HANA are trademarks of SAP SE. maxClaint is an independent consultancy and not an SAP partner.
Frequently asked questions
Questions about SAP PO
When does maintenance for SAP PO end?
Under SAP's maintenance strategy, mainstream maintenance for SAP PO 7.5 ends at the end of 2027, with extended maintenance until the end of 2030. Check the dates that apply to your contracts in SAP's current maintenance overview; they can change.
What is the successor to SAP PO?
SAP Integration Suite. It runs in the cloud or with Edge Integration Cell in your own data centre.
Should all interfaces be moved 1:1 to Integration Suite?
No. A platform change is the chance to retire legacy. Every interface is classified: keep, rebuild, replace or retire.
Where does an SAP PO migration start?
With an inventory. In every migration, the real number of interfaces exceeded the assumed one. A catalogue with owners, volumes and criticality is the foundation; a few typical scenarios follow as pilots.
What is often forgotten in the migration?
Operations. Monitoring, alerting, authorisations and transports decide everyday life after go-live. The operations concept belongs in the migration, not after it.
30 minutes, and you will know whether we can help.
You describe the decision ahead. We tell you which package fits, or that none does.