Convert MySQL to PostgreSQL.

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

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 MySQL to PostgreSQL converters, data migrations between the following databases are possible:

    Refer to the list of available conversion and sync directions in product info cards on the right.

  4. Parallel migration.

    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 PostgreSQL databases.

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.

Its event-driven replication feature supports MySQL and PostgreSQL databases, making 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.3.8

Release Date: Sept. 12, 2022

 Download 23.9 MB  Order from US$ 179
 DBSync for MySQL & PostgreSQL

Version: 3.8.6

Release Date: Nov. 21, 2022

 Download 24.4 MB  Order from US$ 179

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

DBConvert Studio

 Version: 3.4.0

Release Date: May 17, 2023

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
  About Studio   Download 120.0 MB      Order from US$ 599

Using MySQL to PostgreSQL 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 PostgreSQL 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 PostgreSQL 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 PostgreSQL
  • PostgreSQL to MySQL
  • MySQL to MySQL
  • PostgreSQL to PostgreSQL

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, 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. Configure database migration options.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the PostgreSQL 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 PostgreSQL.

Check out our articles about Configure database migration options. for detailed information.

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

DBConvert screenshot
  1. Workaround for firewalls and access rights
  2. Views translation
  3. Flexible customization for all db elements
  4. Bulk Insert and Quantization options for speed-up processing of big volume of data
  5. Conditional data migration. Data Filters.
  6. Full UNICODE architecture support
  7. Data mapping
  8. Proactive detection of potential data migration issues
  9. Command line mode. Scheduling
  10. Savable sessions

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.

By default, DBConvert tries 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.

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

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

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 PostgreSQL target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\mysql2postgresqlPro\mysql2postgresqlPro_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.

Find more Information about 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)

Related Links

Highlights

Read information about reverse migration.

PostgreSQL to MySQL