Convert MySQL to Firebird.

DBConvert/ DBSync software are intended for performing migration tasks easily and reliably from MySQL/ MariaDB to Firebird/ Interbase. InterBase, Firebird, MySQL and MariaDB server connections may be set up as nodes for conversion/ synchronization in any combination. MySQL Dump files may be generated to bypass firewalls restriction, if you cannot use direct connection to servers.

DBSync software is dedicated to make synchronization from MySQL Server to Firebird and vice versa. Insert, update and drop synchronization make overall synchronization possible and your database up-to-date.

 DBConvert for Firebird & MySQL

Migration directions:

  • Firebird → MySQL, MariaDB, MySQL Dump, PHP Script, InterBase, Firebird Dump
  • MySQL, MariaDB → Firebird, MySQL Dump, PHP Script, Firebird Dump, InterBase
  • InterBase → MySQL, MariaDB, MySQL Dump, PHP Script, Firebird, Firebird Dump
  • Firebird ↔ Amazon RDS | Aurora ↔ Interbase
  • Firebird ↔ Google Cloud ↔ Interbase
  • Firebird ↔ Azure Database for MySQL ↔ Interbase

Version: 1.5.8

Release Date: March 11, 2019

 DBSync for Firebird & MySQL

Sync directions:

  • Firebird → MySQL, MariaDB, InterBase
  • MySQL, MariaDB → Firebird, InterBase
  • InterBase → MySQL, MariaDB, Firebird
  • Firebird ↔ Amazon RDS | Aurora↔ Interbase
  • Firebird ↔ Google Cloud ↔ Interbase
  • Firebird ↔ Azure Database for MySQL ↔ Interbase

Version: 1.6.1

Release Date: July 18, 2018

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 1.8

Release Date: Aug. 4, 2020

Supported databases:

  • SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Firebird
  • Excel
  • IBM DB2
  • Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Related Links

Supported OS:

Using MySQL to Firebird conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to MySQL source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to MySQL source database from DBConvert

2. Connect to Firebird destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to Firebird target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • MySQL to Firebird
  • Firebird to MySQL
  • MySQL to MySQL
  • Firebird to Firebird

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the Firebird destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from MySQL to Firebird.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source MySQL database to the closest equivalent of the target Firebird database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from MySQL to Firebird

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps MySQL source and Firebird target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\firebird2mysqlPro\firebird2mysqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

Requirements

  • Firebird 2.x.x and higher
  • Necessary privileges to write into database on the target MySQL server (this requirement is optional as there is an option to overcome the restrictions using dump file or PHP Script)