Download Fidelity Transactions Older Than 90 Days: How to Get Fidelity History Into Quicken

TL;DR: Fidelity's transaction download serves roughly 90 days of activity, and that limit is fixed. Nothing you do inside Quicken reaches further back, because the constraint is on Fidelity's side. To get older history you have two routes: download a file from Fidelity's website for a defined date range, which works in 90 day chunks and only for account types Fidelity serves that way, or take the monthly and quarterly PDF statements Fidelity keeps in its archive and convert them to QFX. The statement route is the only one that reaches back years, and it is the only route at all for accounts Fidelity will not export properly.

Why the 90 day limit exists and why reconnecting does not beat it

This is the part that wastes the most time. When someone notices in October that their Fidelity feed stopped in June, the instinct is to fix the connection, and the connection usually can be fixed. The download that follows still starts around July. People then deactivate and reactivate a second time, assuming they did it wrong, and get the same result.

The reason is that the 90 day window is a property of what Fidelity is willing to serve, not a setting in your file. A fresh connection asks Fidelity for available activity and Fidelity answers with about a quarter of it. That is standard across large US institutions rather than anything unusual to Fidelity, and it is the single biggest reason a Quicken register ends up with a hole in the middle of the year. Repairing a feed is forward looking. It does not backfill.

So the question worth asking is not how to make the connection reach further, but where else the same transactions exist in a form you can import. There are two places.

Route one: download a file from the Fidelity website

Fidelity's site lets you download activity for a date range rather than relying on whatever the live connection offers. Sign in at fidelity.com, go to Accounts and Trade, then Portfolio, then the activity or history view for the account you need. Set the date range, then choose a download format.

The practical catch is that the range picker is also bounded, and people report having to pull history in 90 day chunks rather than requesting a year in one go. That is tedious but workable: four downloads covers a year, and each file imports separately. If Quicken is the destination, choose the Quicken or QFX option rather than CSV. CSV is fine for a spreadsheet and a poor choice for Quicken, for reasons covered further down.

Where this route falls down is account coverage. Not every Fidelity account type exports the same way, and some accounts offer only CSV. Fidelity HSA accounts are the sharpest example of the wider problem: they are the account type Quicken cannot receive transactions from through the connection at all, which is covered in detail in the guide to Fidelity not downloading to Quicken. If the export you need is not offered, skip to route two.

Route two: convert the statement archive

Fidelity keeps monthly and quarterly statements available for far longer than it keeps downloadable activity. Those statements contain exactly the transactions the download screen has stopped serving, printed rather than structured. Converting them turns archived documents back into importable data.

The steps are short. Sign in at fidelity.com and go to Accounts and Trade, then Statements, and save the PDFs covering the period Quicken is missing, one file per statement period. Upload them to a converter and check the extracted transaction table against the printed one, particularly the first and last rows of each statement, since those are where a page break is most likely to have confused the extraction. Export as QFX. Then in Quicken use File, then File Import, then Web Connect File, choose the existing Fidelity account, and review the matches before accepting them.

Quicken flags likely duplicates during the import, which means a little date overlap between files is safe and is usually better than risking a one day gap between statement periods. Work oldest to newest so the running balance reads correctly as you go.

Pick QFX, not OFX, and not CSV

Two format mistakes account for most failed imports here, and both are easy to avoid once you know them.

The first is assuming OFX and QFX are interchangeable. They look almost identical inside, and they are not swappable. QFX is Intuit's licensed variant of OFX carrying extra identifiers, and Quicken's own import documentation lists QFX, QIF, CSV and QXF as the formats it accepts, with plain OFX absent from that list. Renaming a file from .ofx to .qfx does not help either, because what Quicken validates lives inside the file rather than in the extension. The QFX file format reference sets out which identifiers those are. If your destination is MS Money, GnuCash or Banktivity rather than Quicken, plain OFX is the right pick, since those programs read the open format.

