Migrate a WinDev application without stopping the business

Estate audit, migration in batches, data checked line by line. WinDev, WebDev, WinDev Mobile and HFSQL to standard technologies.

8
PC SOFT estates audited and costed in 2026
~8.6 M
lines of WLanguage analysed
6 000+
windows inventoried
20 years
of WinDev / HFSQL practice (since 2005)

Why migrate now

Many WinDev business applications have been running for 15 or 20 years. They work, but three risks are growing:

  • Dependence on a single vendor: language, HFSQL database and tools all come from the same supplier. In 2026 PC SOFT announced a planned annual fee per deployed workstation, whose amount and terms were not confirmed at the time of writing; the matter was the subject of a written question to the French government (no. 16261, Official Journal of 23/06/2026).
  • Recruitment: WinDev developers are becoming scarce, whereas C#, SQL Server or PostgreSQL are common skills.
  • Concentrated knowledge: often one or two people know the application. A documented migration puts that knowledge back into the project.

Migrating is not always the right answer: the audit also serves to decide not to migrate, or to migrate only part of the application.

Public information at the date of publication (6 November 2026). Check the current status with PC SOFT.

Migration targets

SourceTargets
WinDevC# / .NET 8–10 (WPF, WinForms), ASP.NET, web application
WebDevASP.NET, Next.js / React, API Python (FastAPI)
WinDev MobileNative Android (Kotlin, Jetpack Compose)
HFSQLSQL Server, PostgreSQL, MySQL / MariaDB

The method in 6 steps

  1. Estate audit

    Automated code analysis (lines, windows, reports, queries, dependencies, dead code). Deliverable: report and costing per module.

  2. Scoping and decisions

    Choice of target, batch split and priorities. Each technical choice is recorded in a decision log (ADR) handed to the client.

  3. Data migration

    HFSQL schema converted, replayable migration scripts, systematic source = target checks (counts, checksums).

  4. Rewrite in batches

    Module by module, the old and the new application can coexist. No "big bang".

  5. Acceptance

    Business test scenarios validated with key users, automated tests on the new code base.

  6. Go-live and handover

    Supported deployment, documentation, handover to the in-house team or maintenance.

Completed projects

Field CRM

WinDev → C# / WPF .NET 10

Application deployed on around 110 sales workstations.

Synchronisation hub

WinDev + HFSQL → .NET 8 + SQL Server

108 tables, 1,124 fields, 6.2 million rows migrated with source = target checks.

Invoicing

WinDev → .NET 8

Invoice management application rewritten.

Mobile application

WinDev Mobile → Android Kotlin

Native rewrite.

CRM of a medical software vendor

WinDev → ASP.NET

Lead time

28,000 lines

A 28,000-line application migrated in 14 days.

Estimate your migration

Four steps, in your browser, without sending any source code or data: a range in man-days, a complexity level and the main risks.

  1. The application
  2. The data
  3. Context
  4. Result

Step 1 — The application

Source product (required)

Several choices possible.

Approximate version (required)

Visible in the development environment (project statistics). Leave empty if unknown.

A range is accepted, for example "80-120".

Open the simulator on its own page →

Frequently asked questions

How long does a migration take?

It depends mostly on the volume of code, the number of windows and the quality of the data. The simulator above gives an order of magnitude; the audit gives a firm costing per batch.

Does the application have to stop during the migration?

No. The migration is done in batches; the old application stays in service until each module is switched over.

Can we keep HFSQL?

Temporarily, yes, but the recommended target is a standard database (SQL Server, PostgreSQL or MySQL/MariaDB) to end the dependency.

Do you use an automatic converter?

Tools automate the analysis and the data migration, but the application code is reviewed and restructured to obtain maintainable code.

Do you work remotely?

Yes, most of the work is done remotely. On-site days are planned for scoping, acceptance and go-live.

Who maintains the application afterwards?

Your team, with the documentation and a handover, or Altekk under a maintenance contract.

What does an audit cost?

The audit is priced as a fixed fee according to the size of the estate. Book a slot to discuss it.