SQL Server
Access

SQL Server to Access Converter

Selected tables into a new Access file, with editable mappings for a one-time export or a scheduled refresh.

Version
5.6.0
Release Date
Nov. 3, 2026
Size
125.6 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Copy SQL Server tables into a Microsoft Access file. DBConvert creates the .accdb or .mdb file, proposes an Access type for every column, and transfers the rows through a live connection to the server.

  • Reads SQL Server, SQL Server Express, Azure SQL Database, or Amazon RDS for SQL Server.
  • Writes a new .accdb file, or a .mdb in Access 2000 format, optionally protected by a database password.
  • Runs on Windows as a desktop application.
  • The same download converts Access into SQL Server.

Prepare a repeatable Access export

Connections, tables, and mappings stay on separate screens as you prepare the job.

Limit the source data

Select tables and add per-table row filters, such as a date range or one branch. An Access file stops at 2 GB, so a large server database usually needs a subset.

Adjust the target schema

Review the proposed Access types and edit column names and types before loading. Columns Access has no type for, and values that lose precision, are named in the log.

Save the job

Reuse saved connections and keep the tables, mappings, and options together, so the next export is one run instead of a new setup.

Export once, or keep the Access file in step with SQL Server

Conversion and synchronization are modes of one application.

One-time conversion

Build a self-contained Access file from the selected tables: an offline copy, a local reporting database, or data for an Access application.

Scheduled synchronization

Refresh the Access file on a schedule with the inserts, updates, and deletes made in SQL Server. The comparison follows what Access stores, so an unchanged row is not copied again. See how synchronization works.

What the Access side needs

  • The 64-bit Microsoft Access Database Engine on the same computer. It is a free Microsoft download; if it is missing, Connect says so and links to it.
  • A database password is supported. User-level workgroup security (.mdw files) is not.

How SQL Server types map to Access

Access has fewer types than SQL Server. Exact numbers stay exact; where Access has no equivalent, the value arrives in a form it can hold and the column is named in the log.

In SQL Server DBConvert default in Access What to know
IDENTITY keys AutoNumber (Long Integer) Key values arrive unchanged. A key above 2,147,483,647 does not fit and is refused, naming the table.
bigint, decimal, numeric Decimal; bigint becomes Decimal(19,0) Access Decimal stops at 28 digits. A wider column keeps every integer digit and loses fraction digits; a value with too many integer digits is refused, naming table and column.
money, smallmoney Currency Exact, including the money maximum.
Text types Short Text up to its length; longer and (max) columns become Long Text Unicode text and long values arrive whole.
datetime2, datetimeoffset, time Date/Time Access stores whole seconds, so fractions are dropped. A datetimeoffset is stored as its UTC time, a time on Access's day zero.
bit, uniqueidentifier Yes/No, Replication ID Yes/No has no NULL, so a NULL bit becomes No.
varbinary(max), image OLE Object Copied byte for byte.
xml, geography, geometry, hierarchyid, sql_variant, rowversion Long Text holding the value as text; rowversion is not created Access has no such types. Each column is named in the log.

T-SQL code stays in SQL Server

The export covers tables and their rows. Views, stored procedures, functions, and triggers do not convert to Access; rebuild the logic an Access application needs as Access queries.

Supported versions and services

SQL Server

  • 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

Access

  • MS Access .accdb, and .mdb in Access 2000 format or later
  • Database password; the 64-bit Microsoft Access Database Engine is required

How to migrate SQL Server to Access

1

Setup: connect SQL Server and Access

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

The Setup step in DBConvert: the mode, the SQL Server source and Access destination side by side, and the job name

Sync keeps an existing Access database up to date with SQL Server: each run carries only the inserts, updates and deletes since the last one.

The Setup step in Sync mode for SQL Server to Access: how changes are detected and the direction

SQL Server source

Use TCP/IP or Named Pipes. Azure SQL needs SQL authentication, SSL, and outbound TCP 1433.

Access target

Choose a path for the target .accdb or .mdb file, and a database password if the file should have one. The 64-bit Microsoft Access Database Engine must be installed.

2

Tables & mapping: see every Access type before a row moves

Pick the tables, then open one: each SQL Server column shows the Access type it becomes. Change a type or a name in place; the line at the bottom names anything that would fail.

Tables and mapping for SQL Server to Access: the table list and one table's columns with their Access types
3

Execution: start it, and the job is saved

Review what the run will do, start it, and read the log as it goes. The job stays in the list to run again or put on a schedule.

A finished SQL Server to Access conversion: the summary and the operation log

Every option, in the guide

Naming rules, table options, row filters, scheduling and the command line work the same for every database pair, so they live in one place.

Move SQL Server data into Access

Download the current build and run the first job against your own database.

Windows Windows 10 or later · 125.6 MB