Skip to main content

SAP Integration Suite

Retire PI/PO before 2027 and build the integration layer your agents will run on.

Your SAP estate already talks to dozens of systems, partners, and cloud apps. We move that traffic off PI/PO and CPI NEO onto SAP Integration Suite, then design API, event, and B2B patterns that hold up under real volume. As one of the select partners in SAP's Migration Factory program, we retire legacy integration at SAP-internal pace and leave you a layer that is ready for the agent traffic coming next.

Start a conversation See related case studies
SAP Integration Suite sketch
“The Nervous System,” a placeholder by Gemini 3 Pro ImageJun 20262,082 tokensthe story →
Why Mindset

Selected by SAP for the migration, deep enough to have shaped its tooling

Retiring PI/PO runs through SAP's Migration Factory, a select group of partners SAP onboards and routes migration work to. Mindset is one of them, and we have gone further than most: we helped extend SAP's own migration tooling.

  • SAP Migration Factory partner

    One of the select group of partners SAP brings into its PI/PO and CPI NEO migration program and routes assessments to. A program you are onboarded into, not a badge you buy.

  • SAP BTP Expert, Integration specialization

    The SAP Partner Finder competency for Integration Suite specifically, not general BTP. Backed by a deep bench of integration architects.

  • We helped extend SAP's migration tooling

    Mindset worked directly with SAP engineering to make SAP's open-source CPI-NEO-to-Cloud-Foundry converter run on Cloud Foundry, then used it to auto-migrate 251 iFlows for Lucid Motors.

  • First US-based SAP AppHaus partner, SAP Gold Partner

    A design-and-build credential most integration shops do not hold, so the interfaces we ship are usable and governed, not just connected.

The clock is real: SAP ends mainstream maintenance for PI/PO in 2027, and CPI NEO is already being retired.

Why now

PI/PO ends in 2027, and integration is no longer just data moving between systems.

The reality

  • SAP PI/PO hits end of mainstream maintenance in 2027, and the dual-stack Java upgrade weekends are not coming back.
  • CPI NEO is being retired, so even teams already on the cloud have a forced cutover ahead of them.
  • Most landscapes have an accidental architecture: PI/PO, point-to-point scripts, and tools like Apache NiFi stacked up as technical debt.
  • No one has a clean inventory. Interface counts are guessed in spreadsheets, and the SAP assessment tool over- and under-states complexity on the hard ones.

What changes

  • A real inventory first

    We connect to PI/PO and extract every interface, adapter, and message type, then sort them into migration buckets so the plan is built on facts.

  • Pattern-based migration

    We map your interfaces to a standardized pattern library (ERP-to-third-party, data sync, file transfer, B2B) and run them in parallel instead of one at a time.

  • Modern architecture, not a copy

    API-led and event-driven design aligned to Clean Core, so you are not rebuilding the same brittle interfaces in a newer tool.

  • Migration Factory pace

    As one of SAP's select Migration Factory partners, we retire PI/PO at SAP-internal speed, with the accelerators and tooling the program carries.

  • Ready for agent traffic

    We build A2A and MCP-ready flows now, so when agents need to call your SAP processes the integration layer is already there and governed.

  • Governed cutover

    Transport management, parallel runs, and phased go-live so production switches over without the firefighting.

Critical insight

Since Sapphire 2026 unified BTP into the SAP Business AI Platform, Integration Suite carries more than system-to-system data. With the A2A protocol now bidirectional and MCP servers exposing tools to agents, your integration layer is the road every agent drives on. Build it once, build it right.

Capabilities

What we actually do inside Integration Suite

We deliver Integration Suite work across manufacturing, distribution, energy, and beyond, from net-new API practices to full PI/PO retirements. Here is where teams ask us in.

01

Integration assessment and roadmap

Before any build, we map what you have and what it will take to move it.

  • Secure extraction of every PI/PO and CPI interface into a catalog
  • Complexity, volume, and dependency analysis per interface
  • A sequenced roadmap with effort estimates and a guaranteed cost

02

PI/PO and CPI NEO migration

The core engagement: getting off legacy runtimes before they go dark.

  • Pattern-based migration with parallel development for speed
  • Reusable retry and error-handling frameworks for resilient interfaces
  • Phased, parallel-run cutover built for minimal downtime

03

API Management

