SQL Server to PostgreSQL conversion and synchronization.

DBConvert / DBSync database migration software automates the conversion and synchronization of your data from Microsoft SQL Server to PostgreSQL and vice versa. Transfer the database schema, all data, or select only the required data set during the configuration pass in an easy-to-use, wizard-style graphical interface.

Why Migrate from MS SQL Server to PostgreSQL?

  1. The main advantage of PostgreSQL over SQL Server is the licensing cost. PostgreSQL is completely free, and the cost of an MSSQL server depends on the number of users and the size of a database.
  2. SQL Server from Microsoft is a proprietary database instead of PostgreSQL, which is developed and maintained by a global community of open source developers and companies.
  3. Another good reason to try Postgres from a DBA perspective is high availability. If you have any requirements (HA) and cannot afford even a standard SQL Server edition license, go Postgres.
  4. Cross-platform support was another PostgreSQL advantage until Microsoft released SQL Server for Linux in 2017. Both database engines are now available for Windows and Linux. For other deployment scenarios, you can use Docker containers and database clusters on Kubernetes.

Although Microsoft SQL Express is free, it is heavily limited compared to other editions of SQL Server. So if the pricing is an issue, then you should switch to PostgreSQL.

Data type Mapping.

MS SQL Server and PostgreSQL databases are ANSI-SQL compliant. But there are still differences between SQL syntax, data types, and case sensitivity. Mapping data types from SQL Server to PostgreSQL manually isn't all that trivial. Built-in data mapping in DBConvert tools helps to map SQL Server data types to Postgres data types automatically. Besides, there is a manual way to map data types.

Disadvantages of some open-source tools.

While there are some free open source solutions like Pgloader or Sqlserver2pgsql, there are some drawbacks to using them.

  • These are command-line utilities, so they don't have a graphical interface. For those who are intimidated by the terminal, they are not easy to use.
  • These tools are limited to one-way migrations where PostgreSQL can be configured as a destination.

Six reasons to use DBConvert for migrating from SQL Server to PostgreSQL?

  1. DBConvert tools are highly customizable and allow you to quickly and easily export data from SQL Server to Postgres using a comprehensive graphical interface. The DBConvert apps guide you through a few steps, from connecting to the source and target databases, configuring many parameters, and scheduling subsequent launches.
  2. In any combination, data conversion and synchronization between the following databases are possible:
  3. The new DBConvert parallel migration mechanizm is optimized to take full advantage of modern multi-core processors. That speeds up data migration between databases by splitting tables into multiple parts and processing them in parallel.
  4. DBSync software keeps your databases in Sync with Update, Insert, and Drop synchronization features.
  5. Bi-directional synchronization helps to update data in both source and destination databases simultaneously.
  6. 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.
Supported databases:
  • Microsoft SQL Server
  • PostgreSQL
  • CockroachDB
  • SQL Azure
  • Amazon RDS
  • Heroku Postgres
  • MS SQL Dump
  • PostgreSQL Dump
  • PHP Script
 DBConvert for MSSQL & PostgreSQL

Version: 3.6.8

Release Date: April 3, 2024

 DBSync for MSSQL & PostgreSQL

Version: 2.9.9

Release Date: April 25, 2024

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

DBConvert Studio

 Version: 4.0.5

Release Date: May 16, 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 SQL Server 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 SQL Server source database.

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

Connect to SQL Server 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 SQL Server 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 SQL Server source and PostgreSQL target database connection settings with other specified options.


C:\Program Files\DBConvert\mssql2postgresqlPro\mssql2postgresqlPro_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:


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


Explore details regarding reverse migration.