Neptune DXP App Migration Wizard

The Neptune DXP App Migration Wizard runs entirely inside the AI experience panel of Naia Build within the Neptune DXP - Open Edition App Designer. It connects to your Neptune DXP - SAP Edition system over the existing remote system configuration, reads the source app, runs a non-destructive in-memory dry run to analyze and prepare the Neptune DXP - Open Edition version, and — once you confirm — saves the result as a new Neptune DXP - Open Edition app. All processing runs in your browser session. App data is not transmitted to any external server.

The Analyze step is a full in-memory conversion of the Neptune DXP - SAP Edition app to Neptune DXP - Open Edition format. It produces a categorized, per-app report of every element requiring attention before anything is written to Neptune DXP - Open Edition. Use this report to get a precise picture of post-migration work for your specific app, and to distinguish between items that affect the app’s functionality and those that are recommended for review.

The scope of any remaining manual work depends on how heavily your specific app relies on SAP-specific controls and services. The wizard’s built-in Analyze step produces a per-app report of every item requiring attention before any changes are committed.

The Neptune DXP App Migration Wizard handles all structural transformation between the two platforms automatically. This includes the full UI5 control and component tree, scripts, TypeScript resources, HTML fragments, event handlers, stylesheets, manifests, and translations. Back-end connectivity is also restructured automatically: Ajax ID logic is rewritten as TypeScript routed through the Neptune DXP - Open Edition proxy, OData model bindings are recreated for the Neptune DXP - Open Edition environment, REST API bindings receive generated runtime wrappers, and MockServer setups are converted to the Neptune DXP - Open Edition equivalent. Neptune DXP Open Edition-specific metadata fields are set to current best-practice defaults.

For a full breakdown of how each element is handled, see the migration pipeline summary in the migration reference.

The Analyze step identifies which elements in your specific app require attention before or after migration. The two categories to be aware of at this stage are:

SAP-specific elements with no Neptune DXP - Open Edition equivalent: certain control types (SAPUI5 suite controls, Value Help, API Factory) and app types (Custom Components) have no direct counterpart in Neptune DXP - Open Edition. The wizard replaces these with safe placeholders where possible and flags each occurrence in the Analyze report. Cross-app dependencies on other Neptune DXP - SAP Edition apps are also flagged and must be resolved separately.

Elements configured directly in Neptune DXP - Open Edition: some areas of a Neptune DXP - SAP Edition app, including UI5 model definitions, table column definitions, global settings, and i18n attributes, are most effectively established using Neptune DXP - Open Edition’s native tooling after migration. These are a normal part of the post-migration development workflow, not gaps in the migration output.

For the full detail of each category, flagged element types, and recommended actions, see Engineer action reference in the migration reference.

Once migration is complete, you can continue iterating on the app using Naia Build. App complexity is worth keeping in mind: smaller apps (roughly up to 30 components) tend to work well with Naia Build’s agentic capabilities straight after migration. For larger apps, Naia Build needs to examine every component to assess each prompt, which can affect the precision of the output. Connections and bindings may require some manual review and adjustment. Regardless of app size, Naia Build creates a new app version automatically after each prompt, so you can roll back to any previous state at any point and nothing is permanently lost.