Migrating your WinDev application: method, timeline and budget
Your WinDev application has been running for years. It works, but PC SOFT licences weigh a little more every year, maintenance is getting harder and hiring a WLanguage developer is increasingly rare. Migrating to C# (.NET) or to the web (React, Vue.js) does not mean rewriting your application from scratch: we transfer your business logic to the target that makes sense for you.
Your WinDev application costs you more than it brings in
Rising PC SOFT licences, difficult maintenance, impossible hiring
A WinDev application that has been in production for ten years often means a set of management rules that nobody fully masters any more, printable reports tuned to the last detail, and a PC SOFT licence that comes back every year. The code works. But the pool of WLanguage developers is shrinking, and every change takes an effort out of proportion to what it delivers.
Stay on WinDev or migrate: how to decide?
The question is not “should we migrate” but “what costs more: staying or migrating”. Three signals come up every time with our clients: the recurring licence cost, the difficulty of hiring or replacing a WLanguage developer, and the need to open the application to the web or to an existing Microsoft information system. If none of these three signals applies to you, migration is not urgent. If even one comes up every quarter in management meetings, it is time to scope an audit.
Our 4-step WinDev migration method
1. Technical and functional audit of your application
Full mapping of the existing WinDev windows, reports, tables and processes. This audit identifies what migrates as is, what must be adapted, and what can be dropped without risk.
2. Choosing the target: C#/.NET, React or another stack
The choice depends on your context, not on a technological preference. Leaving PC SOFT points towards C#. Opening access from a browser or a field tablet points towards React or Vue.js. We scope this choice with you before estimating anything.
3. AI-assisted migration with expert review
The functional specifications are generated by AI from the existing WinDev code, which speeds up the analysis without losing business detail. Every document sent is anonymized, and sensitive algorithms are reviewed and validated manually.
4. Acceptance testing, tests and knowledge transfer
Functional tests on real data, old and new versions running in parallel during validation, then a gradual go-live. Your teams are trained on the new stack before the final switchover.
WinDev to C# migration: what you gain
Zero dependency on PC SOFT
You leave the vendor licence and the proprietary WLanguage for good. Maintenance relies on a standard, open .NET stack that any C# team on the market can maintain.
3 to 5 times cheaper than a complete rewrite
Because the business logic is systematically analyzed and carried over, not redeveloped from a blank sheet. It is a technical rewrite, not a functional redesign.
Web or desktop application, as you need
Once on .NET, you choose: Blazor for a web interface, or a modern desktop application. Moving to the web remains possible later without another complete rewrite.
WinDev to React / Vue.js migration: the web alternative
When to choose React rather than C#?
When the priority is browser or tablet access, not leaving the PC SOFT ecosystem. WebDev carries your existing business logic over to the web without starting from scratch. React goes further: a modern interface, decoupled from a WinDev back end that can stay in place during the transition.
Integration with your existing information system
A React or Vue.js interface connects to your existing tools through APIs: ERP, customer portal, third-party systems. You no longer have to deploy PC by PC with every update, and your field technicians enter data directly from their tablet.
Why EloNeva rather than another provider?
20 years of PC SOFT and WLanguage expertise
We are not discovering WinDev on your project. The initial audit goes fast because we already know the classic pitfalls: global dependencies, duplicated processes, undocumented printable reports.
A method based on specifications, not improvisation
Every migration starts from a complete map of the existing application and from specifications validated before the first line of code is rewritten. No surprises about the functional scope along the way.
End-to-end support for SMEs
From the initial audit to knowledge transfer to your teams, including budget scoping. A single point of contact throughout.
They migrated their WinDev application
EloNeva: yes, we have already migrated
We migrated our own WinDev ERP to C# for our internal needs. So we have first-hand experience of migration, with the pitfalls to avoid and the best practices to follow.
AIRBEEZ: WebDev -> React migration for their back end.
AirBeez, an aviation services company, migrated its WebDev application to React to modernize the interface and give its customers web access. The business logic was carried over without any loss of functionality.
In the jungle of AI development tools, luckily I came across Laurent.
I decided to leave the PC SOFT and WinDev ecosystem and started migrating my tools to applications developed with AI. I ran into the whims of Lovable, which tends to go beyond the scope you set. Laurent helped me set the rules of the game and keep the development under control.
The essentials: know your business rules inside out, write precise specifications, set the security rules — and never trust the AI without testing, reviewing, testing, reviewing. And the icing on the cake: make them compete. I systematically have Lovable’s code checked by Claude.
Laurent helped me put this approach in place and is always a good source of advice for the human eye that finalizes the work.
Daniel Favier, president of AIRBEEZ
Request your free audit
A technical and functional audit of your WinDev application, with no commitment, to scope the target and the budget before any decision.
Our services
What is included
- Technical and functional audit of the existing WinDev application (windows, processes, WLanguage)
- AI-assisted generation of the functional specifications, systematically reviewed by an expert
- Migration of the business logic to the chosen target: C# (.NET), React or Vue.js
- HFSQL migration to PostgreSQL, SQL Server or HFSQL client/server depending on the context
- A/B testing: old and new versions run in parallel during validation
- Gradual, secure go-live
What is not included
- Server hosting (we advise, you choose)
- Redesign of business processes (outside the migration scope)
- User training (separate quote if needed)
Frequently asked questions
It depends directly on the number of components (windows, reports, processes) and on the chosen target. A migration to React or Vue.js, which carries over the existing logic, costs significantly less than a migration to C#, which is a complete rewrite. The calculator gives a first estimate; the firm quote comes after the technical audit.
From a few weeks for a targeted React port to several months for a complete C# rewrite over a large scope. The timeline depends on the number of components and the volume of data to migrate.
Yes, and it is actually the approach we recommend for critical applications. We migrate in batches, module by module, with the old and new versions running in parallel during validation. This avoids a big bang and limits the business risk.
It is migrated to the target suited to your context: HFSQL client/server if you stay close to the PC SOFT ecosystem, PostgreSQL or SQL Server if you leave WinDev completely. Data migration and migration scripts are included in the fixed price, never treated as a side task.
Interested in this service?
Contact us to discuss your project and find out how we can help.
Contact us