Firebird
MySQL

Firebird to MySQL Converter

Tables and rows into MySQL, once or as a sync that carries only the changed rows, with saved jobs you can run again.

Version
5.4.0
Release Date
Oct. 25, 2026
Size
23.4 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Copy a Firebird database into MySQL without writing the target schema by hand. DBConvert connects to the Firebird server and to MySQL, and creates the tables before it moves a row.

  • Reads Firebird 3.x, 4.x and 5.x on a local or remote Firebird server. Every Firebird type is covered, and non-ASCII text arrives as written.
  • Writes to MySQL, or to a MySQL dump (.sql) file.
  • Converts the database once, or keeps MySQL in step with Firebird on a schedule while you cut over. The same download converts MySQL back into Firebird.
  • Runs on Windows as a desktop application.
How it runs

A Windows application that talks to both servers

You install it, point it at the Firebird server and at MySQL, and transfer directly between the servers. Connections, tables, and mappings remain available on separate screens as you refine the job.

A path, not a database name

Firebird has no list of databases to pick from. You enter the server's host and the database's path on that server - a .fdb file - or its alias, together with the connection character set. UTF8 is offered first.

Choose the dataset

Select the tables you need and apply per-table row filters when only part of the Firebird data belongs in MySQL. A WHERE filter on the Firebird source limits the rows.

Saved and repeatable

A job stores both connections, the table selection, and the options. Run it again from the interface, or start it by name from a batch file or Task Scheduler with --run-job.

Two modes, one download

Convert once, or keep MySQL in step with Firebird

One download covers both. You choose the mode when you set up the job.

One-time conversion

Tables and rows in one pass, into MySQL or into a MySQL dump (.sql) file.

Repeat synchronization

Keep the Firebird application running while MySQL is loaded and tested.

  • A sync straight after a conversion finds nothing to change.
  • After that, a sync carries exactly the rows that changed.
What needs attention

How DBConvert handles the Firebird → MySQL differences

Every mapping is a default you can review or override per column before the run.

In Firebird Why it does not carry over What DBConvert does
BLOB SUB_TYPE TEXT Text of unlimited length, stored in the column's character set. Becomes LONGTEXT. The BLOB subtype is read, and the text is read in the connection's character set, so Czech, Cyrillic or Japanese text arrives as written.

Procedural code stays behind

The migration covers tables and their data. Firebird PSQL stored procedures, triggers, and computed-by columns stay in the source and are rewritten by hand for MySQL.

Where this tool stops

There is no SSH tunnel on the Firebird side: the Firebird server's port, 3050 by default, has to be reachable from the machine running DBConvert. Run a test job on a copy before you switch the application over.

Supported versions and services

Firebird

  • Firebird 3.x, 4.x, 5.x

MySQL

  • MySQL 5.x, 8.x; MariaDB; Percona Server
  • Amazon RDS / Aurora MySQL, Azure Database for MySQL, Google Cloud SQL

How to migrate Firebird to MySQL

1

Setup: connect Firebird and MySQL

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

The Setup step in DBConvert: the mode, the Firebird source and MySQL destination side by side, and the job name

Sync keeps an existing MySQL database up to date with Firebird: each run carries only the inserts, updates and deletes since the last one.

The Setup step in Sync mode for Firebird to MySQL: how changes are detected and the direction

Firebird source

Point DBConvert at a Firebird .fdb / .gdb file or a Firebird 2.5 / 3.0 / 4.0 server — Firebird source settings. Normalize the source charset to utf8mb4-compatible UTF8 before the load.

MySQL target

Use the MySQL connection guide for local MySQL or MariaDB, or Amazon RDS / Aurora for MySQL, Azure Database for MySQL, or Google Cloud SQL for MySQL. Create the target schema as utf8mb4.

2

Tables & mapping: see every MySQL type before a row moves

Pick the tables, then open one: each Firebird column shows the MySQL type it becomes. Change a type or a name in place; the line at the bottom names anything that would fail.

Tables and mapping for Firebird to MySQL: the table list and one table's columns with their MySQL types
3

Execution: start it, and the job is saved

Review what the run will do, start it, and read the log as it goes. The job stays in the list to run again or put on a schedule.

A finished Firebird to MySQL conversion: the summary and the operation log

Every option, in the guide

Naming rules, table options, row filters, scheduling and the command line work the same for every database pair, so they live in one place.

Move Firebird data into MySQL

Download the current build and run the first job against your own database.

Windows Windows 10 or later · 23.4 MB