The second mistake is reaching for CSV because it looks simplest. A CSV row carries no transaction identifier, so Quicken has nothing to match against and cannot detect that a transaction already exists. Import the same statement twice and you get every transaction twice, silently. QFX carries a unique identifier per transaction, which is precisely why it is the right format for backfilling history where some overlap with what is already in the register is likely.

What converts cleanly from a Fidelity statement, and what does not

Worth being straight about this before you start, because Fidelity statements can hold two quite different kinds of activity.

Cash movement converts cleanly. Contributions, distributions, dividends paid as cash, debit card spend, transfers, fees and bill payments are ordinary dated debits and credits, and they land in Quicken as normal transactions with the correct sign. That covers all of a Fidelity Cash Management Account, all of the cash side of an HSA, and the cash activity inside a brokerage account. For most people with a gap in their register, this is the entirety of what they are missing.

Trade level detail is a different shape. A buy or a sell carries a security, a share quantity, a price per share and a commission, and an investment transaction in Quicken is assembled from those fields rather than from one amount. If what you actually need is share lots rebuilt inside a brokerage account, read investment statement to OFX for how that data is structured before you rely on a converted file for it.

How far back do you actually need to go?

Before converting five years of statements, it is worth deciding what the history is for, because the answer changes how much work is justified.

If the goal is a clean reconciliation from a known good starting point, you only need to reach back to the last date the register was correct. That is often one or two quarters, not years. If the goal is tax substantiation, the relevant span is the tax years still open to amendment or audit, and the transactions that matter are the ones with a tax consequence rather than every line. Fidelity HSA holders tend to need the most, since qualified medical expenses have to be itemized and the account is exactly the one Fidelity will not download. Fidelity issues its own year end forms for the reportable items, so when you sit down to file the return itself the brokerage side is already summarized for you, and what the register adds is the detail behind those totals.

If the goal is a full historical record because you are consolidating years of accounts into one Quicken file, then yes, convert the archive. Just do it in statement order and reconcile as you go rather than importing everything and hoping the ending balance ties.

Common questions

Can I download more than 90 days of Fidelity transactions at once?

Not through the Quicken connection, and generally not in a single request from the website either. The workable approach is to request consecutive 90 day ranges from Fidelity's activity download screen, or to use the statement archive, which has no such limit because statements are documents rather than a query against recent activity.

Why does my Fidelity account reconnect successfully but still not show old transactions?

Because reconnecting only affects what arrives from now on. Fidelity serves about 90 days regardless of how recently the connection was established, so anything older than that window was never going to be included. The connection is working correctly; the data simply is not on offer.

How long does Fidelity keep statements available?

Considerably longer than the roughly 90 days of downloadable activity, which is what makes the statement archive useful here. Check the statements section of your account for the exact span available to you, since it varies by account type and how long the account has been open.

Will importing old statements create duplicate transactions in Quicken?

Not if you import QFX. Each transaction in a QFX file carries a unique identifier, so Quicken can recognize one it has already recorded and flag it rather than adding it again. This is the specific reason to avoid CSV for this job: a CSV import has no identifier to match on, so overlapping periods duplicate every time.

Does this work for a Fidelity 401(k) through NetBenefits?

NetBenefits is a separate institution entry from the Fidelity brokerage side and has its own history of downloading nothing or downloading securities Quicken cannot identify. Statements exist for those accounts too, and converting them works the same way for the cash and contribution activity. The connection side of that problem is covered in the Fidelity not downloading to Quicken guide.

The short version

The 90 day limit is not a bug and not something to troubleshoot. Treat it as a boundary and go around it. For recent gaps, pull consecutive date ranges from Fidelity's download screen and import them as QFX. For anything older, or for any account Fidelity will not export properly, the statement archive is the source, and converting those PDFs to QFX puts the transactions back into Quicken with real dates and correct signs. Start with converting a bank statement to Quicken if you want the general workflow first, then apply it statement by statement until the register ties.