Migration snapshot
ActivePlatform
a Mendix
Mendix is Siemens-owned (acquired 2018) with active product development, particularly in PLM/ERP/SAP Siemens ecosystem integrations. Forrester composite 3-yr TCO analysis cites approximately $696,900 ($525K licensing component) for a representative enterprise deployment. Free-tier deployed apps automatically shut down after a few hours of inactivity (per Vertice and TrustRadius, 2026).
Typical timeline
10–14 weeks
Typical cost
$13K–$25K (agency, fixed)
Why teams leave a Mendix
Mendix is a well-funded, Siemens-backed platform — the reasons to migrate are cost trajectory, per-user pricing as a growth tax, and the full-rebuild reality that applies whether you stay or go.
Per-user cost escalation
Standard/Premium tiers are priced per named user; Forrester's composite enterprise analysis cites a 3-yr TCO of approximately $696,900. Costs compound with SAP BTP connector, private cloud, and multi-region add-ons.
Full proprietary lock-in on the app layer
Domain models, microflows, nanoflows, and pages are Mendix-specific constructs stored in .mpr model files. Migrating off means a full rebuild from scratch — there is no runnable source export at any tier.
Siemens ecosystem gravity
Mendix pushes SAP/Teamcenter/Siemens ecosystem integrations. If your roadmap diverges from that ecosystem, you pay for integration depth you don't use while your actual integration needs go unsupported.
Runtime requires Mendix license even on-prem
'On-premises' Mendix means your infrastructure but still Mendix's runtime and an annual license. There is no self-hosted open-source path — the runtime itself is proprietary.
Free tier forces auto-shutdown
Free-tier Mendix apps shut down automatically after a few hours without user activity, making prototyping unreliable without a paid plan and accelerating the cost curve for any app that needs to be always-on.
What can you actually take with you?
Mendix has no runnable source export at any tier. Data is accessible via direct DB connection (self-hosted) or Mendix support engagement (Mendix Cloud). Microflows and nanoflows are human-readable in Studio Pro but require complete re-implementation.
| Asset | Can you export it? | How | Notes |
|---|---|---|---|
| Data | Partial | App database accessible via direct DB connection in on-premises deployments; Mendix Cloud customers need to request database exports via Mendix support. Standard SQL dump if self-hosted. | Initiate Mendix Cloud data-export request 4+ weeks before planned cutover. Document this obligation in the migration contract. |
| Code | No | No runnable off-platform source export exists at any tier. | Mendix Studio Pro produces .mpk packages that run only on the Mendix runtime. Domain models, microflows, nanoflows, and pages are proprietary Mendix model files (.mpr). |
| Design/UI | No | Pages are built in Mendix Studio Pro and stored in the .mpr model file; not exportable as HTML/CSS/React. | Screen inventory via App → Export Documentation (PDF) in Studio Pro is the practical extraction method. |
| Logic/Workflows | No | Microflows and nanoflows are visual logic stored in the Mendix model file; conceptually readable in Studio Pro but not translatable by any tooling. | Must be reverse-engineered by reading the model in Studio Pro. Prioritise business-owner walkthroughs over attempting to parse model files directly. |
| Users & Auth | Partial | User entities are accessible via DB if self-hosted. Mendix SSO/identity federation via OIDC/SAML means user accounts may already be in an external IdP the client controls. | Password hashes not documented as exportable. If using Mendix built-in auth, plan a forced password reset. If using external OIDC/SAML IdP, user migration is managed at the IdP level. |
| Scheduled Events | Partial | Scheduled Event definitions are visible in Studio Pro and documentable via Export Documentation. | The schedule logic itself runs on the Mendix runtime; must be re-implemented as Supabase pg_cron or Vercel Cron Jobs. |
Swipe the table sideways to see the full breakdown.
Where each piece moves in code
Mendix apps migrate to a Next.js (App Router) + Supabase (PostgreSQL) stack, with shadcn/ui replacing Mendix Widgets, Supabase Auth (SAML) or Clerk handling SSO, and Supabase pg_cron replacing Scheduled Events.
a Mendix
Mendix Domain Model (entities + associations)
In code
Supabase PostgreSQL schema (tables + foreign keys)
Each entity becomes a table; associations become foreign keys. Self-hosted DB dump is the cleanest migration path.
a Mendix
Mendix Pages (forms, lists, detail views)
In code
Next.js page/layout components with React Server Components
Data grids and master-detail forms map cleanly to Next.js server-side data fetching.
a Mendix
Microflows (server-side logic)
In code
Next.js Server Actions or API Route Handlers in TypeScript
One microflow = one Server Action function. Prioritise microflow walkthroughs with domain experts in weeks 1–2.
a Mendix
Nanoflows (client-side logic)
In code
React hooks or client components with 'use client'
Nanoflows that call microflows become client components that call Server Actions via fetch.
a Mendix
Mendix Widgets (UI components)
In code
shadcn/ui + Radix UI component library
Mendix data grids have built-in sort/filter/export; define the UI parity list in week 1 and prioritise it in the frontend sprint.
a Mendix
Mendix SSO / OIDC / SAML
In code
Supabase Auth with SAML provider or Clerk for enterprise SSO
Migrate SSO config to the new provider first; run parallel login paths during UAT to avoid user disruption.
a Mendix
Mendix SAP BTP connector
In code
Next.js API Route Handler calling SAP REST APIs directly
Catalogue every OData/BAPI/RFC call in the Mendix model before starting the Next.js API layer — this is typically the biggest scope driver.
a Mendix
Mendix Scheduled Events
In code
Supabase pg_cron or Vercel Cron Jobs
Document business purpose for each Scheduled Event; map each to a cron expression before cutover.
The migration roadmap
A standard Mendix migration runs 10–14 weeks. Extraction and microflow documentation happen first and block all subsequent phases — do not start building Next.js until you have the full screen and logic inventory.
Extraction & Audit
Weeks 1–2- Export app documentation from Studio Pro (App → Export Documentation) to get screen and microflow inventory as PDF
- Connect to the Mendix database directly (self-hosted) or open a data-export request with Mendix support (Mendix Cloud)
- List every external system integration — SAP OData services, REST APIs, JDBC connections
- Audit named-user licences vs actual active users to surface immediate savings potential
- Check Mendix contract for early-termination clauses and next renewal date
Watch out: Mendix Cloud data access requires support engagement — initiate the export request 4+ weeks before cutover. Missing this step is the most common migration blocker.
Foundation & Stack Setup
Weeks 2–3- Set up Next.js App Router project with TypeScript, Tailwind CSS, and shadcn/ui
- Migrate Mendix domain model to Supabase PostgreSQL with Row-Level Security
- Configure Supabase Auth with SAML or Clerk for enterprise SSO
- Establish CI/CD pipeline (GitHub Actions → Vercel)
Data Migration & API Layer
Weeks 3–7- Migrate production data from Mendix database to Supabase PostgreSQL
- Build Next.js API Route Handlers for SAP OData/BAPI calls and other external integrations
- Implement Scheduled Event equivalents as Supabase pg_cron or Vercel Cron Jobs
- Translate microflow business logic into TypeScript Server Actions (walk through each microflow with domain experts)
Watch out: SAP integration re-implementation is typically the single largest scope driver. Get the full list of SAP function modules in use from the Mendix app before starting this phase.
Feature Parity & Frontend Build
Weeks 7–11- Build Next.js page components from Studio Pro screen inventory
- Implement data grids with sort/filter/export (Mendix built-in features that must be explicitly rebuilt)
- Replicate nanoflow client logic as React hooks and client components
- Build and test Row-Level Security policies mirroring Mendix role-based access
UAT & Cutover
Weeks 11–14- Run Mendix and Next.js apps in parallel during UAT
- Execute SSO migration or forced password reset for built-in auth users
- Verify data integrity between Mendix export and Supabase import
- Confirm contract cancellation timing and align cutover before the next billing cycle
Three ways to migrate — honestly
Every path has a real trade-off. Here is what each costs, how long it takes, and where it bites.
DIY (with AI tools)
$500–2,000 (tools + infra)
4–8 months part-time
Fits
In-house teams with Next.js/TypeScript experience and access to Mendix Studio Pro for documentation. Best for apps with fewer than 20 microflows and no SAP integrations.
Risks
Mendix microflow complexity and SAP OData re-plumbing are not beginner tasks. Without prior enterprise integration experience, the SAP API layer alone can stall the project. Expect more than 500 hours of senior engineering time on a medium-complexity Mendix estate.
Freelancer
$5K–12K
2–4 months
Fits
Smaller Mendix apps (under 15 screens, no SAP, simple microflows) with a client who can manage the project and handle Mendix support engagement for data export.
Risks
Mendix expertise is rare in the freelance market. Vet for direct Mendix migration experience rather than general no-code-to-code work. Misreading microflow complexity mid-project causes fixed-scope overruns.
Agency (RapidDev)
Done-for-you$13K–$25K fixed
6–10 weeks
Fits
Mendix apps with a defined screen inventory, documented integrations, and a clear contract renewal date that creates a hard cutover deadline. Fixed-price scope gives the client predictability on a migration where freelancer estimates routinely miss.
Risks
Fixed-price scope requires the Studio Pro documentation export and full integration list before contract sign. Book a free scoping call with RapidDev to confirm scope before committing.
The real risks — and how to defuse them
Microflow complexity underestimate
Mitigation: Mendix microflows can encode years of business logic with no external documentation. Schedule microflow walkthroughs with domain experts in weeks 1–2; treat each microflow as a user story, not a code translation task.
SAP integration rework
Mitigation: OData/BAPI calls via the Mendix SAP Connector need equivalent API Route Handlers in Next.js. Get the full list of SAP function modules in use from the Mendix app before starting — this is the most common source of scope growth.
User identity disruption
Mitigation: If Mendix SSO is the login method, users may need re-enrolment in the new IdP. Migrate SSO config to the new provider first; run parallel login paths during UAT to avoid a hard cutover for authentication.
Mendix Cloud data access delay
Mitigation: On Mendix Cloud, database access requires Mendix support engagement. Initiate the data-export request 4+ weeks before planned cutover and document this obligation in the migration contract.
Per-user license overage during transition
Mitigation: Multi-year Mendix contracts may have early-termination fees. Check contract terms before setting the migration date; align cutover with the renewal window to avoid paying overlapping licenses.
UX regression on data grids
Mitigation: Mendix data grids have built-in sort/filter/export that must be explicitly rebuilt in shadcn/ui. Define the full UI parity list in week 1 and treat each data grid feature as a separate acceptance criterion.
Should you actually migrate?
Migrating is a real project. Sometimes staying is the right call — here is the honest split.
Stay if
- Your product roadmap is deeply tied to Siemens PLM/Teamcenter/MindSphere and Mendix's native connectors save 2–3 months of integration work per major release.
- Your team has 3+ certified Mendix developers and the app is in a stable maintenance phase — the rebuild cost outweighs the lock-in cost for the next 12–18 months.
- Your regulated use case (aerospace, automotive, industrial) benefits from Mendix's domain-specific templates and compliance certifications that would take significant effort to replicate.
- Your named-user count is stable and the per-user pricing model is not creating cost pressure relative to the business value delivered.
Migrate if
- Your Mendix bill (licensing plus Siemens ecosystem add-ons) exceeds $100K/yr and the app complexity does not justify that cost.
- Your team is expanding and the per-user pricing model is becoming a growth tax — every new collaborator adds a license cost that custom code does not impose.
- Your organisation is moving to Azure/AWS-native architecture and Mendix Cloud is creating data-residency or cloud-governance conflicts.
- You need to hire mainstream TypeScript/React developers and the Mendix skill requirement is narrowing your candidate pool.
Our honest verdict
Mendix is a rational choice inside the Siemens/SAP ecosystem with a dedicated Mendix team. Outside that context, the per-user cost trajectory, $696K+ 3-yr TCO, and rebuild-to-exit reality make custom code the better long-term investment.
Do this today: pre-migration checklist
Whatever path you choose, protect yourself first. Work through this before you touch a line of code.
Export app documentation from Studio Pro (App → Export Documentation)
This PDF gives you the screen and microflow inventory — your rebuild specification. Without it, scope cannot be accurately defined.
List every external system integration (SAP OData services, REST APIs, JDBC connections)
SAP integrations are typically the largest scope driver and must be inventoried before any API-layer work begins.
Connect to the Mendix database directly (self-hosted) or open a data-export request with Mendix support (Mendix Cloud)
Mendix Cloud data export requires support engagement with 4+ weeks lead time — start this process immediately.
Audit named-user licences vs actual active users
This surfaces immediate cost savings and establishes the business case for migration before a single line of code is written.
Check your Mendix contract for early-termination clauses and next renewal date
Misaligned cutover timing can result in paying an additional annual Mendix term while the new system is live.
Document all Scheduled Events and their business purpose
Each Scheduled Event becomes a cron job; missing one creates silent production failures after cutover.
Plan forced password reset communication if using Mendix built-in auth rather than external IdP
Password hashes are not documented as exportable; users must reset on cutover day. Two weeks' advance notice is the minimum.
Frequently asked questions
Can I export my Mendix app code?
No. Mendix Studio Pro produces .mpk packages that run only on the Mendix runtime. Domain models, microflows, nanoflows, and pages are stored as proprietary .mpr model files with no runnable off-platform source export at any tier. Migrating off Mendix always requires a full rebuild.
Can I export my Mendix database?
Partially. On self-hosted Mendix deployments, you have direct DB access and can export a standard SQL dump. On Mendix Cloud, database export requires a formal request through Mendix support — initiate this at least 4 weeks before your planned cutover date and document the request in your migration contract.
How long does migrating from Mendix take?
A typical Mendix migration runs 10–14 weeks for apps up to 40 screens with documented integrations. SAP OData/BAPI integrations are the primary timeline driver — each major integration adds 1–2 weeks to the API-layer phase. Begin with a thorough microflow walkthrough in weeks 1–2 before writing any Next.js code.
What happens to my users and passwords after migration?
If you use Mendix's built-in auth, user records are accessible via the database but password hashes are not documented as exportable — all users will need a forced password reset on cutover day. If you use external OIDC/SAML SSO, the user migration is managed at the IdP level and is typically non-disruptive.
Is Mendix shutting down?
No. Mendix is Siemens-owned with active development, particularly in PLM/ERP integrations. The migration case is driven by cost (per-user pricing, $696K+ 3-yr TCO) and lock-in, not a platform shutdown risk.
What replaces Mendix microflows in the new stack?
Each microflow becomes a Next.js Server Action or API Route Handler in TypeScript. Nanoflows (client-side logic) become React hooks or client components. The translation is conceptual, not automated — read each microflow in Studio Pro with a domain expert and write the equivalent TypeScript from the business requirement.
How much does it cost to migrate off Mendix?
A fixed-price agency migration runs $13K–$25K for a well-scoped Mendix app and takes 6–10 weeks. Freelancers typically quote $5K–$12K over 2–4 months for smaller apps. DIY with an in-house team requires senior engineers with enterprise integration experience and 4–8 months. Get a free scoping call to size your specific Mendix estate.
Does Mendix work without the Mendix license even on-premises?
No. 'On-premises' Mendix means your infrastructure but still the Mendix runtime and an active annual license. There is no open-source or self-hosted path that removes the vendor dependency. This is a core reason why migrating to custom code — which you fully own — is attractive once the per-user cost exceeds the rebuild investment.
We migrate no-code apps to production code
- Fixed price — $13K–$25K (agency, fixed)
- No data loss, no downtime
- You own 100% of the code
30-min call. Quote within 48 hours.
