Guide · Integration
SAP PO to BTP Integration Suite — a migration guide
SAP Process Orchestration (PO) reaches mainstream maintenance end in 2027. The path forward is SAP BTP Integration Suite — but a lift-and-shift wastes the moment. This guide covers the 4R framework, the four delivery phases, and how to keep migration governed at enterprise scale.
The 4R Framework
Every interface gets a decision
Migration is the moment to modernise — not to copy the past onto a new platform. The 4R framework forces a clean decision for every interface in scope, with a bias toward refactor and rebuild.
Retire
Rehost
Refactor
Rebuild
Delivery phases
The four phases of a governed PO migration
Phase 1 — Discover
Export your SAP PO configuration with Switch, build the full landscape view, and identify duplicate interfaces, dependencies, and high-risk patterns.
Phase 2 — Triage
Apply the 4R framework to every interface: Retire what's redundant, Rehost where commercials force it, Refactor to modern patterns, Rebuild where simplification wins.
Phase 3 — Design
Per-interface specifications for the target on Integration Suite: API-led where possible, event-driven where it fits, with NFRs, security model, and error/reprocessing patterns agreed before build.
Phase 4 — Build & Cutover
Wave-based delivery with parallel run, business reconciliation, and a cutover that decouples from S/4HANA timelines. CI/CD for iFlows, observability standards, and operational handover from day one.
Switch — built for this
Switch extracts your SAP PO landscape, applies AI-powered analysis across every interface, and generates a migration-ready backlog with auditable approvals. Don't run this migration on spreadsheets.