Access
SQL Server

Access to SQL Server Converter

Move Access .mdb and .accdb files into a SQL Server backend with schema conversion, type mapping, query-to-view handling, saved sessions, and optional staged synchronization.

Converting Access to SQL Server means moving an .mdb or .accdb database into a shared SQL Server backend, not just exporting rows to a generic SQL file.

The hard part is not the row copy; it is preserving the Access relationships, indexes, field types, and supported queries while deciding what happens to the forms, reports, macros, and VBA that lived in the same file.

Which DBConvert tool fits?

Use Microsoft's free SSMA as a baseline check; use DBConvert products when you need a controlled desktop workflow or synchronization.

DBConvert for Access → SQL Server

One-time conversion with DBConvert's mapping UI, saved sessions, query conversion options, and direct targets including SQL Server, SQL Server Express, Azure SQL, and Amazon RDS for SQL Server.

DBSync for Access ↔ SQL Server

Repeat synchronization when the Access database must remain in use while SQL Server becomes the shared backend for new apps, reports, or a phased cutover; see database synchronization concepts for the underlying workflow.

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

How DBConvert handles the Access → SQL Server differences

Access is both a database file and an application platform; SQL Server is only the backend. DBConvert moves the database side with sensible defaults that you can review or override per table; the application objects stay in Access or are rebuilt outside the migration. See the Access front-end / SQL Server backend guide for the application split.

Access-specific field types

Access type SQL Server type
AutoNumberIDENTITY
Yes/Nobit
Memo / Long Textnvarchar(max)
Hyperlinknvarchar(max)
Currencymoney
OLE Object / Attachmentvarbinary(max)

Lookup fields keep their underlying value type; the lookup display is an Access UI concept and lives in the front end.

Access queries → SQL Server views

Translates supported Access SELECT and UNION queries into SQL Server views during the migration. Queries that call VBA functions, form controls, Access-only functions, or local tables are not translated - rebuild those in SQL Server views, stored procedures, or in the new application layer.

Linked-table-ready output

Creates target tables with primary keys preserved from Access - required for an Access front end to detect changes through ODBC linked tables. Adding a rowversion column on heavily-edited tables is a wizard option that makes Access linked-table updates conflict-safe.

Security and workgroups

Reads .mdb files that use Access WorkGroups when those credentials are supplied at the source step; user-level permissions do not map automatically into SQL Server logins, roles, or application security - redesign the security model on the SQL Server side as part of the cutover.

Forms, reports, macros, VBA - out of scope

These are part of the Access application, not the database. DBConvert's migration covers tables (with their fields, types, defaults, and indexes), views, and foreign keys. Forms and reports continue to work as a front end against linked SQL Server tables, or are rebuilt in a web / .NET / BI front end as a separate workstream.

Supported versions

  • MS Access .mdb (Jet) and .accdb (ACE) files
  • WorkGroups credentials and linked tables
  • SQL Server 2008–2022, including Express editions
  • Azure SQL Database and Amazon RDS for SQL Server
  • SQL Server schemas (dbo, custom schemas)
  • Windows authentication or SQL authentication

Supported in this path

Source Access
Target SQL Server
Microsoft Access Microsoft SQL Server SQL Server Express Azure SQL Database Amazon RDS for SQL Server
Access

All Access Tools

Other directions and pairs
SQL Server

All SQL Server Tools

Migration & sync options

Reverse Conversion

SQL Server to Access

Using Access to SQL Server 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 SQL Server destination database

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

Connect to SQL Server target database from DBConvert

SQL Server target

Connect by TCP/IP or Named Pipes, use Azure SQL, or configure Amazon RDS for SQL Server.

More guides for Access ↔ SQL Server

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