SAP PO mainstream maintenance is closing in, and every client we work with is at some point on the runway. The PO-to-Cloud Integration migration is the named migration play in our practice. We have done enough of them to have a strong opinion about the order.
The order that works
- Inventory and triage. Every iFlow gets one of three tags: wave (port mechanically), rebuild (the design no longer suits cloud), retire (the consumer is dead). Triage by business owner, not by IT.
- Stand up Integration Suite in parallel. PO keeps running. New iFlows go to Integration Suite from day one - no exceptions.
- Wave the high-traffic, low-risk ones first. They prove the operating model.
- Rebuild the design-flawed ones. Take the opportunity to fix what was wrong.
- Retire the orphans. They will never be missed.
What kills a runway
- Trying to lift-and-shift the PO operations model. Cloud Integration's monitoring and DLQ patterns are different - design for them.
- Custom adapter modules in PO that have no Cloud Integration equivalent. Identify these early - the workaround is either custom adapter development on BTP or a redesign of the contract.
- BPM and ccBPM. Cloud Integration is not a BPM engine - if you have BPM workflows, plan a separate migration to Build Process Automation.