Free online ACCDB to SQLITE converter

A program, mobile app, or embedded device may require a SQLite database instead of a Microsoft Access file. Converting the data can also produce a portable database that does not require Microsoft Access or the Access Database Engine.

What the ACCDB format is

.accdb is the native database format created by Microsoft Access 2007 and later. An ACCDB file can contain tables, relationships, indexes, queries, forms, reports, macros, attachments, and Access-specific field types.

Microsoft Access opens and manages ACCDB files. Windows applications can access them through the Microsoft Access Database Engine, ODBC, or compatible drivers such as UCanAccess. ACCDB is used for desktop databases, departmental business tools, local reporting, and small line-of-business applications.

What the SQLITE format is

.sqlite, .sqlite3, and sometimes .db are filename extensions commonly used for SQLite database files. SQLite is an embedded relational database engine: tables, indexes, views, triggers, and schema metadata are stored in one portable file without a separate database server.

SQLite is supported on Windows, macOS, Linux, Android, and iOS through native libraries and application drivers. It is suitable for local application data, mobile and device software, test databases, reporting, distribution, and archival copies. SQLite has no server accounts or network service, and its dynamic type system differs from Access's type system.

Convert the file without installing software

You can convert an ACCDB file for free on 101convert.com without installing desktop software. Select the ACCDB input format, upload a file such as database.accdb, choose SQLITE as the output format, start the conversion, and download the resulting database file.

Open the output with a SQLite-compatible application and verify table names, row counts, primary keys, dates, and important values. Do not upload confidential or regulated data unless the service's handling and retention policies meet your requirements. An online conversion normally targets database tables and values; Access forms, reports, VBA, permissions, and other application features may not be preserved.

Transfer the database with desktop software

DBeaver can transfer selected tables when you need to inspect the source schema and choose the destination mappings. The procedure is:

1. Install DBeaver and configure its UCanAccess JDBC driver, including the driver dependencies requested by DBeaver. UCanAccess can read many ACCDB files without Microsoft Access.
2. Create an Access connection and select database.accdb. Test the connection and confirm that the required user tables are visible.
3. Install or select DBeaver's SQLite JDBC driver and create a second connection pointing to a new file such as database.sqlite.
4. In the Access connection, select the required tables and choose Tools → Data Transfer or the equivalent export command.
5. Set the SQLite connection as the target, enable table creation, review the column mappings, and run the transfer. Select options for data, primary keys, indexes, and foreign keys where DBeaver exposes them.
6. Open the destination database and verify row counts, column types, primary keys, indexes, foreign-key definitions, nullability, and representative values. Recreate any missing schema objects manually.

Driver configuration varies by DBeaver edition and operating system. If the Access driver cannot open the file, use Microsoft Access or another compatible Access reader to export the required tables first.

Use CSV as an intermediate format

When direct database transfer is unavailable, open the ACCDB file in Microsoft Access and export each required table through External Data → Text File. Choose a delimited text format and retain column headers. Import the CSV files into SQLite with a SQLite management application or the SQLite command-line tool.

For the command-line tool, create the destination schema first, then use commands such as .mode csv, .headers on, and .import database.csv table_name. Check the delimiter, quote character, encoding, and header handling before importing. CSV transfers values only; they do not preserve relationships, indexes, queries, forms, reports, macros, permissions, or Access-specific field behavior.

Compatibility limitations

• Ordinary tables and scalar values usually transfer more reliably than Access Attachment, multivalue, hyperlink, calculated, and other complex fields. Export complex values into a simpler representation when necessary.
• Access AutoNumber fields commonly map to SQLite integer columns. To obtain SQLite rowid-style automatic numbering, the destination column must normally be defined as INTEGER PRIMARY KEY; a generic integer column does not provide the same behavior.
• Access Yes/No values commonly become SQLite integer values such as 0 and 1. Confirm the expected representation in the destination application.
• SQLite has no dedicated date/time storage class. Dates may be stored as ISO 8601 text, Unix timestamps, or numeric values, so check formatting, timezone assumptions, and fractional-second precision.
• Access queries, forms, reports, VBA modules, macros, user permissions, linked-table definitions, and navigation objects do not become equivalent SQLite objects. Rebuild required application logic separately.
• Password-protected or encrypted ACCDB files require valid credentials and a compatible reader. A linked table may contain only a connection to data stored elsewhere; obtain access to the linked source before converting.
• SQLite foreign-key enforcement, locking, transactions, and concurrent-write behavior differ from Microsoft Access. Enable and test foreign keys with PRAGMA foreign_keys = ON;, and test the converted database with the application that will write to it.