Why the deadline shapes the plan
SAP Process Orchestration 7.5 and PI 7.5 follow the SAP NetWeaver 7.5 maintenance strategy. Mainstream maintenance ends on 31 December 2027. Optional extended maintenance runs until 31 December 2030. Releases below 7.5 are already out of maintenance, so if any part of your estate is still there, it is the first risk to close.
Extended maintenance is optional and should be read as a fallback. A plan that depends on it has no margin left. The sensible approach is to work backwards from 31 December 2027, reserve time at the end for the scenarios that turn out harder than expected, and decide now who owns each decision.
SAP Integration Suite is SAP's strategic integration platform on SAP BTP and the successor path for PI/PO workloads. It is not a single product to install. It is a set of capabilities, and a good migration uses only the ones you need:
- Cloud Integration for integration flows.
- API Management for API proxies, policies and a developer portal. It is now offered only as a capability within SAP Integration Suite.
- Integration Advisor and Trading Partner Management for B2B.
- Integration Assessment and Migration Assessment for planning.
- A migration tool in Cloud Integration for supported PI/PO objects.
- Open Connectors for third-party connectivity.
- Event-driven integration with SAP Integration Suite, advanced event mesh.
This playbook has seven steps, followed by governance, a real example and a closing checklist.
Step 1: Build the inventory and run the assessment
Do not start with tooling. Start with a complete list of what runs today. Many PI/PO systems hold scenarios that nobody has used for a long time, and many hold scenarios that only one person understands.
What to capture for each scenario
For every interface, record these items:
- Business purpose and the business owner who can approve a change.
- Sender and receiver systems, and whether each is on premise, in a cloud or at a partner.
- Adapters and protocols in use.
- Mapping logic, including any custom code.
- Error handling, retries and who is told when something fails.
- Volume pattern: scheduled batch, on demand, or continuous.
- Dependencies on other scenarios, such as shared mappings or shared receiver configuration.
- Whether the scenario is B2B, A2A or an API candidate.
