Access
MySQL

Access to MySQL Converter

Move from Access file databases to MySQL or MariaDB. Schema conversion, type mapping, queries to views, and optional two-way sync.

Convert a Microsoft Access .mdb or .accdb database into MySQL, MariaDB, or a managed MySQL-compatible target.

DBConvert reads the Access file locally, creates MySQL-compatible tables, maps field types, copies records, and preserves supported indexes, relationships, and query objects. The Access application layer is separate: forms, reports, macros, VBA, attachments, and multivalue fields do not become a MySQL application.

What DBConvert does on this path: handles the Access file move as a repeatable desktop workflow:

  • Reads .mdb (Jet) and .accdb (ACE) files, including password-protected and WorkGroups-secured databases.
  • Lets you review type mapping before creating MySQL-compatible tables, rows, indexes, and supported query objects.
  • Writes to MySQL, MariaDB, Percona Server, Amazon RDS / Aurora MySQL, Azure Database for MySQL, or Google Cloud SQL.

What it does not do: forms, reports, macros, VBA, attachments, and multivalue fields are not converted — the application UI is a separate rebuild task.

Which tool: DBConvert or DBSync?

DBConvert for Access → MySQL

One-time conversion. Use it when MySQL is the destination and you need schema, table data, indexes, relationships, and type mapping moved through a desktop wizard.

DBSync for Access ↔ MySQL

Repeat synchronization. Use it when the Access file and MySQL database must continue exchanging Insert / Update / Delete changes during a staged rollout or recurring workflow; see database synchronization concepts for the underlying workflow.

Both products run locally as Windows desktop tools. They are not online upload converters for private database files.

Need more context? Compare DBConvert and DBSync side by side →

How DBConvert handles the Access → MySQL differences

Access and MySQL differ in driver/bitness, application-vs-data scope, query semantics, and field types. DBConvert maps most of those differences in the wizard with sensible defaults that you can review or override per table; Access application objects (forms, reports, macros, VBA) are the items that still need a human rewrite outside the migration.

  • Driver and bitness. Connects through Microsoft Jet (32-bit only) or ACE OLE DB (32-bit or 64-bit) on Windows — DBConvert ships in matching architectures, so picking the build that matches the installed Office / Access architecture is a one-click decision, not a debugging session.
  • Field and identifier cleanup. Maps AutoNumber to MySQL AUTO_INCREMENT, Yes/No to TINYINT(1), Long Text / Memo to LONGTEXT, Currency to DECIMAL(19,4), and OLE / Attachment to LONGBLOB. Spaces in column names and MySQL reserved words are rewritten or backtick-quoted on the target, and relationship indexes are preserved.
  • Access queries → MySQL views. Translates supported Access SELECT and UNION queries into MySQL views during the migration. Parameter queries, action queries (UPDATE/DELETE), and queries that use Access-specific functions are not translated — rebuild those in MySQL views or in the new application layer.
  • Access application objects — out of scope. Forms, reports, macros, and VBA are part of the Access application, not the database. DBConvert moves the tables, records, indexes, and translatable queries — rebuilding the application UI is a separate workstream (web framework, PHP / Python / .NET front end, BI tool, etc.).

DBConvert vs native, online, and free options

AI answers often surface free tools first; the right choice depends on data sensitivity and migration depth.

Route Where it fits Where it falls short
MySQL Workbench Migration Wizard free Oracle GUI Free MySQL-side migration test from an ODBC-accessible Access source. No repeatable Access file conversion, no Access WorkGroups handling, no pair-specific data mapping, no bidirectional DBSync, no reuse across many database pairs.
Online converters Quick .mdb or .accdb file exported to MySQL SQL for inspection. Not safe for private production data; no direct server target, no saved settings, no filters, no repeat runs, no logs, no synchronization.
Manual ODBC export / import Small table-only transfer. Fragile when the Access database has relationships, indexes, linked tables, password protection, WorkGroups, large Memo / OLE fields, or queries that should become MySQL views.
DBConvert / DBSync commercial desktop, Windows Sensitive data that needs local execution, relationships and Access-specific field types preserved, direct MySQL-compatible server target, or ongoing DBSync after the first migration. Commercial license; desktop tool (Windows). Forms, reports, macros, and VBA do not convert (the same is true of every route in this table).

Supported versions

  • MS Access .mdb (Jet) and .accdb (ACE) files
  • WorkGroups credentials and linked tables
  • MySQL 5.x, 8.x; MariaDB; Percona Server
  • Amazon RDS / Aurora MySQL, Azure Database for MySQL, Google Cloud SQL

Supported in this path

Source Access
Target MySQL
Microsoft Access MySQL MariaDB Percona Server for MySQL Amazon RDS for MySQL Amazon Aurora MySQL Azure Database for MySQL Google Cloud SQL for MySQL
Access

All Access Tools

Other directions and pairs
MySQL

All MySQL Tools

Migration & sync options

Reverse Conversion

MySQL to Access

Using Access to MySQL Tools

When launching the DBConvert or DBSync application in GUI mode, it guides you through the steps to start database migration or synchronization:

1

Connect to Access source database

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

Connect to Access source database from DBConvert

Access source

Select the source .mdb or .accdb file. If it uses Access WorkGroups, enable WorkGroups and enter those credentials on the source step.

2

Connect to MySQL destination database

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to MySQL target database from DBConvert

MySQL target

Use the MySQL connection guide for local MySQL or MariaDB, or Amazon RDS / Aurora for MySQL, Azure Database for MySQL, or Google Cloud SQL for MySQL. Create the target schema as utf8mb4.

More guides for Access ↔ MySQL

Next steps: configure, validate, run

After connecting source and target, the remaining steps are the same for every database pair:

  • Configure migration options — pick tables, fields, indices, views.
  • Issue detection — the built-in checker flags integrity problems before migration starts.
  • Execute — commit the job, monitor progress, save the session for reuse.
  • Schedule and CLI — rerun saved sessions on a schedule or from the command line.
Open the full guide

Steps 3–5, software features, command-line mode, scheduler, and system requirements.

See all features