Miri

Migration Specialist

Miri is your AI-powered Application Migration Specialist on the Simplifier platform — she analyzes legacy applications from SAP ABAP, Neptune SAP Edition, Neptune Open Edition, Lotus Domino, and Vibe Coding, and migrates them to Simplifier with dramatically less effort.

Capabilities

SAP ABAP Legacy Analysis & Migration — analyzes ABAP codebases and migrates custom programs, reports, and modules to Simplifier
Neptune SAP Edition Migration — converts Neptune DXP applications running inside SAP to native Simplifier applications
Neptune Open Edition Migration — migrates standalone Neptune Open Edition apps to the Simplifier platform
Vibe Coding App Modernization — takes AI-generated prototype code and hardens it into production-grade Simplifier applications
Lotus Domino Application Migration — analyzes legacy Lotus Domino/Notes applications and migrates them to Simplifier
SAP Clean Core Strategy — enables S/4HANA Clean Core by moving custom code from the SAP stack to the Simplifier sidecar platform
Automated Code Analysis — scans legacy codebases, identifies patterns, dependencies and produces detailed migration plans

How to use

Miri provides a complete Project Management & Agentic Orchestration under https://miri.simplifier.cloud

You can login with Single-Sign-On or Makers Club ID.

For the first time, you have to install an agent on your local environment. See full installation guide.

Watch Miri in Action

See how Miri analyzes a legacy SAP ABAP custom application, identifies all dependencies, and migrates it to a modern Simplifier Fiori application — reducing months of manual work to hours.

You have missed our webinar about Miri? Then also watch the recording in our media section!

Value Proposition

Dramatically reduces migration effort compared to manual rewrites — months become hours
Enables SAP Clean Core by moving custom extensions from the SAP stack to the Simplifier sidecar platform — no S/4HANA upgrade blockers
Multi-technology coverage — ABAP, Neptune SAP Edition, Neptune Open Edition, Lotus Domino, Vibe Coding apps — one agent handles all legacy sources
Production-ready results — every migration is tested, documented, and deployed as a real Simplifier application, not a prototype
Works with Anna — after migration, Anna delivers a modern SAP Fiori UI on top of your migrated application
Full traceability — Miri documents every migration decision and maps old artifacts to new ones for audit and validation

Example Prompts & Use Cases

SAP ABAP Custom App → Simplifier (Clean Core)

“We have a custom ABAP purchasing approval app with 47 reports and 12 RFC function modules. We need to move this off our ECC system before the S/4HANA migration. Analyze the ABAP codebase and migrate it to Simplifier.”

Miri scans the ABAP artifacts, maps reports to Simplifier data sources, converts RFC modules to REST connectors, and builds the business logic — ready for Anna to deliver the Fiori UI.

Neptune SAP Edition → Simplifier

“Our warehouse management app runs on Neptune SAP Edition. We want to move it to Simplifier to prepare for Clean Core. Migrate the complete application including all Neptune widgets and backend logic.”

Miri analyzes the Neptune DXP project, maps widgets to Simplifier UI components, converts the ABAP backend to Simplifier business objects, and keeps all existing SAP data connections intact.

Neptune Open Edition → Simplifier

“We built a field service management app with Neptune Open Edition connecting to our SAP system via OData. Migrate this to Simplifier so we can consolidate all apps on one platform.”

Miri migrates the Neptune OE frontend to SAPUI5/Fiori, reuses the OData connections via Simplifier connectors, and preserves all existing business logic.

Lotus Domino → Simplifier

“Our HR approval workflows still run on Lotus Domino and need to be modernized. Analyze the Notes databases and migrate the workflows and forms to Simplifier.”

Miri reads the Domino NSF structures, maps forms to Simplifier data models, converts LotusScript logic to business objects, and preserves all workflow rules.

Vibe Coding App → Production Simplifier

“Our team built a prototype expense tracker with Cursor. It works but needs to be production-ready on Simplifier. Harden the code, add proper connectors, and make it deployable.”

Miri analyzes the prototype code, identifies gaps (authentication, error handling, data persistence), refactors for the Simplifier runtime, and produces a tested, documented production app.

Full ABAP Portfolio Assessment

“We have 200+ custom ABAP objects across ECC. Before we plan the S/4HANA migration, analyze the entire portfolio: which objects are still used, what do they depend on, and what’s the migration effort to Simplifier?”

