Convert SQL Server to Access.

The programs we offer support the conversion and synchronization of Microsoft SQL database structures, tables, fields, and indexes to Microsoft Access 32/64 formats.

With a wide range of options, the migration process can be tailored to your specific needs for optimal results.

While Microsoft SQL Server is generally considered to be a more advanced database system, there may be situations where migrating data from MS SQL to MS Access is necessary.

Reasons to migrate data from SQL Server to MS Access.

There are several reasons why someone may want to move or synchronize data between Microsoft SQL Server and Microsoft Access. Some of the most common reasons include:

  • Data Analysis: Access is often used as a tool for data analysis and reporting, while SQL Server is typically used as a more robust and powerful database management system. Synchronizing data between the two allows users to take advantage of the reporting and analysis capabilities of Access while still leveraging the power of SQL Server for data management.
  • Data Backup: SQL Server is often used as a primary data storage system, while Access is used as a backup or offline copy of the data. Synchronizing data between the two ensures that the backup copy is always up to date.
  • Data Sharing: Access is often used as a way to share data with a small group of users, while SQL Server is used to share data with a larger group of users or with other systems. Synchronizing data between the two allows all users to have access to the most up-to-date data.
  • Data Migration: An organization might be using Access as a database and want to move to SQL Server as a database because of its scalability, performance and security. Synchronizing the data from Access to SQL Server will help in a smooth transition.

Our solutions make it easy to synchronize data between MS SQL/Windows Azure SQL databases and MS Access.

Our programs run smoothly and quickly without the need for manual intervention. Simply connect to your source and destination databases, configure the necessary parameters, and start the migration process. The wizard interface and command line options allow you to easily schedule automated jobs.

Run our programs using the easy-to-use wizard interface or through our powerful command line to automate scheduling jobs.

Supported databases:
  • Microsoft Access x86/x64
  • Microsoft SQL Server
  • Access queries → MS SQL Server views
  • Azure Database for SQL Server
  • Amazon RDS
  • Amazon Aurora
  • Google Cloud
  • SQL Dump
 DBConvert for Access & MSSQL

Version: 6.1.4

Release Date: Sept. 16, 2022

 DBSync for Access & MSSQL

Version: 4.1.6

Release Date: Oct. 25, 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 SQL Server to Access 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 SQL Server source database.

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

Connect to SQL Server source database from DBConvert

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

  • SQL Server to Access
  • Access to SQL Server
  • SQL Server to SQL Server
  • Access to Access

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

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 SQL Server database to the closest equivalent of the target Access 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 SQL Server to Access

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

Example: C:\Program Files\DBConvert\access2mssqlPro\access2mssqlPro_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:


  • Microsoft Visual C++ 2008 x86 Redistributable package
  • 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)
  • Access 2000 or higher. Both Access 32/64 versions are supported


Read information about reverse migration.