Field CRM
Application deployed on around 110 sales workstations.
Estate audit, migration in batches, data checked line by line. WinDev, WebDev, WinDev Mobile and HFSQL to standard technologies.
Many WinDev business applications have been running for 15 or 20 years. They work, but three risks are growing:
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.
| Source | Targets |
|---|---|
| WinDev | C# / .NET 8–10 (WPF, WinForms), ASP.NET, web application |
| WebDev | ASP.NET, Next.js / React, API Python (FastAPI) |
| WinDev Mobile | Native Android (Kotlin, Jetpack Compose) |
| HFSQL | SQL Server, PostgreSQL, MySQL / MariaDB |
Automated code analysis (lines, windows, reports, queries, dependencies, dead code). Deliverable: report and costing per module.
Choice of target, batch split and priorities. Each technical choice is recorded in a decision log (ADR) handed to the client.
HFSQL schema converted, replayable migration scripts, systematic source = target checks (counts, checksums).
Module by module, the old and the new application can coexist. No "big bang".
Business test scenarios validated with key users, automated tests on the new code base.
Supported deployment, documentation, handover to the in-house team or maintenance.
Application deployed on around 110 sales workstations.
108 tables, 1,124 fields, 6.2 million rows migrated with source = target checks.
Invoice management application rewritten.
Native rewrite.
A 28,000-line application migrated in 14 days.
Four steps, in your browser, without sending any source code or data: a range in man-days, a complexity level and the main risks.
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.
No. The migration is done in batches; the old application stays in service until each module is switched over.
Temporarily, yes, but the recommended target is a standard database (SQL Server, PostgreSQL or MySQL/MariaDB) to end the dependency.
Tools automate the analysis and the data migration, but the application code is reviewed and restructured to obtain maintainable code.
Yes, most of the work is done remotely. On-site days are planned for scoping, acceptance and go-live.
Your team, with the documentation and a handover, or Altekk under a maintenance contract.
The audit is priced as a fixed fee according to the size of the estate. Book a slot to discuss it.