Withdata FileToDB - One-stop solution for importing Excel data to SQLite: local, cloud, batch, automation & more
Excel to SQLite and import Excel into SQLite describe the same import. Need the other direction? SQLite to Excel.
Four steps, the same in the GUI and in the command line. Each one is also where an import usually goes wrong.
📷 Connect to the SQLite file first
Eight source shapes, all from the same dialog. The first two take one source, the next four take many, the last two decide what happens to rows that already exist.
One source
The everyday case: one sheet into one table. Two details decide whether it lands cleanly — whether the first row is a header or data, and the target type of each column. SQLite keeps text and numbers in the same column, so the type is chosen per column, never per row.
Point the wizard at an online workbook — OneDrive, SharePoint or a published Google Sheets URL. It reads the file over HTTPS and never saves a copy locally, which is what you want when the sheet belongs to someone else and the laptop should not keep a snapshot of it.
Many sources
Monthly exports rarely arrive as a single file. Give the wizard a folder and it appends every workbook into the same table: the first file defines the columns, the rest are matched by header name. Files whose header does not match are reported, not silently dropped.
When each file belongs in its own table — one workbook per customer, one per month — the batch mode creates or fills a table per file and takes the name from the file name. Run it once as a session, then schedule it.
Identical sheets — one per week, one per region — stack into a single table: same columns, rows appended in sheet order. If the sheets differ in structure, use the next case instead.
The mirror image: every sheet becomes a table, named after the sheet. This is how a multi-sheet workbook maps onto a relational schema without hand-writing eight CREATE TABLE statements.
Existing rows
Update only touches rows the table already has: match on the key column, overwrite the other fields, leave the rest alone. Re-importing a corrected sheet therefore fixes records instead of duplicating them.
Upsert is the same match with one difference: rows that are not in the table yet are inserted instead of ignored. That makes it the right mode for a list that keeps growing — orders, tickets, inventory — imported on a schedule.
Every import above runs unattended: save the configuration as a session, generate a .bat or .sh script from it, and let Windows Task Scheduler or Crontab run it hourly, daily or weekly.
Check the row count against the sheet before trusting the summary report:
SELECT COUNT(*) FROM customers;
SELECT name FROM sqlite_master WHERE type = 'table' ORDER BY name;
If the count is lower than expected, read the rejected-rows report first — a type mismatch or a header that did not match is the usual cause, and both are written to the run log.
No, FileToDB reads Excel files natively without Microsoft Excel.
All processing runs locally. No data is uploaded to any server.
Yes, full support for Windows, Linux, and macOS.
FileToDB supports SQLite 3.0+ (all modern versions).
Yes — save the session, generate the script, schedule it (see Run it on a schedule).
Both are read directly; the sheet picker and the column mapping work the same way for either format.
Yes, when the sheets share the same columns — rows are appended in sheet order (see Several sheets into one table).
Free trial available | Full tutorials | 24/7 support
$75 one-time · volume discounts to $55 · 30-day money-back · pricing & licence terms
Download Withdata FileToDB