SAP PI/PO migration guide
A practical framework for your move to SAP Integration Suite.
SAP ends mainstream maintenance for PI/PO on December 31, 2027. Extended maintenance runs only to 2030, at extra cost. A migration of any real size takes long enough that the deadline is already inside your planning horizon.
What’s inside the guide
- Why migrate to SAP Integration Suite What Cloud Integration, API Management, Advanced Event Mesh and Integration Advisor give you that PI/PO never did.
- Sizing and planning your migration Target strategy with ISA-M, landscape assessment, pilot project, 1:1 vs. redesign, and the business case.
- Architecture and platform decisions Where to redesign iFlows, reverse proxy and API management, security by design, and Cloud vs. Edge Integration Cell.
- Executing the migration, object by object ICOs, classical scenarios, channel templates, connectivity (File, JMS, IDoc, RFC, REST, JDBC, OFTP) and content conversion.
- Governance: workflow, testing, go-live Release planning, developer guidelines, regression testing with real messages, transport, and rollback.
- Choosing your migration tooling and partner SAP’s migration tool vs. Figaf, and what to ask an implementation partner.
- How Figaf supports your migration Assessment, automated migration, testing, governance and transport.
- Managing B2B and Trading Partner Management Why native TPM struggles at scale, and how to keep it manageable.
- Conclusion and next steps
Five things to get right
Plan before you migrate
Skipping the sizing step is the single biggest cause of migrations running over budget. Decide your target integration strategy first; SAP’s ISA-M is a good starting point.
Run a representative pilot
10-100 interfaces, depending on landscape size, covering mappings with function libraries, Java mappings, different adapter types, routing and EDI. Take at least some all the way to production.
Migrate 1:1 where you can, redesign where it pays off
The right approach is almost always hybrid: 1:1 to control cost and risk, redesign where modernization delivers real value.
Test with real production messages
Testing is where most migration effort goes. Automated regression testing, replaying PI/PO messages through Cloud Integration and comparing the output, is the most efficient way to validate at scale.
Don’t forget transport
“Export the iFlow” sounds like a two-minute job. Dependencies, externalized parameters and security material make transport the step most estimates leave out.
The life of one migrated interface
- Understand: pattern, and whether to migrate 1:1, redesign, replace or retire
- Migrate: routing, mappings, function libraries and channels
- Configure: adapter settings and security material in each tenant
- Fix: message mappings, UDFs and scripts
- Test: real production messages and automated regression
- Document: what changed, and which tests prove it works
- Transport: through test to production, with dependencies checked
- Go live: low-traffic window, partners informed, rollback plan ready
- Evaluate: lessons learned into the next release
“Everybody can migrate to iFlows. You only get the credit once you’ve actually tested the integration.”
Plan your migration
Migration checklist
Are you ready to start? Check the foundation for your migration before the project begins.
Migration estimator
Estimate time and cost, and compare a manual approach with a tool-assisted one.
Free Migration Edition
Assessment and migration dashboard, trial migration of up to 10 ICOs, and 30 days of automated testing.
Frequently asked questions
When does SAP PI/PO support end?
Mainstream maintenance ends December 31, 2027. Extended maintenance is available until December 31, 2030 at additional cost.
How long does a PI/PO migration take?
It depends on the number and complexity of interfaces. Run a pilot to measure your own per-interface time, then use the migration estimator.
Can I migrate without upgrading PI/PO first?
With Figaf, yes: ICOs and dual-stack objects from PI 7.11 through 7.5 are supported. SAP’s own migration tool supports PI/PO 7.31, 7.4 and 7.5.
Should I use SAP’s migration tool or Figaf?
Neither handles every scenario best. Pilot both against a representative set of your own interfaces and compare.
Why Figaf
In 2021, Figaf won SAP’s Hack2Build competition to automate PI/PO migrations. The winning prototype has since been developed with customers and partners in real projects. In Figaf customer projects, automating assessment, migration, testing and transport has reduced overall migration effort by at least 30%.
Figaf migration article series
14 articles that take you through a migration, from planning to testing. Read them in order, or pick the step you are at.
Plan
Migrate
- ICO Migration
- Classical or Receiver Determination Migration
- What is your workflow for your migration?
- SAP PI Connectivity and SAP Cloud Integration
- Mapping Channels for SAP PI to Integration Suite
- Modification of ICOs before your migration
- Migration of SAP PI File Channels with Content Converter
- Guide for migrating PI/PO B2B mappings to Integration Suite B2B TPM
Test and transport
Ready to go forward with your migration?
Start with the free Migration Edition, or talk to us about your landscape.