Convert MySQL to SQL Server.

DBConvert / DBSync software automates the conversion and synchronization of your data from MySQL to Microsoft SQL Server and vice versa. Migrate the entire database, or select only the dataset you need during the configuration pass in a user-friendly wizard-style GUI.

At the core level, both MySQL and Microsoft SQL Server have a lot in common. The reason for migrating or syncing data depends on your business needs, available budget, and environment.

Microsoft SQL Server Migration Assistant for MySQL performs the tasks of migrating MySQL to SQL Server. But with SSMA, you can only transfer data in ONE direction to MSSQL. Also, it does not perform tasks such as synchronization between MySQL and MS SQL Server.

Why use DBconvert tools?

  1. DBConvert and DBSync for MySQL and MS SQL perform database conversion and synchronization tasks between the following databases in any direction:
    • Microsoft SQL Server,
    • MariaDB,
    • Percona,
    • Windows Azure SQL Databases/ Azure SQL Data Warehouse,
    • Azure Database for MySQL,
    • AWS RDS/ Aurora,
    • Google Cloud SQL for SQL Server,
    • Google Cloud SQL for MySQL.
  2. Data types in MS SQL and MySQL are similar but not the same. The Type Mapping feature helps you map MySQL data types to their closest and relative SQL Server equivalents.
  3. Parallel migration engine of DBConvert takes full advantage of modern multi-core processors. It speeds up data migration by splitting database tables into multiple parts and processing them in parallel.
  4. You don't need to know how to write scripts to convert views from MySQL to SQL Server. DBConvert will convert every selected view automatically.

Database synchronization between MySQL and SQL Server.

After copying your data from source MySQL to the target SQL Server, you would need to sync your data. DBSync software keeps your databases totally in sync with Update, Insert, and Drop synchronization types.

Trigger-based synchronization algorithm instantly tracks changes in both source and destination databases. The trigger-based sync method increases recurrent synchronization speed in times.

Bi-directional synchronization helps to update data in both MySQL and MSSQL databases simultaneously.

Supported databases:
  • SQL Server
  • MySQL
  • MariaDB
  • SingleStore DB (formerly MemSQL)
  • TiDB
  • Percona Server for MySQL
  • Vitess
  • Azure Database for MySQL
  • SQL Azure
  • Amazon RDS
  • Amazon Aurora
  • Google Cloud
  • ☑ Views conversion between SQL Server and MySQL
  • MySQL Dump
  • PHP Script
  • SQL Server Dump
 DBConvert for MSSQL & MySQL

Version: 4.3.1

Release Date: Sept. 9, 2022

 DBSync for MSSQL & MySQL

Version: 5.4.6

Release Date: Sept. 23, 2022

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

DBConvert Studio

 Version: 3.4.4

Release Date: Sept. 16, 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 MySQL 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 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 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:

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

Example: C:\Program Files\DBConvert\mssql2mysqlPro\mssql2mysqlPro_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 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 SQL Server (this requirement is optional as there is an option to overcome the restrictions using dump file)


Read information about reverse migration.