From 1 January 2028 there will be no more standard support for SAP Process Integration and Process Orchestration. Whoever doesn't plan now will migrate later under time pressure. I accompany your migration from architecture consulting to operations — as an independent freelancer, without tool bias.
End of mainstream maintenance for SAP PI/PO. After that no patches, no security updates, no new features.
Typical migration duration depending on complexity and number of scenarios — assessment, redesign, move, hypercare.
Mappings, adapters, error handling and operations concepts need to be rethought on the BTP — not just copied.
Starting after 2026 means a very tight risk buffer. Starting before end of 2025 still allows calm waves and enough hypercare time.
Inventory of your current PI/PO landscape. Classify scenarios, slice domains, draft target architecture on the BTP. Decision between Integration Suite, hybrid models and co-existence.
Integration Suite isn't automatically the right answer for every scenario. I evaluate neutrally: SAP on-platform options, event brokers, API gateways, and if relevant non-SAP alternatives like Boomi or MuleSoft — depending on your portfolio.
The blueprint becomes a reliable plan: wave by wave, with clear dependencies, test and cutover concept. Proven on the first 5–10 scenarios, then industrialised.
I stay hands-on: iFlow development, mapping redesign, adapter migration, Groovy scripts, API proxies. Always with review by your team so the solution stays when I leave.
After the cutover the work isn't done. I stay as sparring partner for your operations team — incident analysis, performance tuning, onboarding of further partners. Handover to clean operations.
I'm SAP-savvy but not SAP-dogmatic. Usually the migration ends up on SAP Integration Suite — but in justified cases on a hybrid or non-SAP solution. The three most common target pictures in my projects:
Cloud Integration, API Management, Integration Advisor, Event Mesh, Open Connectors — as a consolidated platform on the BTP. For most SAP-centric landscapes the most efficient path.
When event volume is high or non-SAP systems need to join asynchronously: Solace-based AEM for the event layer, CPI for the synchronous-procedural business.
Azure Integration Services, Boomi, MuleSoft, webMethods, Workato: make sense when an enterprise integration platform already exists or non-SAP systems set the tone. I evaluate objectively, not commercially motivated.
Structured quick-scan of your landscape. Inventory, complexity scoring, risk heatmap. At the end you know where you stand — in two working days.
Full target architecture, wave planning, tool decision, budget and time frame. Workshops with your team. Decision-ready for IT leadership.
Operational collaboration over the full duration — as architect, as hands-on engineer, as sparring partner. Part-time or full-time, remote or hybrid.
Technically: yes. Organisationally: no. A clean migration of 50–200 scenarios takes 12–24 months including test and hypercare phases. Anyone not in assessment by early 2026 runs into time pressure — and time pressure costs double in projects.
For SAP-centric landscapes usually yes. However, there are cases where an already-adopted iPaaS (Boomi, MuleSoft) or a dedicated event-broker solution (Solace, Kafka) makes more sense. I evaluate neutrally — I don't sell licences.
Part of it can be migrated automatically using the SAP Migration Assessment Tool — realistically 30–60% of scenarios depending on complexity. The rest needs to be redesigned. That's not a disadvantage: many legacy artefacts get cleaned up in the process.
As soon as external consumers (partners, mobile apps, storefronts) come into play: yes. API Management sits as a governance layer in front of your CPI iFlows and handles OAuth, rate limits, versioning, analytics and the developer portal.
I'm a freelancer, not a consultancy. Typically embedded in your team with a clearly defined scope. I bring knowledge in — and build it up. The goal is always that your team can continue independently afterwards.
It depends heavily on number of scenarios, complexity and target architecture. A blueprint typically takes 4–6 weeks. The full migration ranges from 6 person-months to several person-years depending on scope. Reliable numbers come from the assessment.
Write me — or book a 30-minute intro call directly. I usually reply within 24 hours.