Governed, reusable APIs instead of one-off connections.

  • API proxies, policies, and a developer portal
  • Reusable business APIs across SAP and non-SAP systems
  • Security, rate limiting, and versioning that survives audit

04

Event-driven integration with Event Mesh

Real-time, loosely coupled flows for processes that cannot wait on batch.

  • Event streaming for supply chain, finance, and manufacturing
  • Decoupled producers and consumers that scale independently
  • Patterns that feed real-time apps and reporting

05

B2B, EDI, and partner connectivity

The trading-partner traffic that keeps orders and invoices moving.

  • EDI and B2B onboarding for customers and vendors
  • IDoc, file/SFTP, and modern REST/SOAP patterns side by side
  • Trading partner management and monitoring

06

Agent-ready integration (A2A and MCP)

Where Integration Suite is going, and where we are already building.

  • MCP servers that expose SAP processes to agents under control
  • Bidirectional A2A flows between SAP and external agents
  • AI-enriched iFlows for validation, anomaly checks, and decisions

07

Hybrid and multi-cloud connectivity

Tying the cloud back to what still runs on-prem.

  • Cloud-to-on-prem via Cloud Connector with secure tunnels
  • Integration across hyperscalers and third-party systems
  • High-throughput handling for transactional and bulk data
MIND · our toolchain

MIND goes deepest in Integration Suite

MIND is the proprietary set of accelerators our consultants run on every engagement. It is richest here, because Integration Suite is where we have run the most migrations, and each one sharpens the next.

Explore the MIND toolchain
  1. 01 Interface inventory extractor Connects to PI/PO and CPI and pulls every interface, adapter, and message type into a scored catalog, so the plan is built on facts, not a spreadsheet guess.
  2. 02 Migration pattern library ERP-to-third-party, data sync, file transfer, and B2B/EDI patterns. We map each legacy interface to a modern one and build them in parallel, not one at a time.
  3. 03 Reusable retry and error-handling framework Resilient iFlows that recover from transient failures on their own. On Lucid Motors it covered 49 interfaces, with zero retry failures since go-live.
  4. 04 SAP migration-tool extension We extended SAP's open-source CPI-NEO-to-Cloud-Foundry converter to run on Cloud Foundry, then auto-migrated 251 legacy iFlows with it.
Real impact

Migrations that land without the firefighting

We have done SAP Integration Suite work across enterprise landscapes in manufacturing, distribution, energy, and more, from full PI/PO and CPI NEO migrations to net-new API and event practices. The ones we can name:

Lucid MotorsAutomotive
65 interfaces

migrated off deprecated CPI NEO with zero downtime

When SAP announced the retirement of the CPI NEO runtime, Lucid's entire integration landscape was at risk. We stood up a dedicated BTP sub-account on Cloud Foundry and migrated all 65 business-critical iFlows across EDI, foreign trade, order management, and e-commerce. A reusable retry framework now covers 49 of those interfaces, and there has not been a single retry failure since go-live.

Border StatesDistribution
40% lower cost

30+ integrations rebuilt on BTP Integration Suite, 3x faster

Border States ran an accidental architecture of Apache NiFi and PI/PO workloads that had become expensive technical debt. We profiled 30+ legacy integrations, built a standardized pattern library, and ran developers in parallel to migrate them all in 22 weeks at 40% lower cost and a 100% success rate. They decommissioned NiFi and made Integration Suite their strategic platform, and one tool built on it cut a 100-line order from about two hours to about two minutes.

More SAP Integration Suite work

More of the same, anonymized at the client's request.

See all case studies
Manufacturing

A major roofing products manufacturer moves its integration backbone off PI/PO and onto SAP BTP, Clean Core ready

Read the case study Manufacturing

How a global contract electronics manufacturer stood up a net-new API practice on SAP BTP

Read the case study
How we engage

Assess, migrate, govern

A migration stalls when discovery drags or when interfaces get rebuilt one at a time. We front-load the inventory and run the build in parallel.

  1. Phase 1

    Assess

    2-4 weeks

    Connect to PI/PO, extract a full interface catalog, score complexity and volume, and sort interfaces into migration buckets. You leave with a roadmap, an effort estimate, and a guaranteed cost.

  2. Phase 2

    Design and plan

    2-3 weeks

    Stand up the BTP sub-account with dev, test, and prod separation, secure connectivity, and role-based access. Define the API, event, and B2B patterns each interface will move to.

  3. Phase 3

    Build and migrate

    varies by scope

    Run developers in parallel against the pattern library, with reusable retry and error handling baked in. Roughly 20 weeks for a 100-interface estate versus 32 the traditional way.

  4. Phase 4

    Test and cut over

    2-4 weeks

    Unit, end-to-end, and UAT cycles with functional SMEs, then a phased parallel-run go-live and hypercare. The point is no surprises in production.

