Migrating data from Firebird to MySQL

This guide walks you through migrating data from Firebird to MySQL in a few simple steps using ESF Database Migration Toolkit. Simplify complex migration tasks and save valuable time with our streamlined approach.

Firebird vs. MySQL:

FireBird is an open-source relational database management system (RDBMS) that offers robust features, high performance, and scalability. It provides cross-platform support, running on Windows, Linux, macOS, and various Unix platforms. With its SQL compliance, ACID transactions, and multi-generational architecture, Firebird is well-suited for both small-scale applications and enterprise-level deployments. Additionally, its lightweight footprint and minimal administration requirements make it a popular choice for embedded database solutions.
MySQL is an open-source relational database management system (RDBMS) that provides a powerful and scalable platform for managing and storing data. Developed by Oracle Corporation, MySQL is widely used in web applications and is known for its reliability, flexibility, and ease of use. It supports various storage engines, including InnoDB for transactional processing and MyISAM for read-intensive applications, offering developers the flexibility to choose the engine that best suits their needs. With features like ACID compliance, replication support, and a thriving community of developers, MySQL is a popular choice for businesses of all sizes looking to build robust and efficient database-driven applications.

Prerequisite:

Software Required:

DMToolkit_x64.zip (63.5 MiB)	64-bit Windows application for ESF Database Migration Toolkit 12.2.07 (2025-07-01). (md5: 0750355677f7108916a6c1f2bc0d4d87)
DMToolkit_win32.zip (58.9 MiB)	32-bit Windows application for ESF Database Migration Toolkit 12.2.07 (2025-07-01). (md5: a9ba6351d787ff958b4ff2d9ca888576)

System Supported:
- Windows 7 or higher.
- Firebird 1.5 or higher.
- MySQL 3.23 or higher.

Step by Step Wizard:

Configure Firebird/InterBase Connection
- In the Choose a Data Source dialog:
  - Select Firebird/InterBase from available options
- Provide authentication credentials:
  - Username: SYSDBA (default)
  - Password: masterkey (default)
- Select the database character set from dropdown
- Specify database location:
  - Click the [...] button (Browse)
  - Select your Firebird (.fdb) or InterBase (.gdb) file
- For network connections:
  - Enter server address in format: [server_name][/port][/path_to_file]
  - Examples:
    - localhost/3050:/var/db/test.fdb
    - dbserver.example.com:/data/prod.gdb
Fig. 1: Configuring Firebird/InterBase data source
Configure MySQL Destination
- In the "Choose a Destination" dialog:
  - Select "MySQL"
- Enter connection parameters:
  - Server name: localhost (default)
  - Port: 3306 (default)
  - Username and Password
- Optional configurations:
  - Select a MySQL storage engine
  - Specify character set (e.g., UTF-8)
- Database selection/creation:
  - Click the Refresh button to list available databases
  - Either:
    - Select existing database from list
    - Or enter new database name
  - Note: New databases will be automatically created during migration
Fig. 2: MySQL destination configuration
In "Select Source Table(s) & View(s)" Dialog
- Select migration objects: Choose tables or views to include in the migration.
  
  Fig. 3: Select tables and views
- Modify table structure: Click the ellipsis (...) button to access table options and schema adjustments.
  
  Fig. 4: Do transform
- Configure field mapping: In the Field Mapping options:
  - Customize destination fields (name, data type, default value, comments)
  - Select data transfer method:
    - Overwrite Table (replace existing data)
    - Empty Data (truncate before insert)
    - Append Data (add to existing data)
    - Skip Table (exclude from transfer)
  - Apply data filters before transfer
Execution Dialog
- Start migration: Click "Submit" to initiate automated data transfer from Firebird to MySQL.
  
  Fig. 5: Execute migration
- Monitor progress: Click "Browse Log" for real-time migration tracking, including issue resolution details.
- Save configuration: Click "Save as job" to store settings for:
  - Quick reloads of migration jobs
  - Command-line execution (use: dmtc.exe --help for parameter options)
Finished!

After migration completes, the toolkit generates a comprehensive report for verifying migration accuracy. You can monitor progress as the automated process runs efficiently. For any questions or feedback, contact us – our team is ready to assist.