LOCAL DATABASE CONVERTER / EXCEL TO SQL INSERT

Excel to SQL INSERT

Generate reviewable SQL INSERT statements from one XLSX worksheet using stored values and no database connection.

Processed in this browserOne unencrypted .xlsx file up to 15 MB and 50 worksheets. The selected sheet supports one header row plus 50,000 records, 200 columns, 1,000,000 cells, and 20 MB SQL output.

Step 1 / source

Choose the source

XLSX - one SQL script

Drop one file here

Choose the one xlsx worksheet you want to turn into escaped sql insert script.

Browse filesChecking publication status...

Step 2 / choices

Choose worksheet and SQL rules

Select the tab, destination table, dialect, empty-cell handling, and statement batch size.

Worksheet numberEnter the one-based workbook tab position to convert, from 1 to 50.Destination tableEnter one safe table identifier or a schema-qualified name such as public.customers.SQL dialectChoose identifier quoting and boolean literals for the database that will review the script.Empty worksheet cellsChoose whether empty cells become SQL NULL or an empty string literal.Rows per INSERTSplit the output into statements containing from 1 to 1,000 rows each.

Step 3 / convertCreates a separately named result and never writes into the source file.

After success, the selected source is cleared from this workspace.

No file upload

This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.

Original stays unchanged

The converter creates a separately named output. It never writes back into the source file.

Bounded work

One unencrypted .xlsx file up to 15 MB and 50 worksheets. The selected sheet supports one header row plus 50,000 records, 200 columns, 1,000,000 cells, and 20 MB SQL output.

Plain-language method

How Excel to SQL INSERT works

The browser reads stored worksheet values without recalculating formulas, uses row one as normalized columns, quotes identifiers, escapes every non-empty cell as SQL text, maps blanks by your rule, batches INSERT statements, and never contacts a database.

01
Choose a valid source
Use a compact worksheet with column names in row one. Hidden sheets count in one-based tab order; formula results must be saved in the workbook.
02
Review the conversion choices
Choose the exact destination dialect. Empty-to-NULL is usually appropriate for missing values, but not when empty text is meaningful.
03
Inspect the separate result
The result ends in _nirmion_tools.sql. Review it against the destination schema and execute only in an authorised database client.

Useful when

Practical jobs this tool handles

Prepare a controlled spreadsheet migration.
Create seed data from a reviewed worksheet.
Hand a deterministic script to a DBA for validation.

Before converting

Check the source and destination rules

Recalculate and save the workbook.
Verify worksheet, table, and columns.
Test the script inside a rollback-capable transaction.

Know the boundary

Know what the destination format cannot keep

Excel formatting and displayed types are not a database schema. Values are emitted conservatively as strings or NULL; constraints, numeric conversion, dates, conflicts, and transactions require destination review.

Quick answers

Questions before you convert

The conversion contract is deliberately explicit.

Are formulas recalculated?

No. Only saved results are read.

Are numbers emitted without quotes?

Worksheet values are conservatively written as strings because display formatting can hide identifiers or precision.

Does this modify the database?

No. It creates SQL text only.