Common questions

Questions teams ask before they start

When does PI/PO actually end?
SAP's end of mainstream maintenance for PI/PO is 2027. That is close enough that a full migration, which can run several months for a real estate, needs to be on the roadmap now. CPI NEO is being retired too, so even teams already in the cloud have a cutover ahead of them.
How long does a migration take?
It depends on interface count and complexity, but a 100-interface estate runs roughly 20 weeks our way versus about 32 traditionally. We get there with a full inventory up front and parallel development against a pattern library, not by cutting corners on testing.
Why Mindset over another SAP partner?
We are one of the select partners SAP onboards into its Migration Factory program for retiring PI/PO, and we hold an SAP BTP Expert competency with Integration as a specialization on SAP Partner Finder. We have delivered Integration Suite migrations and builds across many enterprise landscapes, including full PI/PO and CPI NEO migrations for Lucid Motors and Border States.
Do you just move the interfaces as they are?
No. A straight lift-and-shift rebuilds the same brittle interfaces in a newer tool. We redesign to API-led and event-driven patterns aligned to Clean Core, so the result is an integration layer worth keeping, not a copy of the old one.
What does agent-ready integration mean for us?
Since Sapphire 2026, Integration Suite carries agent traffic as well as data. With the A2A protocol bidirectional and MCP servers exposing tools safely, we can build flows now that let agents call your SAP processes under governance. You do not have to act on it today, but building toward it means you are not re-platforming again in two years.
Who should do the migration: an SI, a hybrid team, or our own people?
Most teams land on a hybrid: we run the assessment, the pattern library, and the hardest interfaces, while your people learn the platform alongside us and own the long tail. Pure-internal stalls on the 2027 clock; pure-outsourced leaves you unable to maintain what you bought. We staff for the handoff from day one.
What if we will not finish before 12/31/2027?
Mainstream maintenance ends 2027-12-31; SAP offers extended maintenance to 2030-12-31 at a premium, so you are not off a cliff, but you are paying more to run something with no future. The right move is to start the assessment now (it is only a few weeks), get a real interface inventory and a phased plan, and migrate the critical traffic first so the deadline stops being a risk.
The migration playbook

Everything we have learned getting teams off PI/PO

The deadline math, the questions that make a migration predictable, and the real numbers from migrations we have run.

The 2027 PI/PO deadline, and how to cut your timeline 40%

Why the clock is real, and how the M-Suite accelerator compresses the work.

Read

A discovery starter: 12 questions that make a migration predictable

The questions to answer before you scope, so the estimate actually holds.

Read

Ten reasons to move from PI/PO to Integration Suite

The case for the move, beyond the maintenance deadline alone.

Read

Lucid Motors: 65 interfaces migrated, zero downtime

When SAP retired CPI NEO, we moved every business-critical iFlow to Cloud Foundry.

Read

Border States: 30+ integrations rebuilt, 40% cheaper

A full PI/PO and Apache NiFi retirement onto Integration Suite, in 22 weeks.

Read

M-Suite accelerator, now generally available

The estimator and automation that make our migrations faster and more predictable than SAP-standard tooling.

Read
Recent thinking

From our Insights.

All Insights
Adjacent practices

More of our SAP technical work.

SAP BTP

The foundation your SAP estate extends, integrates, and runs AI on.

Read more

S/4HANA

The core your business runs on, and the foundation everything else gets built on top of.

Read more

Application Management Services

SAP support from the people who understand the architecture, not a generic helpdesk.

Read more

SAP Joule Agents

An agent factory for SAP

Read more

Clean Core

Get your SAP core standard, governed, and upgrade-safe, so the AI era can actually be trusted to run on it.

Read more

Business Data Cloud

The path from BW to intelligent enterprise

Read more

Talk to a SAP Integration Suite partner.

The first call is a working session, not a pitch. Bring a real problem and we’ll whiteboard it with you.

Start a conversation