Convert OFX to SQL Online

Paste an OFX table below, edit it if you need to, and get SQL back. The conversion runs in your browser, so nothing is uploaded, there is no size limit and there is no signup.

From

From a page

The only part of this site that uses a server. The address is sent to it so the page can be fetched, because a browser is not allowed to fetch someone else's page itself. Your own files are never involved.

Nothing here is uploaded. The parsing happens on this page.

Edit

Paste or upload something above and it will appear here.

ToDataMarkupDocumentsCodeSchemasImages

Header rowDetect numbersTableStatementsRows per statement

The output will appear here once there is a table to convert.

What OFX is

OFX is the format behind the Download Transactions button on your bank's website. Version 1 is SGML, where a leaf element has an opening tag and no closing one. Version 2 is real XML. QFX is Intuit's variant of the same thing with a few extra tags, which is why a .qfx file opens in Quicken and is refused by software that only knows plain OFX.

Retail banks, credit card issuers and brokerages, because it is what Quicken and Microsoft Money asked for and the industry standardised on.

What SQL is

SQL here means the statements that move a table into a database: INSERT INTO with a VALUES list, and optionally the CREATE TABLE that defines the columns.

Anyone seeding a database, moving a spreadsheet into an application, or writing a migration.

What changes when you convert OFX to SQL

Each STMTTRN block becomes a row: date, amount, type, payee, memo, cheque number and the bank's own transaction id. The account number and currency come from the statement header and are added to every row, so a file merged with another still says which account it came from. Both the SGML and the XML flavour are read the same way.

String values are escaped by doubling any single quote. Statements are written in batches so a large table does not become one statement megabytes long, which many clients refuse. Ask for CREATE TABLE as well and column types are inferred: a column stays INT until a value does not fit, then widens to DECIMAL, then to VARCHAR.

What carries over from OFX to SQL

One property of the OFX has no home in SQL, and it is worth knowing which before you convert.

OFX can hold a value that is itself a list or an object. SQL has only flat cells, so nested values are flattened into one cell rather than being spread across columns.

SQL marks its header cells differently from its data cells, so the first row is written with that marker.

The result can be read a record at a time, and appended to by adding to the end of it. That is worth having for a table too large to hold in memory, and it means a SQL file that is cut off part way through still gives you every record before the cut.

Both formats record types, so numbers, booleans and nulls survive as themselves rather than as text.

A worked example

Three rows of staff data, with an identifier that has a leading zero, a value containing a comma, a value containing quotes and one blank cell. Those are the four places formats disagree, so they are the four places to look.

OFX in

OFXHEADER:100
DATA:OFXSGML
VERSION:102

<OFX>
<BANKMSGSRSV1><STMTTRNRS><STMTRS>
<CURDEF>GBP
<BANKACCTFROM><ACCTID>60161331926819</ACCTID></BANKACCTFROM>
<BANKTRANLIST>
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260115120000[0:GMT]
<TRNAMT>-42.50
<FITID>20260115001
<CHECKNUM>1043
<NAME>Greenfield Grocers
<MEMO>Weekly shop
</STMTTRN>
<STMTTRN>
<TRNTYPE>CREDIT
<DTPOSTED>20260116000000[0:GMT]
<TRNAMT>1850.00
<FITID>20260116001
<NAME>Acme Ltd
<MEMO>January salary
</STMTTRN>
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20260118000000[0:GMT]
<TRNAMT>-9.99
<FITID>20260118001
<NAME>Streaming service
</STMTTRN>
</BANKTRANLIST>
</STMTRS></STMTTRNRS></BANKMSGSRSV1>
</OFX>

SQL out

INSERT INTO `staff` (`id`, `name`, `role`, `started`, `hours`) VALUES
  ('007', 'Halima Yusuf', 'Analyst, data', '2024-03-15', '38.5'),
  ('012', 'Jonah "Jo" Pryce', 'Engineer', '2025-11-02', NULL),
  ('104', 'Wei Chen', 'Manager', '2023-06-30', '40');

Questions

How do I convert OFX to SQL?

Paste your OFX into the box above or drop the file onto it. Check the table in the grid, then copy or download the SQL from the output panel. It takes one step and the data never leaves your browser.

What is the difference between OFX and QFX?

QFX is OFX with Intuit-specific tags added, most importantly a bank identifier that Quicken uses to decide whether it will accept the file. The transaction data is identical, which is why anything that reads OFX reads QFX. Banks often charge for the QFX version of the same download.

Are the generated INSERT statements safe to run?

Quotes in your data are escaped, so the statements are syntactically correct. They are not parameterised, which is fine for a one-off import you are running yourself and not fine as a pattern for application code that takes user input.

What happens to nested values?

SQL has no nested cell, so a list or object inside a OFX value is flattened into a single cell rather than expanded into extra columns. Split it before converting if the parts need to be separate.

Is there a limit on file size?

No. The work happens on your own machine, so the limit is your machine's memory rather than an upload cap. A file with tens of thousands of rows converts in a second or two.

Is my data uploaded anywhere?

No. The parsing and generating are done by JavaScript running on this page. You can watch the network tab while you convert and see that nothing is sent.