# SAP PI/PO to Integration Suite Migration Readiness Assessment

> Source: https://netray.co/tools/sap-pi-po-to-integration-suite-migration-assessment
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Twelve questions that score how ready your PI/PO landscape is to move to SAP Integration Suite, with a plan per band.

## Category

sap

## Erp

SAP PI/PO

## Audience

- SAP integration architect
- SAP PI/PO developer
- SAP Basis administrator
- IT manager

## Tool

**Kind:** assessment

**Questions:**

#### Which PI/PO release and stack are you on?

**Options:**

##### PO 7.5 single stack (Java), recent SP

**Score:** 3

##### PO 7.5 on an older SP

**Score:** 2

##### PI 7.3x or 7.4 single stack

**Score:** 1

##### Dual stack PI (ABAP and Java)

**Score:** 0

#### How many integrated configurations (ICOs) and classic scenarios are active?

**Options:**

##### Under 50

**Score:** 3

##### 50 to 200

**Score:** 2

##### 200 to 500

**Score:** 1

##### More than 500

**Score:** 0

#### What is your adapter mix?

**Options:**

##### Mostly SOAP, REST, IDoc and HTTP

**Score:** 3

##### Significant SFTP/File, JMS or JDBC

**Score:** 2

##### Third party adapters (for example industry or legacy protocol adapters)

**Score:** 1

##### Custom developed adapter modules everywhere

**Score:** 0

#### Do you use ccBPM or NW BPM processes?

**Options:**

##### None

**Score:** 3

##### A few simple BPM processes

**Score:** 2

##### Several with correlation or human tasks

**Score:** 1

##### Many, business critical

**Score:** 0

#### How much Java mapping and UDF logic do you have?

**Options:**

##### Mostly graphical message mapping, few UDFs

**Score:** 3

##### Moderate UDFs and some XSLT

**Score:** 2

##### Many Java mappings

**Score:** 1

##### Heavy Java mappings with external libraries or lookups

**Score:** 0

#### Do you use the B2B add-on (EDI separator, EDI converters, AS2)?

**Options:**

##### No B2B on PO

**Score:** 3

##### A few partners

**Score:** 2

##### Many EDI partners via B2B add-on

**Score:** 1

##### B2B add-on is our main EDI hub

**Score:** 0

#### Is SAP Cloud Connector in place for on-prem connectivity?

**Options:**

##### Installed and used today

**Score:** 3

##### Planned and approved by security

**Score:** 2

##### Not discussed yet

**Score:** 1

##### Outbound cloud connectivity not allowed

**Score:** 0

#### How dependent is your monitoring on PO?

**Options:**

##### Simple message monitoring only

**Score:** 3

##### Alert rules in the PO alert framework

**Score:** 2

##### Solution Manager interface monitoring on top

**Score:** 1

##### Custom monitoring and reprocessing tools built on PO

**Score:** 0

#### Do you know your monthly message volume and how it maps to your Integration Suite licence?

**Options:**

##### Yes, measured and compared with our plan

**Score:** 3

##### Measured, not yet compared

**Score:** 2

##### Rough estimate only

**Score:** 1

##### Unknown

**Score:** 0

#### What are your team skills in Integration Suite (iFlows, Groovy, adapters)?

**Options:**

##### Team has built and run productive iFlows

**Score:** 3

##### Trained, a few pilots

**Score:** 2

##### PO skills only

**Score:** 1

##### Dependent on one person or an external partner

**Score:** 0

#### Have you run the Migration Assessment capability in Integration Suite against your PO?

**Options:**

##### Yes, report reviewed and scenarios categorised

**Score:** 3

##### Connected, report not reviewed

**Score:** 2

##### Planned

**Score:** 1

##### No

**Score:** 0

#### Where must the integration runtime run?

**Options:**

##### SAP cloud runtime is acceptable

**Score:** 3

##### Cloud for most, a few flows must stay local

**Score:** 2

##### Most runtime must stay on-prem (Edge Integration Cell needed)

**Score:** 1

##### Fully air-gapped, no cloud control plane allowed

**Score:** 0

**Bands:**

#### Ready to start migration waves

**Min:** 75

**Max:** 100

**Verdict:** Your landscape is mostly standard adapters and mappings with the connectivity and skills in place. You can plan waves and move scenarios with the migration tooling.

**Recommendations:**

- Group interfaces into waves by business process and adapter type.
- Use the Migration Tool in Integration Suite to generate iFlows from PO objects, then test each one.
- Run PO and Integration Suite in parallel per wave with a clear cut over per interface.
- Set up monitoring and alerting in Integration Suite before the first productive wave.

#### Prepare: inventory and redesign

**Min:** 50

**Max:** 74

**Verdict:** Migration is realistic but you need a complete inventory and decisions on the non standard pieces first.

**Recommendations:**

