Moneydance to QuickBooks: Convert Moneydance QIF Exports to QBO for QuickBooks Online and Desktop

Open your Moneydance file, choose File, then Export, and select the QIF option. You pick a date range (choose all dates for a full history) and decide whether to write every account into one file or one file per account. Choose one file per account. Destination programs, QuickBooks included, import into a single account, so a merged file piles unrelated registers into one place.

Moneydance also exports to CSV, which is useful for a spreadsheet review but weaker as an import format because it drops the structure importers rely on. If your destination is QuickBooks, QIF is the export you want, then convert it. If your destination is a workpaper, either works and the QIF to Excel converter produces a cleaner sheet than the raw CSV.

No. QuickBooks cannot open a Moneydance data file, and it cannot read QIF either. QuickBooks Online and Desktop accept QBO (Web Connect), QFX, OFX and CSV for bank transaction imports, and nothing else. So the working path is Moneydance to QIF to QBO, with the conversion happening in between.

People often try CSV first because Moneydance offers it and QuickBooks accepts it. It works, and then it costs you an hour. You map columns by hand for every file, QuickBooks has no way to tell a re-import from new activity so overlapping ranges duplicate, and date columns get misread. QBO removes all three problems because it carries a bank feed structure and a unique ID per transaction.

QIF carries the category on the L line and split detail on S, E and dollar lines, so the information leaves Moneydance intact. What happens next depends on the output format. Spreadsheet outputs (XLSX and CSV) show every split line with its own category and amount. QBO and OFX are bank feed formats, so they carry the transaction, the date, the amount and the description, and you categorize inside QuickBooks.

That is not a loss so much as a difference in what the formats are for. QuickBooks wants to apply its own chart of accounts and its own rules to incoming transactions, and Moneydance categories rarely map cleanly to a US chart of accounts anyway. Import as a feed, then let QuickBooks bank rules do the categorization once instead of arguing with imported labels.

Go to Transactions, then Bank transactions, choose Upload from file, select the .qbo, and pick the account it belongs to. The transactions appear in the For Review tab exactly like a live bank feed. Review, categorize, and add them. QuickBooks Online enforces a 350 KB limit per file, which is thousands of transactions, so split by year if a long history trips it.

In QuickBooks Desktop the equivalent is File, then Utilities, then Import, then Web Connect Files. Both routes are covered step by step on the QIF to QuickBooks Online and QIF to QuickBooks Desktop pages, including what to do when QuickBooks refuses a file.

Bring the current fiscal year and the prior one into QuickBooks as live transactions, and keep older years as spreadsheet archives. A QuickBooks Online register loaded with a decade of personal transactions is slow to work in and makes reports harder to read. The archive still answers any question that comes up later.

If an accountant is doing catch-up bookkeeping, ask which periods they need before you import anything. Sometimes the answer is one specific year, and importing everything creates work they will have to undo. Converting is cheap, undoing an import is not.

Investment registers export to QIF fine, but they do not convert usefully to QBO or OFX, because those are banking formats with no field for share quantity, price per share, or cost basis. Convert investment accounts to Excel instead, where every field survives and a preparer can rebuild basis from real rows.

QuickBooks is not built to track a brokerage account in the first place. The common and correct setup is bank and credit card activity live in QuickBooks, investment history archived in a spreadsheet, and the year end broker statements filed alongside it.

Compare three numbers: the transaction count in the Moneydance register for the date range, the count in the converted output, and the ending balance. If all three agree, nothing was dropped. QIF has no built in warning when a date range clipped early, so the check has to be yours rather than the software's.

The converter reconciles the parsed transactions against the file's own totals and shows the result before you download, which is where a mangled split or a misread apostrophe year becomes visible. Catching it there costs a minute. Catching it after a QuickBooks import costs an afternoon, because now you are deleting transactions out of a register instead of re-running an export.