For organizations still relying on SAP Process Integration or SAP Process Orchestration (PI/PO), 2027 is a practical planning deadline—not a reason to switch off every interface at once. SAP states that mainstream maintenance for SAP PI/PO 7.5 ends December 31, 2027, with optional extended maintenance through December 31, 2030 under applicable conditions. SAP’s October 2026 guidance also highlights constraints affecting Java-related support arrangements after 2030.
The difficult question is not only whether to move to SAP Integration Suite. It is which integrations to assess, redesign and migrate first without disrupting orders, suppliers, inventory, finance or customers. A responsible program needs a verified inventory, business ownership, technical assessment and repeatable regression testing before it needs an aggressive migration date.
At a glance: begin with a landscape inventory and a bounded pilot. Prioritize high-risk dependencies and interfaces with a clear path to modernization, but do not move mission-critical, heavily customized flows without proper testing, cutover and rollback plans.
What happens to SAP PI/PO after 2027?
SAP’s maintenance strategy applies to SAP Process Integration and SAP Process Orchestration 7.5 in alignment with SAP NetWeaver 7.5. Mainstream maintenance runs through the end of 2027, while optional extended maintenance can extend to the end of 2030. This does not mean every existing interface automatically stops processing messages on January 1, 2028. Organizations must confirm their own release, commercial terms and support entitlements.
The long-term picture requires equal attention. SAP clarified in October 2026 that its existing support arrangements for Java used with NetWeaver AS Java 7.5 are scheduled to end after 2030, limiting what customer-specific maintenance can replace. For a company that expects PI/PO to remain critical indefinitely, this is a reason to create a funded transition plan now—not an invitation to make unsupported promises about future support.
Sources: SAP NetWeaver maintenance strategy and SAP’s October 2026 support clarification.
The five integration groups to assess first
1. Stable, well-understood interfaces for a controlled pilot
A good first migration candidate is not necessarily your most important interface. Begin by identifying several flows with known endpoints, representative payloads, business owners and manageable dependency chains. These can be used to validate connectivity, deployment, mapping, operations, alerting and the test process in SAP Integration Suite.
The aim is to learn what changes when a message passes through the new runtime. Can the team detect failure and retry safely? Are the output fields equivalent? Do certificates and credentials rotate properly? Can support engineers find and replay failed messages? A pilot that answers those questions provides evidence for later waves.
2. Business-critical integrations with many dependencies
Order-to-Cash, Procure-to-Pay, warehouse, manufacturing and finance integrations often cross several applications and partners. They should be assessed early because their dependency and testing requirements influence the roadmap, even if they are migrated later. An end-to-end business-service map is more useful than a long list of technical interface IDs.
For example, a sales-order flow may depend on pricing, inventory availability, warehouse execution, carrier status and invoicing. Migrating one leg without examining the others could create reconciliation or exception-handling issues. Assign a business owner who can validate the complete process.
3. Custom mappings, Java code and adapter modules
Identify these early because they can consume disproportionate redesign and testing effort. SAP documents limitations in its Migration Tooling around custom adapter modules, specific mapping patterns, lookups and message-processing behavior. A technically “successful” conversion might not preserve every business rule or operational control.
These scenarios need a design review that asks what the old logic really does, whether a supported capability now replaces it, whether the connected application must change, and what regression evidence is required. Treat unexamined custom code as a risk to be resolved, not a small line item to be migrated last.
4. Partner-facing B2B and EDI integrations
External partner connections introduce coordination beyond the SAP team. B2B and EDI scenarios may require partner-specific mappings, acknowledgments, testing windows, certificate exchanges and formal sign-off. SAP’s automated Migration Assessment has limitations for B2B scenarios and related business-process logic, so these require deliberate manual review.
Assess them early enough to reserve partner testing time. Their cutovers may be scheduled later around agreed windows, commercial commitments and operational calendars.
5. Low-value, dormant or duplicate interfaces that can be retired
One of the quickest ways to reduce migration effort is to avoid rebuilding something the business no longer needs. An inactive application, decommissioned reporting feed or duplicate master-data integration should be examined for retirement. But do not confuse low traffic with low value: a quarterly finance or regulatory interface might execute rarely and still be essential.
Require business-owner approval, usage evidence and an agreed monitoring period before retirement. Every retired interface should reduce cost and complexity without creating an unseen operational gap.
How SAP Migration Assessment can guide the plan
SAP Integration Suite includes a Migration Assessment capability that evaluates existing PI/PO integration scenarios and assigns classifications including Ready to migrate, Adjustment required and Evaluation required. These classifications help prioritize review. They do not guarantee automated conversion or successful production operation.
- Ready to migrate: the scenario aligns with available capabilities, but may still need manual or semi-automated migration and configuration changes.
- Adjustment required: the scenario partly aligns and needs changes to the integration design or connected systems.
- Evaluation required: more investigation is needed, often because of unsupported behavior, custom code or unclear dependencies.
SAP explicitly distinguishes an assessment category from the migration tool’s automation coverage. It also lists limits for custom adapters, B2B and BPM scenarios and dependencies inside custom mappings. Teams should record both the classification and the effort to achieve functional equivalence.
See SAP’s Migration Assessment concepts, assessment limitations, and Migration Tooling limitations.
Should every interface run in the cloud?
Not necessarily. SAP Integration Suite’s Cloud Integration capability is an important target for many scenarios, but the architecture should reflect network, latency, compliance, data-residency and operational requirements. SAP’s Edge Integration Cell provides an option for processing certain integration workloads inside a private landscape with a customer-managed Kubernetes runtime while retaining cloud-based design and governance.
That private runtime is not a free shortcut: it adds infrastructure, storage, networking, monitoring and lifecycle responsibilities. Compare the full operating model before selecting it. The goal is an integration landscape that is easier to govern and support, not one that replicates every legacy dependency in a different location.
For background, see SAPSOL’s article on SAP Integration Suite and SAP BTP and modernization around the SAP core.
A practical 30-day plan for IT leaders
If your organization is starting now, the first month should produce decisions and evidence rather than a premature promise to replace the entire platform.
- Week 1 — Confirm the baseline. Verify SAP PI/PO versions, entitlements, support contracts, installed add-ons and accountable business and technical owners.
- Week 2 — Inventory the integration estate. Capture interfaces, adapters, mappings, custom components, connected systems, throughput, error handling, service levels and sample payloads. Flag dormant, critical and externally governed flows.
- Week 3 — Assess and classify. Use SAP Migration Assessment where applicable. Review custom code and known assessment blind spots manually. Classify candidates as retire, reuse, migrate, redesign or defer.
- Week 4 — Plan a pilot and operating model. Select representative flows, define expected outputs, ownership, monitoring and rollback, and assign exit criteria. Obtain approval for the first controlled wave.
From there, plan a 60–90-day sequence to validate architecture, execute the pilot, establish regression coverage and build a business-aligned migration roadmap. This is a planning method, not a claim that the entire PI/PO landscape can be migrated in 90 days.
What to ask before approving your first migration wave
- Do we know which transactions and applications each integration supports?
- Do we have current technical and business owners for each scenario?
- Have custom modules, mappings and B2B or BPM dependencies been reviewed?
- Can we prove that retries, duplicates, sequencing and error recovery behave correctly?
- Is the target connectivity and security design approved?
- Do business owners have representative test cases and approval criteria?
- Are coexistence, rollback and legacy decommissioning requirements documented?
Next step: build a defensible SAP PI/PO migration roadmap
The safest migration plan is not the slowest or the fastest. It is the one that clearly identifies what must change, what can be retired, what needs redesign and what business evidence is required to go live. SAP Integration Suite can be the foundation, but inventory quality, design decisions and accountable testing determine whether the transition is operationally sound.
SAPSOL Technologies can help structure readiness discovery, integration analysis, target-design discussions and migration-wave planning. For a detailed framework, see The 2027 SAP PI/PO Migration Playbook. You can also request a consultation with SAPSOL or review its SAP consulting services.
