Convert PostgreSQL to SQL Server.

With our DBConvert/DBSync applications, you can easily synchronize and convert your databases from PostgreSQL to Microsoft SQL Server or to Windows Azure SQL Databases. Amazon RDS PostgreSQL/Heroku Postgres instances can also be used as a source or target. The wizard-style interface will guide you through all the steps of performing migration and replication jobs efficiently and effectively.

Reasons to migrate from PostgreSQL to MS SQL Server?

  1. Compatibility with other systems: If you are using other systems or applications that are compatible only with SQL Server, then converting your PostgreSQL database to SQL Server can make it easier to integrate with these systems.
  2. Performance: In some cases, SQL Server may offer better performance than PostgreSQL, especially for complex queries or large datasets.
  3. Features: SQL Server offers a number of features that are not available in PostgreSQL, such as support for in-memory OLTP, automatic tuning, and advanced security features.
  4. Ease of use: Some users may find SQL Server easier to use or more familiar than PostgreSQL, which could make it a better choice for certain projects.

The new DBConvert parallel migration mechanism is optimized to take full advantage of modern multi-core processors, which speeds up data migration between databases by splitting tables into multiple parts and processing them in parallel.

In scenarios where you have server restrictions, you can create an MS SQL Dump file with all the data from your PostgreSQL database.

Why you might want to synchronize a PostgreSQL database with an SQL Server DB?

  • Data replication: Synchronizing the databases allows you to replicate data between the two systems, which can be useful for backup, disaster recovery, or creating a data warehouse.
  • Improved performance: Synchronizing the databases can help improve performance by allowing you to distribute the workload between the two systems. For example, you could use PostgreSQL for transactional processing and SQL Server for reporting and analysis.
  • Integration with other systems: Synchronizing the databases can make it easier to integrate with other systems or applications that use SQL Server.
  • Consolidation of data: Synchronizing the databases can help you consolidate data from multiple sources, making it easier to manage and analyze.
  • Cross-platform compatibility: Synchronizing the databases allows you to work with data across platforms, which can be useful if you are using a mix of Windows and Linux systems.

The DBSync application performs synchronization and replication from a PostgreSQL source to Microsoft SQL Server smoothly due to

three synchronization types (Drop, Insert, Update).

Additionally, our built-in scheduler lets you to launch automatically, with no interaction required from you.

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.6

Release Date: Sept. 9, 2022

 DBSync for MSSQL & PostgreSQL

Version: 2.9.7

Release Date: Oct. 18, 2022

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

Using PostgreSQL to SQL Server 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 PostgreSQL source database.

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

Connect to PostgreSQL source database from DBConvert

2. Connect to SQL Server 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 SQL Server 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:

  • PostgreSQL to SQL Server
  • SQL Server to PostgreSQL
  • PostgreSQL to PostgreSQL
  • SQL Server to SQL Server

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 SQL Server 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 PostgreSQL to SQL Server.

Check out our articles about Configure database migration options. 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.

By default, DBConvert tries to automatically map the database types of the source PostgreSQL database to the closest equivalent of the target SQL Server 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 PostgreSQL to SQL Server

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

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


  • 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)


Read information about reverse migration.