Migrating from WinDev or WebDev: your real options in 2026.
Thousands of business systems run on WinDev. In 2026, keeping them there means a subscription that expires with the invoice and runtime fees announced for apps already in production. This guide walks through the three ways out — and what each one costs you in time, risk and money.
Why developers are looking for the exit now
- The IDE became subscription-only. Stop renewing and the tools stop working.
- Runtime fees were announced for applications running at your clients — apps that never had a meter before.
- No public price list. Costs are negotiated by quote, and they have moved in one direction.
- The technology ceiling. A language one company maintains, a talent pool that shrinks every year, an ecosystem the rest of the industry doesn't share.
The three ways out
1 · Rewrite by hand
Hire a web team, re-specify every screen and rule from a codebase nobody fully documented. The classic 2–3 year project — the one that often dies at 60%.
2 · Point an AI coder at it
Fast on the first screens, then it drifts: it guesses business rules, loses the dependency order, and you find the breakage in production.
3 · Convert with a method
Read the whole codebase first, extract every rule with an ID, convert in dependency order, generate tests from the rules, and ship on an open stack. This is what WXCode does.
What a methodical conversion looks like
- Import everything project ZIP, documentation PDFs, the database schema, stored procedures.
- Meet your codebase again a knowledge base of windows, pages, procedures, queries, classes, reports and tables, with the dependency graph and every business rule extracted and explained.
- Convert milestone by milestone into Next.js, Laravel, Django, Rails and more (16 stacks), in topological order, while your legacy keeps running on the same data.
- Prove nothing broke thousands of tests generated from your rules, verification at every milestone, the app running from the first one.
- Run it on the web build, test, deliver, publish, observe, care: the whole lifecycle, in one place.
What you keep, what you leave
You keep your data (the schema is converted 1:1), your business rules (extracted with IDs, traceable to tests), your screens' logic, and — for the first time — a documented system.
You leave the subscription, the runtime meter, the proprietary language, and the single-vendor talent market. Your converted app is a normal git repository in an open stack: no vendor runtime, no per-session fees, nothing that expires.
Questions developers ask first
A real 3-year, 7-person rewrite was done by one developer in about 6 months with WXCode — milestone by milestone, not big-bang.
The database schema is converted 1:1, so the new app reads the same data. Your legacy keeps running during the migration.
All of them are first-class elements in the knowledge base and are converted — reports included, with the rules that govern them.
No. The platform carries build, test, deploy, domain and monitoring. You choose the stack; WXCode does the parts you never had to learn on desktop.
Download your project at any time. It runs without WXCode. You stay for the knowledge base and the cockpits, not because you're trapped.
See what you free up.
Put your seats and sessions into the exit calculator, then import your project and meet your codebase again.