WinDev to C# (.NET) migration: replace WinDev without losing your business logic

Your WinDev application works, but it locks you into the PC SOFT ecosystem: recurring licence, proprietary WLanguage, a small pool of developers. Migrating to C# (.NET) ends this dependency without throwing away years of business logic.

Leave the PC SOFT ecosystem without starting from scratch

A WinDev application often holds ten years of accumulated management rules, printable reports tuned to the last detail, and automations that nobody ever documented again. The code works, but it costs you a licence every year, and the pool of WLanguage developers keeps shrinking.

Replacing WinDev with a C# (.NET) application addresses this problem directly: you move to a standard, open Microsoft stack that any .NET team on the market can maintain.

What it changes in practice

  • No more dependency on the PC SOFT licence: recurring cost eliminated
  • A much larger pool of C# / .NET developers for maintenance
  • Access to the open-source ecosystem: ASP.NET Core, Blazor, Entity Framework
  • Native interoperability with REST APIs, Azure AD and cloud services
  • A rewrite, not a port: timeline and budget to match

Who it is for

This migration makes sense when the business logic needs to be redesigned anyway, when you expect hiring difficulties on WinDev, or when your application must integrate natively with an existing Microsoft information system.

Our method

  1. Audit of the WinDev code: full mapping of windows, reports, tables and processes
  2. AI-generated functional specifications: speeds up the analysis without losing business detail
  3. Rewrite in C# (.NET): modern architecture, deliveries in batches
  4. HFSQL to SQL Server, MariaDB or PostgreSQL migration: complete data migration
  5. A/B testing: old and new versions run in parallel during validation
  6. Gradual go-live

Is another target a better fit?

Our services

What is included

  • Audit of the existing WinDev code (windows, processes, WLanguage)
  • AI-assisted generation of the functional specifications
  • Rewrite of the business logic in C# (.NET)
  • HFSQL to SQL Server, MariaDB or PostgreSQL migration
  • A/B testing with the old and new versions running side by side
  • 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

Three reasons come up every time: recurring licence costs, difficulty hiring WLanguage developers, and the need for native interoperability with the Microsoft ecosystem (Azure AD, REST APIs, ASP.NET Core). If none of these applies to you, a WinDev to web migration is often faster and cheaper.

A rewrite. Unlike a migration to WebDev, which carries over the existing logic, moving to C# changes both the language and the architecture. The timeline and budget are higher, but you leave WLanguage for good.

It is migrated to SQL Server, MariaDB or PostgreSQL depending on your context (existing Microsoft environment, cost constraints, open-source preference). Data migration and the HFSQL migration scripts are included in the fixed price.

Yes, and we say so openly. Documents sent to the AI are anonymized and sensitive algorithms are handled manually.

Longer than a migration to WebDev, because it is a rewrite rather than a port: from a few weeks to several months depending on the functional scope and the volume of data.

Interested in this service?

Contact us to discuss your project and find out how we can help.

Contact us