Skip to content
Discuss your project

WinDev migration · WLanguage

WinDev to C# and .NET migration, controlled and without disruption

Your WinDev and WLanguage applications carry your business. We migrate them to C# and .NET, or to the target of your choice, with acceptance tests written first, code produced by AI agents, automated checks and a review at every step. Your code can stay on your own infrastructure.

See the method

Why now

WinDev’s licensing model has changed

Since 2024, PC SOFT has been reshaping how its tools are sold and used. The facts, as published by the vendor and the press:

Nothing forces you to leave WinDev overnight: your current applications keep running. But for many companies, now is the right time to plan a path to an open platform whose running costs do not depend on a single vendor.

The target

Why C# and .NET

  • Developers you can hire

    C# is one of the most widely used languages in the world: nearly 28% of respondents to the 2025 Stack Overflow survey. Hiring staff or finding a contractor becomes easy.

  • No runtime fees

    .NET is free and open source (MIT licence): your applications deploy without per-seat or per-session licences.

  • A public roadmap

    A new version every year, long-term support releases maintained for three years: .NET 10, released in November 2025, is supported until November 2028.

  • Your choice of tools

    Visual Studio, VS Code or Rider; SQL Server, PostgreSQL or MariaDB; your own servers, Azure or another cloud. No more single-vendor lock-in.

  • A gradual migration

    WinDev can produce .NET assemblies, so both worlds can coexist during the migration, module by module.

Stack Overflow Developer Survey 2025 .NET open-source licence .NET support policy

The method

A migration driven by tests

There is no reliable automatic converter from WLanguage to C#: migrating means rewriting. Our agent factory makes that rewrite fast, and our tests make it safe.

  1. Assessment

    We inventory your projects (windows, reports, queries, HFSQL analyses, dependencies), identify the risks, split the work into batches and estimate the effort.

  2. Safety net

    Before touching the code, we capture current behaviour in automated acceptance tests: what the application does today becomes the reference.

  3. Batch migration

    Module by module, AI agents rewrite the code in idiomatic C#, without being able to change the tests. HFSQL data moves to the target database, backed by consistency checks.

  4. Continuous verification

    Build, acceptance tests and automated checks on every iteration. A batch only moves forward when everything is green.

  5. Review and go-live

    Each batch is reviewed by the architect, then rolled out gradually: old and new run side by side until the switch-over.

The outcome

What you get

  • Readable C# code that your team, or any .NET contractor, can maintain.
  • An automated test suite that protects every future change.
  • Your data migrated to the database of your choice, backed by consistency checks.
  • Documentation of the architecture and of the decisions taken, batch by batch.
  • The complete history: tickets, tests, reviews and logs for every step.
  • Knowledge transfer to your teams, if you wish.

Confidentiality

Your code never leaves your infrastructure

The source code of a business application is a sensitive asset. Our agents can work with open-weight AI models running locally, on your servers or on a dedicated workstation: not a single line of code goes through an external AI provider.

  • Open-weight models running locally, benchmarked on real tickets.
  • Online models (Claude, Codex) used only with your explicit consent.
  • Every step is recorded: ticket, tests, log, review.

Getting started

The migration assessment

An architect’s first look at your WinDev application: we analyse your sources and your context, then hand you a clear migration path.

  • Technical inventory and dependency map.
  • Risks, priorities and batch plan.
  • Choice of target: C# and .NET, web, API or desktop.
  • Effort estimate and indicative timeline.
Request an assessment

FAQ

Your questions about WinDev migration

Can we migrate without stopping our operations?

Yes. The migration happens in batches: migrated modules and WinDev modules coexist, and each switch-over happens once its batch is validated.

What happens to our HFSQL data?

It is moved to SQL Server, PostgreSQL or the database of your choice, with repeatable migration scripts and consistency checks before each switch-over.

Will the migrated code be maintainable?

That is the first goal: idiomatic C#, tested, reviewed and documented, that any .NET developer can pick up.

Is our code sent to an AI provider?

Not necessarily. We can work exclusively with models running locally, on your infrastructure. Whether to use online models is decided with you.

Is there an automatic WinDev to C# converter?

Not a reliable one: WLanguage, its reports and its queries have no direct equivalent. That is why we rewrite, with AI agents governed by acceptance tests and a human review.

Which targets besides C# and .NET?

Depending on your context: a web application (ASP.NET Core, Blazor), an API, a modern desktop application, or another language if your team requires it. The assessment helps you choose.

How long does a migration take?

From a few months to more than a year, depending on the size and complexity of the application. The assessment gives an estimate batch by batch.

Do we have to leave WinDev right away?

No. Your current applications keep running. The right time is when you can plan calmly; the assessment gives you what you need to decide.

Let’s talk about your WinDev application

Tell us about your application, its size and your deadlines: we will come back to you with precise questions and a first recommendation.

Discuss your project

WINDEV, WEBDEV, WINDEV Mobile, WLanguage and HFSQL are trademarks of PC SOFT. They are mentioned for descriptive purposes only; IntelliNova is neither affiliated with nor endorsed by PC SOFT.