Access
SQLite

Access to SQLite Converter

Tables, indexes, foreign keys, and rows in one SQLite file - built once, or refreshed from Access on a schedule.

Version
6.0.0
Release Date
Nov. 19, 2026
Size
35.2 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

DBConvert Studio adds an optional AI assistant that explains a run's errors, writes the SELECT of a table from SQL from your words, and tells what a plan does to your tables. It does nothing until you pick an agent, and it never sees your passwords.

See the assistant

Turn a Microsoft Access database into a single SQLite file without writing the schema by hand. DBConvert reads the Access file, proposes a SQLite type for every field, and creates the tables, indexes, and foreign keys before copying the rows.

  • Reads .accdb and .mdb files, including files protected with a database password.
  • Writes a SQLite database file at the path you choose.
  • Runs on Windows as a desktop application.
  • The same download converts SQLite back into Access.

Choose what goes into the SQLite file

Connections, table selections, and mappings stay on screens you can return to while you prepare the file.

Select the tables

Pick the tables to copy and add a Table from SQL when only part of a table belongs in the file.

Review the types

See the SQLite type proposed for each field and change it before the run. Fields the copy cannot carry as they are, such as Attachment fields, are named in the log.

Save the job

Keep the connections, table selection, and options in a job, and run it again when the Access data changes.

Build the file once, or keep it in step with Access

Conversion and synchronization are modes of one DBConvert application.

One-time conversion

Create the SQLite file with its schema and rows. Open it in the application that will use it and check the data before you retire the Access file.

Scheduled synchronization

Keep Access in use and refresh the SQLite copy with the inserts, updates, and deletes made since the last run. A second job sends SQLite changes back into Access. See how synchronization works.

When a SQLite file is the right target

Data without Access installed

A SQLite file opens through the SQLite library on Windows, Linux, macOS, and mobile platforms. The machines that read it need no Access or Office installation.

An embedded or offline copy

Ship the data inside an application, a mobile app, or a test fixture as one file, and rebuild it from Access when the source changes.

What the Access side needs

DBConvert reads Access files through Microsoft's Access Database Engine. DBConvert adds it if it is missing.

  • DBConvert adds Microsoft's 64-bit Access Database Engine if it is missing. If a 32-bit Office blocks it, Connect says so and links to Microsoft's download.
  • A file in Access 2000 format or later. Access 97 files cannot be read; open one in Access and save it in a newer format first.
  • A database password is supported. Workgroup security (.mdw files) is not.

How Access fields map to SQLite

SQLite stores a number as a 64-bit integer or a double. Where that would lose digits, DBConvert stores the value as text instead.

Scroll sideways to see all columns.

In Access DBConvert default in SQLite What needs attention
Currency, Decimal A Decimal of up to 15 digits becomes NUMERIC(p,s). Currency and wider Decimals become TEXT holding every digit. SQLite has no exact decimal type. An application doing money arithmetic should read the text value, not a double.
AutoNumber INTEGER PRIMARY KEY AUTOINCREMENT, with the existing key values. SQLite continues numbering after the highest copied value.
Date/Time, Yes/No Dates are ISO 8601 text, such as 2026-01-15 13:45:56. Yes/No is stored as 1 or 0. Dates before 1900 and up to the year 9999 arrive unchanged. SQLite date functions read this format.
Short Text, Long Text, Replication ID Short Text keeps its length as VARCHAR(n); Long Text becomes TEXT. A Replication ID is its {...} text. SQLite does not enforce text lengths, so the declared length is a description only.
OLE Object, Attachment, multi-value fields OLE Object and binary fields become BLOB, byte for byte. Attachment and multi-value fields become TEXT: the file names, or the values separated by ;. Attached files themselves are not copied. Each such field is named in the log.
Default values Now() becomes CURRENT_TIMESTAMP and Date() becomes CURRENT_DATE. Number and text defaults, including an empty string, are kept. A default built from another expression is dropped and named in the log.

Queries, forms, reports, macros, and VBA stay in Access

Supported field and table validation rules become SQLite CHECK constraints. The log names rules that cannot be transferred and rules that existing rows violate. See Validation rules.

DBConvert moves tables with their fields, indexes, and primary and foreign keys. Saved queries and the Access application objects are not converted; rebuild them in the application that will use the SQLite file.

Supported versions and services

Access

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

SQLite

  • SQLite 3.0 and later

How to migrate Access to SQLite

1

Setup: connect Access and SQLite

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.

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

Access source

Select the source .accdb or .mdb file and enter its database password if it has one. Reading it needs the 64-bit Microsoft Access Database Engine.

Look inside the Access file first

To see what an .mdb or .accdb file holds before converting it, open it in the free MDB and ACCDB Viewer: tables with their Access types, relationships as an ER diagram, saved queries and read-only SQL, in the browser, with no upload and no Access installed.

Open the MDB viewer · VS Code extension

SQLite target

Choose a writable path for the target SQLite database file.

2

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

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

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.

Validate the copy

With Validate after the run on, the destination is checked when the copy ends: schema, totals and rows. The window shows which tables, rows and columns differ.

How validation works

Every option, in the guide

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

Move Access data into SQLite

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

Windows Windows 10 or later · 35.2 MB