Lower costs
Lower Neptune DXP licence costs and less dependency on a third-party vendor, with ROI quantified before you start.
R&D unit, an InTenz solution
InRize: migrate from Neptune DXP to native SAP Fiori / UI5
A packaged, tooled solution to move off Neptune DXP and return to the SAP standard.
- 225+
- apps migrated
- 280,000+
- users served
- 0
- service interruptions
SAP standard
Native SAP Fiori / UI5 apps, integrated with the launchpad and SAP BTP, in line with clean core principles.
No disruption
ABAP backend and business logic retained, app-by-app cutover, no service interruption.
How it works
From Neptune DXP to native SAP Fiori / UI5
We replace the UI layer and keep the ABAP backend: business logic stays where it is.
Neptune DXP apps
UI on a third-party platform
Subscription and vendor dependency
Automated migration- 1Analyse
- 2Regenerate
- 3Test and cut over
SAP Fiori / UI5 apps
Native SAP UI, launchpad
SAP standard, clean core, SAP BTPABAP backendBusiness logic and data
Kept as is, no rewrite- 1
Analyse
Map functions and backend bindings.
- 2
Regenerate
SAPUI5 interface generated, automatic migration rate measured.
- 3
Test and cut over
Testing, SAP transports, app by app.
What changesThe interface, now native SAP.
What stays the sameYour ABAP backend, your processes, your data.
The tool in action
InRize, from the inside
The migration cockpit compares generated code with local code, diagnoses errors and keeps track of every manual change.
- 01Assisted diagnosisA runtime error is analysed: its cause is explained, the places involved are found and the fix is applied directly to the local code.
- 02Tracked manual changesEvery developer change is detected and described line by line, then flagged to be replayed after each new code regeneration.
Simulator
Migration effort divided by ten
Estimate the workload needed to move your Neptune apps to SAP Fiori, by hand or with InRize.
The figures in euros are established with you, based on your estate.
Indicative orders of magnitudeBased on our projects, excluding acceptance testing by your key users and post-migration maintenance.
The actual figures are established during the audit of your estate.
Migration effort divided by
migration workload
Our InRize offers
Three ways to deploy InRize
Depending on your teams, your deadlines and your applications, InTenz migrates for you, makes your teams autonomous, or combines both.
Discover InRizeCommon to all three offersInRize tool rental for the whole migration.
01
Offer 1: turnkey
InRize Delivery
InTenz migrates your Neptune estate, committed to both deadlines and results.
02
Offer 2: guided autonomy
InRize Enable
Your teams migrate with InRize, InTenz trains and supports them.
03
Offer 3: tailored
InRize Hybrid
InTenz or your teams: each application goes to the right hands, based on its criticality, complexity and confidentiality.
Compare the offers
| What is included | InRize Delivery | InRize Enable | InRize Hybrid |
|---|---|---|---|
| InRize tool rental | |||
| Audit of your Neptune DXP estate | Optional | ||
| Scoping document | Optional | ||
| PoC on a first application | Optional | ||
| Migration delivered by InTenz | Fixed price | Scope entrusted to InTenz | |
| Training your teams | Scope taken over by your teams | ||
| Commitment | Deadlines and results | InTenz expertise on hand | Results on the fixed price, expertise on the rest |
| Contract model | Fixed price | Time and materials | Fixed price + assistance |
Security
Your code stays with you
Code security
No external AI: your code never leaves the tool
InRize does not call any AI model (LLM) or any external service to transform your code.
All conversion rules are built into the tool, which does all the processing: your code is never sent outside.
These rules grow with every release, published weekly.
- No LLM calls
- Built-in conversion rules
- A new release every week
FAQ
Do we have to migrate all Neptune apps at once?
No: in batches, starting with the most critical or costly ones.
Neptune DXP and Fiori coexist in the launchpad; each batch is approved before the next one.
Do we lose functionality when leaving Neptune?
The target is functional parity as a minimum.
Does InRize use AI to transform the code?
No.
No AI model (LLM) or external service is involved: all conversion rules are built into the tool and your code is never sent outside.
The rules grow with every weekly release.
Is InRize compatible with S/4HANA?
Yes: Fiori is the native S/4HANA experience, and SAPUI5 relies on the OData, CDS and RAP standards.
Migrating avoids maintaining two UI technologies, in line with clean core principles.
Your InRize contact
Frédéric Branchi
Head of Sales
“I am available to discuss your application estate and your priorities.”
Request an InRize demo