Migrating an HFSQL Classic database to SQL: a practical plan
Whether you are leaving WinDev, adding a web front end or consolidating databases, the same steps keep a migration under control. This guide walks through them.
Last reviewed: November 2, 2026
1. Take inventory
List the data folders in use and the tables each one contains. Note which tables carry memo fields (.MMO), which are protected by a password, and roughly how many rows the big ones hold. Keep the project analysis (.wdd) that goes with the data: it describes the tables, and Fic2All uses it to read column names, types and order.
2. Choose the target database
Pick the engine that fits what comes next, not what is fashionable. PostgreSQL and MySQL suit new web and back-office applications, SQL Server suits Microsoft-centric environments, and SQLite suits archives, local copies and embedded use.
3. Work on a copy
Copy your data folder and run the first migration on the copy. Fic2All only reads source files, but a copy lets you rehearse without any pressure and gives you a clean reference for comparing results.
4. Convert and read the report
Run the conversion and open the verification report. For each table you see rows read versus rows written, and any rejected row with its column and error message. Fix the cause of each rejection, rerun, and keep the report as evidence.
5. Verify beyond the counts
Row counts are the first check, not the last. Spot-check accented text, dates, numbers and empty values on real records, and run a few queries your application depends on. The verification guide lists the checks in detail.
6. Plan the cut-over
Decide when the old data stops changing, run the final migration on that frozen data, verify it, and only then point the new application at the new database. Keep the original HFSQL files until you are sure.
Ready to move your HFSQL data?
Pick a plan, install Fic2All and let the verification report do the checking.
See plans and pricing