MySQL to PostgreSQL conversion and synchronization.

DBConvert and DBSync for MySQL and PostgreSQL are database migration and synchronization tools designed to simplify the data conversion from MySQL to Postgres.

Transferring data between two different management systems is not a trivial task. There are many obstacles to direct data export. So tools to help transfer data between MySQL and PostgreSQL are in great demand in the market.

Let's compare the well known open source tool, pgloader, with the DBConvert / DBSync DB migration tools.

Pgloader vs. DBConvert tools.

  1. CLI vs. GUI.

    Pgloader is a command-line tool and thus doesn’t have a visual interface.


    DBConvert tools are highly customizable and allow you to quickly and easily export data from MySQL to Postgres using a comprehensive graphical interface.

  2. Configuration.

    To use pgloader, you need to configure it manually before starting database conversion. To be successful with pgloader, you have to do a bit of work to create working configurations.


    In DBConvert products, the target database is presented in the form of a tree, which greatly simplifies the configuration of settings. The proven advantage of DBConvert software is that it can be effectively used by non-professional users.

  3. Database migration directions.

    Pgloader serves data conversion tasks from various databases to PostgreSQL. In other words it transfers databases in ONE direction only.


    In any combination, using our software, data migrations between the following databases are possible:

    Refer to the list of all available conversion and sync directions in the sidebar on the right.

  4. Parallel processing of data.

    The new parallel migration engine of DBConvert takes full advantage of modern multi-core processors. That speeds up data migration between MySQL and Postgres databases by splitting tables into multiple parts and processing them in parallel.

  5. Database synchronization.

    DBSync software keeps your databases in Sync with Update, Insert, and Drop synchronization features.

    Bi-directional synchronization helps to update data in both source and destination databases simultaneously.

    Trigger-based Synchronization algorithm is developed to accurately analyze the destination database data and instantly track changes in both databases. The trigger-based sync method increases recurrent synchronization speed in times.

Even if you have no direct access to MySQL or PostgreSQL servers, generated by DBConvert dump files are useful to get over server access restrictions.

For recurring synchronization and conversion processes, use the Built-in Scheduler.

Convert MySQL to PostgreSQL

Moving and synchronizing data from MySQL to PostgreSQL can't be more comfortable than using our migration software. Wizard interface will guide you through several easy steps to perform fast and robust data migration and sync from MySQL to Postgres.

DBConvert Streams.

DBConvert Streams is a powerful, flexible software solution that converts heterogeneous databases and facilitates real-time Change Data Capture (CDC) data replication.

This preview version of DBConvert Streams is free, allowing users to explore its capabilities and benefits. The cross-platform and cloud-first software enables seamless execution across different operating systems and cloud environments. It can also be efficiently run in a Docker container, providing a convenient and scalable deployment option.

With its blazingly fast performance, DBConvert Streams excels in data transfer speed. For example, it can transfer 10 million records in approximately 30 seconds, showcasing its high efficiency. Moreover, it took about 6 minutes to copy 100 million records from the source to the target database, further demonstrating its impressive performance.

Event-driven replication feature makes it an ideal tool for data integration and streaming across distributed platforms.

For further information, please refer to the DBConvert Streams documentation available at https://stream.dbconvert.com

Supported databases:
  • MySQL
  • PostgreSQL
  • MariaDB
  • SingleStore DB (formerly MemSQL)
  • TiDB
  • Percona Server for MySQL
  • Vitess
  • CockroachDB
  • Amazon RDS for MySQL
  • Amazon RDS for PostgreSQL
  • Amazon Aurora (MySQL Compatible)
  • Amazon Aurora (PostgreSQL Compatible)
  • Heroku Postgres
  • Azure Database for MySQL
  • Azure Database for PostgreSQL
  • Google Cloud
  • PostgreSQL Dump
  • PostgreSQL PHP Script
  • MySQL Dump
  • MySQL PHP Script
 DBConvert for MySQL & PostgreSQL

Version: 4.4.0

Release Date: June 13, 2024

 DBSync for MySQL & PostgreSQL

Version: 3.8.8

Release Date: May 1, 2024

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

DBConvert Studio

 Version: 4.1.3

Release Date: Sept. 19, 2024

Supported databases:

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

Using MySQL to PostgreSQL conversion and synchronization tools.

When launching the DBConvert or DBSync application in GUI mode, it seamlessly guides you through the steps to initiate database migration or synchronization:

1. Connect to MySQL source database.

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to MySQL source database from DBConvert

2. Connect to PostgreSQL destination database.

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to PostgreSQL target database from DBConvert

NOTE #1: Each DBConvert or DBSync tool's name comprises two different databases, enabling any specified database to operate as the source or destination. Furthermore, the same type of database can function as both the source and destination.

NOTE #2: Connections to cloud databases (e.g., Amazon RDS, Google Cloud, or Azure SQL) aren't explicitly specified in the user interface but use the same settings as traditional on-premises databases.

NOTE #3: Connections to source and target databases remain active until you close the DBConvert/DBSync application or reopen new connections.

Refer to our documentation for specific source/ destination configurations for different databases.

3. Configure database migration options.

Specify the tables, fields, indices, and views you want to transfer to the PostgreSQL destination database by checking/unchecking the corresponding boxes.

Customize general database/ tables settings. Or configure specific table , field, index object individually when migrating data.

Explore our articles in the user's manual about Configuring database migration options. for detailed information.

The screenshot below summarizes the general features available in DBConvert software.

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

The database enforces certain relations on the data, and on the customization step, an intelligent error checker verifies all possible data integrity and referential integrity issues. It highlights any problems before migration starts.

By default, DBConvert attempts to automatically map the database types of the source MySQL database to the closest equivalent of the target PostgreSQL database types. However, you can manually change the data types for the entire database globally using the "Global mapping" or individually for each field.

Explore the Intelligent error checker for more information. on errors and warnings

5. Execution. The final stage of data migration.

Initiate the conversion or synchronization process after configuring source and destination databases in the previous steps.

Click the "Commit" button to start conversion. Here, you can also monitor the migration/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

Explore more about the options available during the execution stage

Command line mode

Pass previously saved sessions as parameters to the Command-Line DBConvert Client. A session retains MySQL source and PostgreSQL target database connection settings with other specified options.

Example:

C:\Program Files\DBConvert\mysql2postgresqlPro\mysql2postgresqlPro_Cons.exe /Session:"Session_Name"

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

Built-in scheduler.

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

Find more Information about the built-in scheduler

DBConvert screenshot

Supported OS:

Requirements

  • 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)
  • Necessary privileges to write into database on the target PostgreSQL server (this requirement is optional as there is an option to overcome the restrictions using dump file or PHP Script)

Highlights

Explore details regarding reverse migration.