Guide · Legacy software · Quebec SMBs
Taking over abandoned WinDev, Access or in-house software: where to start
In short
Before rewriting anything, you secure what’s there: recover the source code and the access, make a complete, verified backup, then document what the software really does. Only then do you choose: keep it as is, stabilize it and modernize it piece by piece, or replace it in stages. A complete rewrite all at once is rarely the right first decision.
The 7 checks before touching anything
- The source code, not just the installed program. Without it, you can only work around problems, never fix them.
- The development tools and licences. WinDev, for example, is a commercial environment from PC SOFT: changing the code requires a licence from the vendor.
- The access: server, database, hosting, domain name, administrator accounts. They’re often in the former developer’s name.
- A backup that has been successfully restored. A backup that has never been tested isn’t a backup.
- The dependencies: Windows version, printer or barcode scanner drivers, libraries, database (HFSQL for WinDev, .accdb file for Access).
- Who uses what, and the tasks that can only be done in this software.
- What breaks most often, and what the team already does to work around it.
The developer left and you don’t have the source code: what now?
It’s the most common situation, and it’s almost never hopeless. Start by looking for the code: the former supplier’s contract or invoice, the former developer’s computer, the server, backups, a USB key forgotten in a drawer. For a WinDev project, you need the project files, not just the installed program (.exe).
If the code can’t be found, the data can almost always be recovered: an HFSQL database or an Access file can be read and exported without the program. The application can then be rebuilt around the existing data, in stages, by observing what the old software does screen by screen.
To keep it from happening again: require every supplier, in writing, to hand over the source code, the documentation and all access, in your company’s name.
How do you find a developer to take over software?
Look for someone who offers to read the software first, not rebuild it. Three questions quickly separate the candidates: have they already taken over software written by someone else in that language? Do they start with an inventory and a backup? What do they hand over at the end — code, documentation, access?
Be wary of “it all needs to be redone” before they’ve even seen the code. Sometimes it’s true, but that gets shown after the inventory, not before.
What’s the future of WinDev, Access and old Windows software?
WinDev is still sold by PC SOFT, and Access is still offered by Microsoft. The real question isn’t the tool’s future, but your software’s: who can fix it when it crashes, and what computer it runs on. Since October 14, 2025, Windows 10, Access 2016 and Access 2019 no longer receive security updates (Microsoft). In-house software that depends on any of them becomes a risk, even if it still works.
Maintain, modernize or replace?
| Path | When to choose it | Risk | Price range |
|---|---|---|---|
| Keep it as is | The software does its job well, few changes planned | Low in the short term, the dependency remains | Support agreement |
| Stabilize, then modernize piece by piece | The software is critical but fragile; you want to keep existing habits | Low: you change one part at a time | Sprint from $4,500, then phases of about $6,000 |
| Replace in stages | The software is holding back growth or can no longer be changed | Medium: the data migration must be checked | Most systems: $12,000 to $30,000 |
What software should replace WinDev or Access?
There’s no single best language: choose a widely used technology that other developers will be able to take over after you. For an SMB, that’s often a web application (PHP/Laravel, .NET or Python) with a standard SQL database, accessible from any computer or phone. If your needs are standard, off-the-shelf software may be enough.
The data from the old system (HFSQL, Access) is migrated to the new database; you check that the totals match before switching over. For Access, the method is detailed in the guide to replacing an Access database.
How much does it cost to take over software?
The 20-minute assessment is free. The takeover starts with a fixed-scope, fixed-price sprint, from $4,500: inventory, verified backup, fixes for blocking bugs and documentation. The rest is done in phases of about $6,000, at the pace of your operations. Pricing details are in the custom software pricing guide, and the service is described on the legacy software takeover page.