EN FR
Sign in Get Fic2All

Convert HFSQL to SQL Server

Fic2All migrates your HFSQL Classic data to Microsoft SQL Server from your Windows machine, without touching your source files, and finishes with a table-by-table verification report.

Last reviewed: November 2, 2026

Why move HFSQL data to SQL Server

Many HFSQL applications live in Windows environments where SQL Server is already the company standard: its tooling, its backup and security model, and its reporting stack are familiar to the team. Moving the data there lets the application and the rest of the information system share one database platform.

Fic2All reads your .FIC and .MMO files through the HFSQL ODBC driver and writes the tables to your SQL Server database, with a verification report so the switch is something you can check, not just trust.

SQL Server is a good fit if…

  • your organisation already runs SQL Server and its tools.
  • you are rewriting the application with .NET or a Microsoft-centric stack.
  • you want your data available to the reporting tools your team already uses.

How the conversion works

  1. Choose your data folder. Fic2All lists the tables it finds, each with a clear status: Ready, Protected or Error.
  2. Unlock protected files. If a file is protected, Fic2All asks for its password. It is used for that file only and is never stored.
  3. Connect to SQL Server. Enter the connection details and test them before you start. You can save the connection as a profile for the next project.
  4. Convert. Each table is processed on its own, with progress per table. A problem on one table does not stop the others.
  5. Read the report. For every table, rows read versus rows written. Rejected rows are listed with the row, the column and the database error.

Before you start

  • Windows 10 or 11 (Fic2All is a desktop app that runs on your machine).
  • The HFSQL ODBC driver published by PC SOFT, installed once from their official site.
  • Your HFSQL Classic data (.FIC and .MMO files) and, next to them, the project analysis (.wdd) that describes the tables.
  • The server name or address, database name and credentials of your SQL Server instance.
  • The password of any protected file, if there is one.

The HFSQL ODBC driver, explained

Proof, not hope: the verification report

A migration is only finished when you can show nothing was lost. Fic2All ends every run with a report that compares, table by table, the rows read from your HFSQL files with the rows written to SQL Server. If rows were rejected, the gap is visible and each rejected row is listed, so nothing disappears silently.

How to verify an HFSQL migration

Questions

Can I convert to a SQL Server on my network?

Yes, as long as your PC can reach it. Enter the server details, test the connection from Fic2All, and save it as a profile if you will migrate more than once.

Does it change my source files?

No. Fic2All only reads your source files. Nothing is ever written to them.

Do I need WinDev or HFSQL installed?

You do not need WinDev. Fic2All reads your files through the HFSQL ODBC driver published by PC SOFT, which you install once from their official site. If the driver is missing, Fic2All explains it and points you to the download; the rest of the work is unaffected.

What if some rows cannot be written?

Rejected rows are counted and listed with the row, the column and the database's error message. The report shows the gap for that table, so nothing disappears silently.

Ready to move your HFSQL data?

Pick a plan, install Fic2All and let the verification report do the checking.

See plans and pricing

Keep reading