Oracle
SQLite

Oracle to SQLite Converter

Selected Oracle tables, keys, and rows in one SQLite file - exported once, or kept in step by a scheduled job.

Version
5.4.0
Release Date
Oct. 25, 2026
Size
70.4 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Turn selected Oracle tables into one portable SQLite file. DBConvert reads the Oracle schema, proposes a SQLite type for every column, then writes the tables, keys, indexes, and rows into the file.

  • Reads Oracle Database 11.2 and later, including Express Edition, over a host, port, and service name.
  • The Oracle client ships with the application; nothing else to install.
  • Runs on Windows as a desktop application.
  • The same download converts SQLite back into Oracle.

Prepare a reusable export job

Connections, tables, and mappings have their own screens. Return to any of them as you refine the job, without restarting the setup.

Connect to the schema

Connect as Normal, SYSDBA, or SYSOPER. Tables are read from one owner; left blank, that is the login, in upper case as Oracle stores it.

Limit the dataset

Select individual tables and apply row filters when the SQLite copy needs only part of the Oracle data.

Save the export

Keep the connection, selected tables, mappings, and output path together as a job, and run it again for the next copy.

Export once, or keep the SQLite copy in step

Both modes are part of the same DBConvert application.

One-time SQLite export

Create the selected tables in a new SQLite file and transfer their rows in one run. Test the file with the application that will read it before you hand it out.

Scheduled synchronization

A sync job carries only the rows inserted, updated, or deleted in Oracle since the last run. Before local edits go back to Oracle, decide which side owns them and review keys and conflict rules.

When a SQLite file is the right output

Data that travels with an application

Ship reference or customer data inside a desktop, mobile, or field application that has no connection to the Oracle server.

Snapshots, fixtures, and offline analysis

Give testers, analysts, or a demo a dataset of their own, without an Oracle account for each of them.

How Oracle types map to SQLite

DBConvert proposes the declarations below; you can change them per column. Primary keys, unique and plain indexes, and foreign keys are created with the tables.

In Oracle DBConvert default in SQLite What needs attention
NUMBER NUMBER(p) of up to 18 digits becomes SMALLINT, INT, or BIGINT. NUMBER(p,s) becomes NUMERIC(p,s), and a bare NUMBER stays an unbounded NUMERIC. Numbers stay numbers, but SQLite keeps 19 digits of a whole number and 15 of a fraction. Every column that can hold more is named in the log.
FLOAT, BINARY_DOUBLE, BINARY_FLOAT FLOAT and BINARY_DOUBLE become DOUBLE; BINARY_FLOAT becomes REAL. Both are stored as SQLite's 8-byte floating point, so values arrive unchanged.
Character types, CLOB, LONG VARCHAR2, NVARCHAR2, and CHAR keep their length as VARCHAR, NVARCHAR, and CHAR; NCHAR becomes NVARCHAR. CLOB, NCLOB, and LONG become TEXT. SQLite does not enforce declared lengths. CHAR values keep Oracle's trailing spaces.
DATE, TIMESTAMP, INTERVAL DATE becomes DATETIME and every TIMESTAMP becomes TIMESTAMP, stored as text with its fractional seconds. INTERVAL types become VARCHAR(64). A time-zone timestamp is written as its UTC instant; the original offset is not kept. Test how your SQLite driver reads date text.
BLOB, RAW, LONG RAW BLOB, byte for byte. Large payloads make a large file. Filter rows if the copy only needs part of them.
Identity columns and defaults An identity key becomes an INTEGER primary key with its values kept. Literal defaults are kept, and SYSDATE becomes CURRENT_TIMESTAMP. Other function defaults, such as SYS_GUID(), are dropped. New SQLite inserts continue above the highest copied key.

If the application relies on foreign keys, enable SQLite foreign-key enforcement on each connection.

PL/SQL and Oracle security stay in Oracle

The export covers tables with their columns, indexes, and foreign keys. Packages, procedures, triggers, views, scheduler jobs, users, and grants are not converted. SQLite has no stored-procedure layer or user model, so that logic moves into the application.

Supported versions and services

Oracle

  • Oracle Database 11.2 and later
  • Oracle client included in the installer

SQLite

  • SQLite 3.0 and later

How to migrate Oracle to SQLite

1

Setup: connect Oracle 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.

The Setup step in DBConvert: the mode, the Oracle source and SQLite destination side by side, and the job name

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

The Setup step in Sync mode for Oracle to SQLite: how changes are detected and the direction

Oracle source

Enter the host, port, and service name, such as ORCL or XEPDB1. Leave the owner blank to read the login's own tables. See Oracle connection settings and the Oracle troubleshooting guide.

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 Oracle 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.

Tables and mapping for Oracle to SQLite: the table list and one table's columns with their SQLite 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 Oracle to SQLite 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 Oracle data into SQLite

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

Windows Windows 10 or later · 70.4 MB