Microsoft Access Migration And Sync

Microsoft Access is a one of the most popular entry-level desktop database management system available today. MS Access uses a familiar Microsoft Office UI which makes it understandable enough even to less experienced database developers.

Our DBConvert tools make it possible to scale MS Access applications when they need to be upsized to enterprise level solutions or access data needs to be published to the web. DBSync apps are able to easily replicate data between MS Access and other DBMS.

Both MS Access x86 and Access x64 databases are supported.

Note that all Access related converters and sync tools are able to move data between two Access databases configured as a source and a target database.

Top 5 Reasons to Migrate from Microsoft Access to Server databases:
  1. Deployment of information. Migrating Access to a server based solution opens up your possibilities to utilize your data. Any kind of server-based client can use the information, not just Access. This allows your data to be exploited extensively in more contexts, and by more people, increasing its value.

    Your database becomes more accessible over the Web. Although Access provides some capabilities for making a web-based database, there is undoubtedly a wider range of options available for server databases. In addition, the web interface is the best solution for providing a platform-independent entry point to your information. Browsers on many types of machines and devices can access it.

  2. Management of large databases. The total size for an Access database is limited to about 2 Gb. Server dbms routinely manage terabytes of data efficiently.

  3. Multi-user access. MS Access is generally intended for a single-user environment in a local use scenario. Although Access provides capabilities for data sharing, that is not really its strength. A server database offers the ability to manage large amounts of data efficiently. Such server database were designed from the beginning to run in a networked environment for supporting large numbers of clients simultaneously.

  4. Integrity and Backup management.Migrating data from Access to a server-side database provides benefits for data integrity and backups. Server databases provide centralized places to store data and automated capabilities for performing backups exist for all popular database platforms. Backup can be more complicated for individual Access users who store their data locally.

  5. Hardware/ Platform choices. Server database engines run on several platforms including Linux, Unix and Windows. If you use Access you are limited to the Windows family OS exclusively.

DBConvert Studio 

 Version: 1.3.8

Release Date: Jan. 16, 2018

Supported databases:

  • Microsoft SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Microsoft Access
  • Microsoft FoxPro
  • SQLite
  • Firebird
  • Microsoft Excel
  • IBM DB2
  • MS Azure SQL
  • Amazon RDS
  • Heroku Postgres
  • Google Cloud
DBSync for Access & MySQL

Version: 6.8.1

Release date: Nov. 30, 2017

Synchronization directions:

  • Access ↔ MySQL, MariaDB, Percona
  • MySQL ↔ MariaDB ↔ Percona ↔Amazon RDS
  • Access ↔ Amazon RDS
  • Access ↔ Google Cloud
  • Access ↔ Azure Database for MySQL
DBSync for Access & MSSQL

Version: 4.1.2

Release date: July 19, 2017

Synchronization directions:

  • Access ↔ MS SQL Server
  • Access ↔ SQL Azure
  • MS SQL Server ↔ SQL Azure
  • Access ↔ Amazon RDS
DBSync for Access & PostgreSQL

Version: 4.2.0

Release date: Feb. 6, 2017

Synchronization directions:

  • MS Access ↔ PostgreSQL
  • Access ↔ Amazon RDS ↔ Heroku Postgres
DBSync for Access & FoxPro

Version: 3.4.5

Release date: Sept. 12, 2015

Synchronization directions:

  • Access → FoxPro free tables *.DBF
  • Access → FoxPro database *.DBC
  • FoxPro → Access
DBSync for Access & Firebird

Version: 1.1.8

Release date: July 8, 2016

Synchronization directions:

  • Access ↔ Firebird
  • Access ↔ InterBase
  • InterBase ↔ Firebird
DBSync for Access & SQlite

Version: 1.0.8

Release date: Aug. 15, 2016

Synchronization directions:

  • Access → SQLite
  • SQLite → Access
DBSync for Oracle & Access

Version: 1.2.0

Release date: July 14, 2016

Synchronization directions:

  • Access ↔ Oracle
  • Access ↔ Amazon RDS
DBConvert for Access & MySQL

Version: 8.3.5

Release date: Jan. 12, 2018

Conversion directions:

  • Access → MySQL, MariaDB, Percona, MySQL Dump, PHP Script
  • MySQL, MariaDB, Percona → MS Access
  • Queries from Access → MySQL, MariaDB, Percona views migration
  • Access ↔ Amazon RDS
  • Access ↔ Google Cloud
  • Access ↔ Azure Database for MySQL
DBConvert for Access & MSSQL

Version: 6.1.0

Release date: Oct. 5, 2017

Conversion directions:

  • Access x86/x64 → MS SQL Server, MS SQL Dump
  • MS SQL Server → Access 32/64
  • Access queries → MS SQL Server views
  • Access 32/64 ↔ SQL Azure
  • Access x86/x64 ↔ Amazon RDS
DBConvert for Access & PostgreSQL

Version: 4.3.7

Release date: Jan. 11, 2018

Conversion directions:

  • Access → PostgreSQL, Dump, PHP Script
  • PostgreSQL → Access
  • Access ↔ Amazon RDS ↔ Heroku Postgres
  • MS Access queries → PostgreSQL views
DBConvert for Access & FoxPro

Version: 3.4.5

Release date: Sept. 12, 2015

Conversion directions:

  • Access → FoxPro free tables *.DBF
  • MS Access → FoxPro database *.DBC
  • FoxPro → Access
DBConvert for Access & Firebird

Version: 1.2.2

Release date: July 29, 2016

Conversion directions:

  • Access → Firebird, Firebird Dump, InterBase
  • Firebird → Access, Firebird Dump, InterBase
  • InterBase → Access, Firebird, Firebird Dump
DBConvert for Access & SQlite

Version: 1.1.0

Release date: Jan. 17, 2018

Conversion directions:

  • Access → SQLite
  • SQLite → Access
DBConvert for Oracle & Access

Version: 1.1.8

Release date: July 12, 2016

Conversion directions:

  • Access → Oracle, Oracle Dump
  • Oracle → MS Access
  • Oracle → Oracle Dump
  • Access ↔ Amazon RDS