SAP Integration Suite migration
Automotive Cloud Foundry SAP BTP SAP CPI (NEO, legacy) Featured
Lucid Motors: 65 interfaces off deprecated CPI NEO, zero downtime
Delivered 2025
Lucid Motors reached 50% faster integrations after Mindset moved 65 business-critical interfaces off SAP's deprecated CPI NEO, with zero downtime and zero defects at cut-over.
By the numbers
-
Faster integrations on the new platform
-
Of 65 interfaces migrated, zero defects
-
0
Downtime on a live manufacturer
-
0
Retry failures across 49 hardened interfaces
Before
CPI NEO, on a deadline
- SAP's deprecation of CPI NEO put Lucid's whole integration estate at risk.
- 65 business-critical interfaces facing the NEO shutdown.
- No window for downtime on a live manufacturer.
After
Integration Suite on Cloud Foundry
- All 65 interfaces designed, built, tested, and deployed on Integration Suite.
- A reusable retry iFlow pattern engineered around the platform's JMS queue limits.
- Zero residual defects and zero downtime at cut-over.
“We truly appreciate everyone's hard work and commitment. This is a significant step forward for Lucid's SAP Landscape and Architecture, which aligns with SAP's Strategic direction, bringing cutting edge capabilities with scalability and accelerated digital transformation.”
Why this matters
Everyone migrates PI/PO. Moving off NEO to Cloud Foundry with a custom retry pattern and zero defects is the harder, more current problem, and the proof the platform play works.
The challenge
SAP set a shutdown date for CPI NEO, and Lucid Motors ran its whole integration estate on it. 65 business-critical interfaces, the ones behind EDI, foreign trade, sales and order management, business reporting and e-commerce, had to move to SAP Integration Suite on Cloud Foundry before NEO went dark.
Lucid is a live manufacturer. There was no window to take orders, shipments, or trade compliance offline while the migration happened.
Lucid also wanted the new interfaces to heal themselves. When a network timed out or a downstream service went quiet, the integration should retry on its own instead of waking someone up at 2am.
What we did
Mindset, a Minneapolis SAP Gold Partner, ran the work as a Scrum engagement with two-week sprints, daily standups, weekly cadence calls, and monthly leadership reviews. The first move was a clean BTP Integration Suite sub-account under Lucid's global enterprise account, split into dev, test, and prod, with secure connectivity through Cloud Connector, certificates, OAuth 2.0, and SFTP, plus role-based access and CTMS transport management for governed promotion.
The team worked directly with SAP engineering to get SAP's open-source CPI-NEO-to-Cloud-Foundry migration tool running on Cloud Foundry. That auto-converted 251 legacy iFlows so the team could do real impact analysis, clean out the dead weight, and focus on the 65 interfaces that were still active.
The resiliency ask got its own answer: one reusable, parameterized retry iFlow pattern with configurable retry limits, delays, and escalation, engineered around the JMS queue limits on the platform. The same pattern was applied uniformly across 49 interfaces, so retry behavior is consistent and tunable instead of hand-coded per flow.
Cut-over went in phases aligned to business function, each one validated with parallel runs before the old NEO flow was retired. After go-live came two weeks of hypercare and a full runbook and documentation handover so Lucid's own team owns the platform. Connected systems spanned Anaplan, Ceridian, Coupa, Salesforce ESPP, GTS, MES, TrueCommerce, CFS, V360, and SAP ECC.
The outcomes
All 65 contracted interfaces were designed, built, tested, and deployed on Integration Suite on Cloud Foundry with no residual defects at cut-over. The 49 interfaces carrying the retry pattern logged zero retry failures after go-live.
Only 6 minor production items surfaced during hypercare, and two of those turned out to be enhancement requests rather than problems. Every one was resolved inside SLA.
Lucid hit business continuity well ahead of the NEO sunset, on a platform with lower latency and higher throughput. The public Mindset case study headlines the result as 50% faster integrations.
If we built this today
Concept · not delivered scopeA watcher for every interface.
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.
When SAP set the CPI NEO shutdown date, 65 business-critical interfaces behind EDI, foreign trade, order management, reporting and e-comm had to move and then stay healthy without anyone firefighting transient failures by hand.
The data product
Integration observability data product on SAP Business Data Cloud
A governed data product that grounds the agent in real message history, retry outcomes and SLA breaches across all 65 interfaces, so its proposals reflect how each flow actually behaves rather than a guess.
Data product on Business Data Cloud
The Joule agent
iFlow Health Watcher
Reads runtime telemetry across the Integration Suite tenant, message logs, retry counts, latency and throughput per iFlow, and watches for the transient failures that used to mean manual firefighting. It proposes the retry or reconnect action and flags any flow drifting toward a hard failure before it breaks.
SAP Integration Suite, SAP BTP, Cloud Foundry, Cloud Connector · PROPOSE · Post-go-live retry failures and unplanned integration downtime
The Fiori app
Integration Suite monitoring with Joule (BTP, not a Fiori app)
This one lives in SAP BTP, not the S/4HANA launchpad, so there is no single OOTB Fiori app to name here. The honest fit is Joule embedded in Integration Suite monitoring, surfacing failing messages and proposing the fix in context.
Lives in SAP BTP, not the Fiori launchpad.
We would mine the integration estate in SAP Signavio first, map the landscape in SAP LeanIX, then let MIND accelerators carry the old iFlows across to the new platform with the self-healing logic baked in.
What we built
-
65 of 65 interfaces migrated · zero defects at cut-over
NEO to Cloud Foundry migration
All active CPI NEO interfaces redesigned, built, tested, and deployed on SAP Integration Suite on Cloud Foundry.
-
Applied across 49 interfaces · zero post-go-live retry failures
Reusable retry iFlow pattern
One parameterized retry flow with configurable limits, delays, and escalation, engineered around the platform's JMS queue limits and applied uniformly.
-
251 legacy iFlows auto-converted
SAP migration tool, extended for Cloud Foundry
Worked with SAP engineering to run SAP's open-source NEO-to-Cloud-Foundry tool on Cloud Foundry, auto-converting legacy iFlows for impact analysis and cleanup.
-
3 governed environments · governed transport via CTMS
Clean BTP governance foundation
A dedicated Integration Suite sub-account split into dev, test, and prod, with CTMS transport management, Cloud Connector, OAuth 2.0, certificates, SFTP, and role-based access.
-
Zero downtime on a live manufacturer
Phased, zero-downtime cut-over
Cut-over sequenced by business function, each phase validated with parallel runs before the old NEO flow was retired.
-
6 minor items in hypercare, all resolved within SLA
Hypercare and full handover
Two weeks of hypercare plus a complete runbook and documentation handover so Lucid's own team operates the platform.
-
5 business domains · 11+ connected systems
Enterprise integration coverage
Interfaces spanning EDI, foreign trade, sales and order management, business reporting, and e-commerce, connecting Anaplan, Ceridian, Coupa, Salesforce ESPP, GTS, MES, TrueCommerce, CFS, V360, and SAP ECC.
A look at the work