- Run Migration Assessment and classify every scenario by effort.
- Retire unused ICOs before you migrate anything.
- Decide connectivity: Cloud Connector, Edge Integration Cell or both.
- Train the team on iFlows and Groovy with one low risk pilot.

#### High effort: BPM and B2B redesign

**Min:** 25

**Max:** 49

**Verdict:** BPM processes, B2B and heavy Java mapping will need redesign rather than conversion. Plan this as a project, not a lift and shift.

**Recommendations:**

- Redesign BPM processes, for example as stateless iFlows with persistence or as SAP Build Process Automation where human tasks exist.
- Plan EDI on Integration Advisor and Trading Partner Management, partner by partner.
- Budget for testing with every external partner.
- Use the 2027 end of mainstream maintenance as the planning deadline, with extended maintenance only as a buffer.

#### Not ready

**Min:** 0

**Max:** 24

**Verdict:** Release, connectivity or runtime constraints block a move today. Stabilise and decide the target first.

**Recommendations:**

- Upgrade to PO 7.5 on a current SP to stay supported.
- Settle with security whether a cloud control plane is acceptable; if not, evaluate Edge Integration Cell or a non SAP on-prem middleware.
- Measure message volumes and document every interface.
- Revisit this assessment after those decisions.

## Content

**Intro:** This assessment scores an SAP PI or PO landscape on twelve factors that drive the effort to move to SAP Integration Suite, from release and adapter mix to BPM, B2B, connectivity and runtime location. The result band comes with a concrete next step list.

**Sections:**

#### Why the date matters

**Body:** SAP Process Orchestration 7.5 is part of SAP NetWeaver 7.5, which SAP supports with mainstream maintenance until the end of 2027 and offers extended maintenance for PO 7.5 until the end of 2030; confirm the current dates in the SAP Product Availability Matrix. Older PI 7.3x and 7.4 releases are already out of mainstream maintenance, so they should move to PO 7.5 or straight to the target. SAP's stated successor is SAP Integration Suite, which runs in the SAP Business Technology Platform, with Edge Integration Cell as a hybrid option when the runtime must stay in your own data centre.

#### How to use it

**Body:** Answer each question for the whole landscape, using the worst realistic answer where interfaces differ. The score is the percentage of the maximum, matched to four bands. Factors that typically turn a conversion into a redesign carry the most weight in practice: BPM processes, B2B add-on use, Java mappings with libraries, and custom adapter modules. Run the assessment again after Migration Assessment has produced a real inventory; the first pass is usually more optimistic than the data.

**Bullets:**

- Migration Assessment: connects to PO and rates each scenario by effort.
- Migration Tool: creates iFlows from PO integrated configurations.
- Edge Integration Cell: Integration Suite runtime on your own Kubernetes.

#### Worked example

**Body:** A manufacturer has PO 7.5, 180 ICOs, mostly IDoc and SOAP with 30 SFTP flows, two NW BPM processes, 40 EDI partners on the B2B add-on, Cloud Connector already used for SuccessFactors, and alerting in the PO alert framework. That lands in the Prepare band. The plan is to move IDoc and SOAP flows in waves with the Migration Tool, redesign the two BPM processes, and treat EDI partners as a separate track on Trading Partner Management.

#### Common mistakes

**Body:** Counting interfaces without retiring dead ones first, assuming every PO adapter has a one to one equivalent, ignoring message metering in the Integration Suite contract, and leaving monitoring until the end. Another frequent gap is reprocessing: operations teams used to resending messages in PO need the equivalent procedure in Integration Suite documented before cut over.

**Cta:** If you want an AI assistant that answers questions about your interface inventory, message errors and mappings from data that stays on your servers, we can build that alongside the migration.

**Faq:**

#### When is SAP PI/PO end of support?

**Answer:** PO 7.5 follows SAP NetWeaver 7.5: mainstream maintenance until 31 December 2027, with extended maintenance offered until the end of 2030 at extra cost. Check the SAP Product Availability Matrix for the current statement before planning.

#### Is there a tool to migrate PI/PO to CPI?

**Answer:** Yes. Integration Suite has a Migration Assessment capability that analyses PO content and estimates effort, and migration tooling in the Integration Suite design area that converts supported PO integrated configurations into iFlows. Converted flows still need testing and often adjustment.

#### Can we keep integration on-prem after PO?

**Answer:** Edge Integration Cell lets you run Integration Suite runtime in your own Kubernetes environment while design and monitoring stay in the cloud tenant. If no cloud control plane is allowed at all, you need a different on-prem middleware.

#### What usually needs redesign rather than migration?

**Answer:** ccBPM and NW BPM processes, B2B add-on EDI flows, Java mappings with external libraries, custom adapter modules, and any custom monitoring or reprocessing built on PO. Standard IDoc, SOAP and REST flows with graphical mappings usually migrate with the tooling.

## Search terms

sap pi po to cpi migration, sap pi po to integration suite migration, sap pi po end of life, sap pi po end of support, sap pi po support end date, end of life for sap pi po, edge integration cell

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json