Miri scans the complete ABAP catalog, builds a dependency graph, identifies dead code, and delivers a prioritized migration roadmap with effort estimates for each object.

FAQs

What data does Miri use for migrations?

Miri analyzes legacy application code and artifacts, then migrates them to Simplifier. Source artifacts Miri handles include:

SAP ABAP — reports, function modules, includes, custom programs
Neptune SAP Edition — DXP widgets, project structure, backend logic
Neptune Open Edition — standalone apps and OData connectors
Lotus Domino / Notes — NSF structures, forms, LotusScript logic
Vibe Coding — prototype / AI-generated code (Cursor, Claude, Copilot, etc.)

The LLM that is used by this service is hosted on servers located in Germany and the model is exclusively accessed by Simplifier. We do not use customer data to train models.

Usage data collected for product improvement

To continuously enhance our product, we collect the following anonymized data with each usage:

Timestamp
Request duration
Number of input and output tokens
User input
LLM-generated output
Anonymized customer ID

This data is securely stored in infrastructure accessible exclusively by Simplifier and is deleted after two months.

Data is encrypted at rest and in transit.

The legacy source code you upload as a migration task is processed in your private workspace. Miri documents every migration decision and maps old artifacts to new ones so you can audit and validate the result.

Learn more in the Miri Documentation and on miri.simplifier.cloud.

Which source platforms does Miri support?

Miri natively supports the following legacy source platforms:

SAP ABAP — custom reports, function modules, includes, programs, modules
Neptune SAP Edition — DXP applications running inside SAP
Neptune Open Edition — standalone Neptune apps, including OData-connected ones
Lotus Domino / Notes — Notes databases (NSF), forms, LotusScript logic
Vibe Coding / Prototype Apps — AI-generated code from Cursor, Claude, Copilot, Windsurf, or any other agentic dev environment

Miri produces a production-grade Simplifier application — including tested business logic, documented mappings, and deployment-ready assets — in all of these cases.

Common scenarios:

SAP Clean Core — move custom ABAP extensions off the S/4HANA core
Consolidation — multiple Neptune / Domino apps → one Simplifier platform
Prototype → Production — harden AI-generated code for real-world use

Want to see it in action? See the example prompts and use cases or the Miri in Action video.

Does Miri work together with Anna?

Yes. Miri and Anna are designed to work together:

Miri — analyzes the legacy codebase, identifies dependencies, migrates the application to Simplifier, and produces tested + documented artifacts.
Anna — takes the migrated application and delivers a modern SAPUI5 / Fiori user interface on top of it.

Typical flow:

You give Miri the legacy app (ABAP, Neptune, Lotus Domino, or prototype code).
Miri migrates it to Simplifier — data model, business objects, connectors, workflows, tests.
Anna takes over and generates the Fiori UI in a single step.

Result: a production-ready Simplifier application — with Clean-Core alignment, modern UX, and full traceability of every migration decision.

If your goal is not migration but building a new app from scratch with AI, Anna is the right starting point.

Learn more: Miri Application Migration · try Miri

Where is my data stored and processed?

Miri has 2 major software components where your data are stored and processed:

Miri Web Interface – Orchestrating the Miri Agents and Subagents via Task Board, Cost Control, User, Roles, Rights and Cost Management
Miri Agent – process the Task via your own LLM , connect your Sytems via MCP within your own network

Miri Agent

Miri runs a local agent on your own environment (Windows, macOS, or Linux — via daemon or Docker). That agent scans and analyzes your legacy sources — ABAP, Neptune, Lotus Domino, or prototype code — within your own network.

The LLM is your choice. You configure which AI model Miri uses — the one that has been approved by your security and data-protection officer. This can be an on-premises model, a private cloud, or a SaaS endpoint you have already cleared. Miri does not lock you into a specific provider.

In practice this means:

Source code stays in your network — analysis, scanning and refactoring run on the local agent
You pick the applied LLM — your approved model of choice, not a vendor-predefined one
Compliance on your terms — the setup satisfies your security / data-protection requirements because the model endpoint is your decision

Installation of the local agent:

Miri Web Interface

The Miri platform (miri.simplifier.cloud) is hosted at AWS in Frankfurt (EU). Only non-AI data is processed there, in particular:

Task descriptions — the task descriptions of your migration tasks
Attachments — files you attach to a task
User data for login — the email address of the user used to log in to the platform
Token Costs per User / AI Agent
Audit Log Data (Which User do what within the Interface)