Skip to main content

Integration Migration · SAP BTP · Clean Core Readiness

Manufacturing SAP API Management SAP BTP SAP Cloud ALM

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

A Major Roofing Products Manufacturer Delivered 2026

Mindset migrated a large independent roofing manufacturer's legacy PI/PO interfaces to SAP BTP Integration Suite, reaching 100% process documentation in Signavio and a 100% first-pass testing rate before moving into the manufacturing application phase.

By the numbers

  • Integration process maps documented in Signavio

  • First-pass functional testing rate

  • 3 environments

    Dev, QA, and Production all migrated and governed

Before

Legacy PI/PO, limited visibility

  • On-premise SAP PI/PO middleware with rising operational overhead and constrained scalability.
  • Limited centralized observability, making it hard to know what was running and how.
  • Custom coupling between systems that did not align to Clean Core, complicating the path to S/4HANA.

After

SAP BTP Integration Suite, Clean Core ready

  • All in-scope interfaces rebuilt as modern iFlows on SAP BTP Integration Suite, with API Management governance and Cloud ALM monitoring.
  • Every iFlow documented as a BPMN 2.0 process model in Signavio, giving the team a living record and a de-risked S/4HANA migration path.
  • 100% testing pass rate and zero documentation defects before the project moved into the manufacturing application phase.

Why this matters

A conservative, family-owned manufacturer that needed to see proof before trusting a new platform. Mindset earned that trust by documenting every process, hitting 100% on testing, and leaving the team with a clean foundation for S/4HANA.

The challenge

One of North America's largest independent makers of asphalt shingles and waterproofing products ran its integration backbone on an on-premise SAP PI/PO landscape. That setup had served the company well, but it was accumulating operational overhead, making centralized observability hard to maintain, and constraining the team's ability to govern interfaces consistently.

The bigger issue was what came next. An S/4HANA transformation was on the roadmap, and the existing middleware was not aligned to SAP Clean Core principles. Custom coupling between systems would complicate the ERP move. The manufacturer needed its integration layer cleaned up and cloud-ready before that transformation could begin in earnest.

The company's culture is conservative and evidence-driven. Any new platform had to be proven against security requirements before the team would trust it in production.

What we did

Mindset ran the migration in structured phases from assessment through go-live and hypercare, following the SAP-recommended migration path from the SAP Migration Guide for Process Orchestration.

Every in-scope PI/PO interface was assessed for cloud readiness. Point-to-point integrations not suited for cloud were documented and excluded from scope. The rest were rebuilt as modern iFlows on SAP BTP Integration Suite across Development, QA, and Production environments.

Four technical pillars defined the approach. SAP BTP Integration Suite served as the runtime. SAP API Management provided consistent exposure, security, throttling, and lifecycle governance for all interfaces. SAP Signavio Process Modeler captured a BPMN 2.0 process model, a documented digital twin, for every iFlow. SAP Cloud ALM handled monitoring, alerting, and production-readiness across the estate.

Legacy PO 7.5 artifacts that could not be automatically converted were manually recreated and optimized into modern iFlow designs. A dedicated functional testing team was onboarded and aligned to existing RICEF documentation and the company's strict security requirements. The project ran on a remote delivery model with daily standups Monday through Thursday, weekly cadence calls, and Jira as the single source of truth. The engagement also included an SAP Cyber Security Report Mitigation workstream and BTP enablement advisory services.

The outcomes

The migration hit its quality benchmarks before moving into the manufacturing application phase. All in-scope integrations passed code review and technical testing, clearing enterprise readiness. Every integration process map was documented in Signavio, a 100% documentation rate with zero defects. Initial functional testing batches came back at a 100% pass rate.

Beyond the migration itself, the work established a clean, governed foundation for the company's future S/4HANA transformation. Business users gained the ability to update pricing and promotion logic without heavy ABAP development. The documented process flows in Signavio de-risk the eventual ERP move and give the team a living record of how their integrations actually work.

If we built this today

Concept · not delivered scope

Integration that watches and heals itself.

This is a forward-looking concept, not the scope we delivered on this engagement. It is the build we would reach for now, grounded in SAP that ships today.

This engagement moved a roofing products manufacturer's integration backbone off on-premise PI/PO and onto SAP BTP, so the modern build is an agent that keeps those cloud iFlows healthy and Clean Core ready instead of waiting for the next middleware incident.

The data product

Integration Observability Data Product

A governed data product on SAP Business Data Cloud that grounds the agent in real message flow, latency, and error semantics across every migrated interface. It gives the watcher one trustworthy view instead of scattered middleware logs.

Data product on Business Data Cloud

The Joule agent

iFlow Health Watcher

Reads interface telemetry, message logs, and error patterns across SAP Integration Suite, then proposes fixes, retries, and Clean Core alignment steps for the migrated iFlows before a flow degrades. It maps each legacy PI/PO interface to its cloud target and flags where custom coupling still needs to go.

SAP Integration Suite, SAP API Management, SAP BTP, SAP Cloud ALM · PROPOSE · Interface uptime and migration backlog burndown, fewer integration incidents per release

The Fiori app

SAP Integration Suite (Flow Builder, not a Fiori app)

Integration lives on SAP BTP, not in an S/4HANA Fiori app, so the honest home is the Integration Suite design and monitoring console where Joule helps build and watch iFlows. Joule assists inside the Flow Builder pattern rather than in the launchpad.

On SAP BTP, not the Fiori launchpad

We mine the real interface flows in SAP Signavio first, map the old estate to the new one in SAP LeanIX, and let MIND accelerators carry the legacy integrations across without losing the institutional knowledge.

The Joule Agent Factory Process intelligence

What we built

  • 100% of in-scope integrations code-reviewed and technically tested

    PI/PO to Integration Suite migration

    Full assessment and rebuild of in-scope SAP PI/PO interfaces as modern iFlows on SAP BTP Integration Suite across Dev, QA, and Production, following the SAP-recommended PO migration path.

  • 100% of integration process maps documented, zero defects

    Signavio BPMN 2.0 process documentation

    A digital twin for every iFlow, documented in SAP Signavio Process Modeler to create a living process record and de-risk the S/4HANA transformation.

  • Centralized governance applied across all in-scope integrations

    SAP API Management governance layer

    Consistent API exposure, security policy enforcement, throttling, and lifecycle management for all migrated interfaces.

  • Centralized observability across the BTP integration landscape

    SAP Cloud ALM monitoring

    Production-readiness monitoring and alerting across the integration estate, replacing the limited observability the team had on the legacy middleware.

  • 100% first-pass testing rate on initial functional test batches

    Functional testing program

    A dedicated functional testing team aligned to existing RICEF documentation and the manufacturer's security requirements, validating each interface before promotion.

  • Security requirements validated alongside the migration

    SAP Cyber Security workstream

    A parallel cyber security report mitigation workstream addressing identified security findings as part of the broader BTP migration engagement.

  • Internal team readiness for S/4HANA-era operations

    BTP enablement and advisory

    Platform enablement and advisory services to build internal team capability on BTP Integration Suite, positioning the company to operate the platform independently.