XML to SQL: turning a data export into INSERT statements
By the Converterzilla Team
We build privacy-first PDF and image tools that run entirely in your browser. Our team has shipped JavaScript file-processing apps used by thousands every day, and we write here about the libraries, trade-offs and patterns we use.
A common one-off task: someone hands you an XML export — a legacy system dump, a partner data feed, a report — and you need it in a database table, right now, without standing up a full ETL pipeline for a task you'll do once. Generating a batch of INSERT statements directly from the XML is often the fastest path.
How the conversion works
The same repeating-element detection used for XML-to-CSV applies here: find the element that occurs once per record, flatten its nested fields into column names, and emit one INSERT INTO table (col1, col2, ...) VALUES (...); statement per occurrence. The column list comes from the union of fields seen across all records, exactly like the CSV case — so a field that's only present on some rows still gets a consistent column position across every statement, with NULL where it was absent.
Three things worth checking before you run the output
- The table name and column names are valid identifiers for your database. Element and attribute names from XML don't always make legal SQL identifiers — spaces, leading digits, and reserved words all need handling, and different databases have different rules about what needs quoting.
- String values are properly escaped, not just quoted. A value containing a single quote — a name like
O'Brien— needs the quote itself escaped within the SQL string literal, not just wrapped in outer quotes, or the statement breaks (or worse, becomes a SQL injection vector if this is ever done with untrusted input server-side rather than as a one-off local script). - Numeric-looking strings that should stay strings. A product code or phone number that's all digits can get inferred as a SQL numeric literal, silently dropping a meaningful leading zero. Spot-check a few generated statements against the source XML before running the batch.
Our XML to SQL converter lets you set the target table name, flattens nested fields into columns, and quotes/escapes string values automatically — all generated locally in your browser. Review the generated statements against a few source records before running them against a real database, same as you would with any generated SQL.