Fiori & InRize

Neptune DXP or native SAP Fiori: how to choose?

Licensing, data access, mobility, clean core: choose and migrate in batches without disruption.

The author

Pierre-Éric Bouchez

Director & Partner, R&D unit

By Pierre-Éric Bouchez, published 25 August 2026

Share on LinkedIn

In brief

  • Neptune DXP and SAP Fiori both produce SAPUI5 applications; the difference lies in tooling, data and licensing.
  • Neptune speeds up development from ABAP, but adds dependency on a third-party vendor.
  • Native Fiori relies on SAP standards (OData, RAP, CAP) and on the clean core recommended for S/4HANA.
  • Migration is done in batches: both technologies coexist in the launchpad during the transition.

Key takeaways

01

When to keep Neptune

Recent and stable estate, heavy offline use, staying on ECC or on-premise S/4HANA, low licence cost.

02

When to move to Fiori

S/4HANA and clean core project, fewer vendors, screens covered by Fiori elements, scarce Neptune skills.

03

Migrate without disruption

Estate audit, scoping, OData or RAP redevelopment, testing and progressive cutover: the InRize approach.

04

Duration

An audit in a few weeks, then batches of one to three months, testing included.

Sources: Neptune Software, SAP Learning