The problem
An application on a low-code platform consists of models that only that platform understands. If you stop using the platform, you can often take the generated code with you, but it was produced by a machine, comes without the development environment around it, and is hard to keep working with. Even moving to a new generation of the same platform often turns out to be a rebuild in practice.
Why it keeps coming back
- The speed of low-code works at the start; the dependency only becomes visible later.
- There is no documented exit path, so every departure starts from zero.
- Business logic is interwoven with platform-specific components.
Our approach
- The generated code as an inventory, not an end point. It shows what the application does: data, screens, rules. We build on that, but we do not keep working in it.
- Rebuilding on a fixed stack. Every application becomes clear, open-source software with the same structure, which any developer can maintain and which you own.
- Step by step. Application by application, with the integrations (for example with SAP) intact, so the organisation can keep working as usual.
- AI-assisted, within fixed rules. AI speeds up the rebuild considerably. Our house rules make sure the result stays maintainable.
What to watch out for
- For every new application, record how you will one day move away from it: an exit plan belongs at the start, not at the renewal.
- Choose an architecture that does not depend on a single vendor.
- Rebuilding is also a chance to clean up: not every feature of the old application is still needed.
Would you like advice on phasing out low-code? Request a free advice conversation.
Updated on