What I'm asking for
A non-interactive export entry point for Quicken Classic for Windows: one command that writes the same file that File
File Export > Quicken Interchange Format (.QIF) File... produces today, without a human clicking through the dialog.
Something as simple as:
qw.exe --file="C:\Users\me\Documents\Quicken\home.qdf" --export-qif="C:\Users\me\Exports\home.QIF" --accounts=all
--from=1992-01-01 --quiet --exit-when-done
with a meaningful exit code (0 = written, non-zero = failed) and no dialogs. QXF or CSV would serve equally well; the
format matters less than the fact that no UI interaction is required.
Why
I keep more than 30 years of records in Quicken and analyse them with my own tooling: long-run category trends,
retirement cash-flow work, year-over-year comparisons. Everything downstream of the export is automated. The export
itself is the one step that cannot be, because it exists only as a sequence of clicks.
The data file is encrypted, which is correct and I don't want that changed. But it also means Quicken itself is the
only program that can read my data, and the only way to get data out is a person operating a dialog. That single
manual step gates everything else.
Why the existing workarounds don't cover it
Task Scheduler can launch Quicken, but it cannot drive the export dialog. Launching the program isn't the missing
piece; a non-interactive export is.
Scheduled Updates downloads transactions into Quicken. This is about getting data out.
UI automation that sends synthetic clicks is brittle, breaks with every layout change, and nobody should have to
script a GUI to read their own records.
Why this should be inexpensive to build
The export engine already exists. This asks for a second way to invoke it, not a new feature. It is read-only, so
there is no write path into the data file and the risk surface is small. No new file format, no cloud dependency, no
UI work.
Security can stay exactly as it is: prompt for the file password on the console, or read it from Windows Credential
Manager. I am not asking to weaken file encryption.
What this is not
I know a broader "run Quicken on a schedule" idea was marked Not Planned. This is deliberately smaller. I will handle
scheduling myself with Task Scheduler. All I need from Quicken is an export that doesn't require a person at the
keyboard.
Who else benefits
Anyone doing their own analysis in Excel, Python or a database; anyone keeping an independent archive against future
file-format changes; and anyone wanting to connect Quicken data to AI tools, which is the direction the "Claude
Connector for Quicken" idea in this category points at. A scriptable export is the smallest building block that makes
all of that possible.
