Wamos Air

WinDev to C# migration in two weeks with Claude Code

13 executables, 1 Windows service and 3 SQL Server databases converted from WinDev to C# in two weeks by the in-house developer, equipped and supported by EloNeva.

2 weeks

of conversion by the in-house developer

100%

of the client’s requirements met

5 days

of EloNeva involvement in total

Context

Wamos Air ran a business application developed in WinDev, grouped into a single project that produced several deliverables thanks to WinDev configurations:

  • 13 executables and 1 Windows service;
  • 65 windows;
  • 12 printed reports;
  • 214 classes;
  • 6 procedure collections;
  • 3 Microsoft SQL Server databases.

A real-size project, with a strong constraint: a single developer to carry out the conversion, and a fixed deadline.

The client’s requirements

  1. Identical screens: users were not to be disrupted by the migration.
  2. Identical printouts: the 12 reports had to produce exactly the same documents.
  3. Project converted before November 23.

Our approach: make the developer autonomous, not replace him

Rather than taking on the conversion ourselves, we equipped and trained the Wamos Air developer, who knows his application better than anyone. Our role: give him the method, the tooling and a safety net.

1. Audit of the WinDev project - 1 day

  • Analysis of the project structure: configurations, executables, Windows service, windows, reports, classes and procedures.
  • Interview with the developer to understand the history, the sensitive areas and the implicit business rules.
  • Definition of the conversion order and the points to watch.

2. Training on the EloNeva-migration plugin - 2 days

  • Getting started with Claude Code and the EloNeva-migration plugin.
  • Conversion method: from WinDev code (WLanguage) to C#, window by window, report by report.
  • Verification best practices to guarantee identical screens and printouts.

3. Conversion by the Wamos Air developer - 2 weeks

Equipped with the plugin, the developer converted the whole project on his own: executables, Windows service, windows, printed reports, classes and procedures.

EloNeva’s support focused on:

  • A short daily meeting to remove blockers, validate choices and adjust the method.
  • Targeted help, without weighing down the developer’s schedule.

Results

  • Deadline met: project converted before the November 23 deadline.
  • 100% of the client’s requirements met: screens and printouts reproduced identically.
  • Skills kept in-house: the developer now masters the C# code of his application and the AI tooling to evolve it.
  • Limited support investment: 5 days of EloNeva involvement in total.

And after the migration?

Convinced by Claude Code, the Wamos Air developer has since connected his Jira to Claude Code to handle user requests. The tool adopted for the migration has become an everyday tool for maintaining and evolving the application.

What this project shows

A WinDev to C# migration no longer has to be a months-long project handed to an external team. With a structured method, specialized AI tooling and short support, the developer who knows the application can convert it himself, on a controlled schedule and with no loss of functionality. And the tooling put in place keeps delivering value long after the project ends.

See also: WinDev to C# (.NET) migration · WinDev to Web migration · All our migrations

Wamos Air has authorized EloNeva to communicate about this project.

Could your WinDev application follow the same path?

We always start with a one-day audit to assess the feasibility, scope and schedule of your migration.

Contact us