“The import freezes on a large statement file”
Multi-year exports are where finance apps show their age. The file is usually valid — it is simply larger than the importer was built for, and the failure mode is a freeze rather than a helpful message.
Symptoms
The app stops responding partway through the import Import succeeds but takes many minutes, or crashes near the end Smaller date ranges from the same account import instantly
What actually causes it
Whole-file parsing in memory
Most desktop importers load the entire document before writing anything, so memory use grows with the file rather than staying flat.
Per-transaction duplicate checking
Every incoming transaction is compared against existing ones. When both sides are large, that comparison grows much faster than the file does.
A structural defect deep in the file
A parse error thousands of transactions in can look like a hang, because the app is failing slowly rather than stopping.
How to fix it
- Check the file first: drop it into the fixer below, which reports the transaction count and any structural problems without opening your finance app.
- Repair anything it finds — a defect midway through is worth ruling out before blaming size.
- Re-export in yearly or quarterly ranges and import them oldest first, which keeps every step small and makes a failure easy to locate.
- Back up your data file before a large import; recovering from a half-finished one is much easier with a backup than without.
Related import problems
Skip the manual edit — fix it automatically
The fixer handles files far larger than most desktop importers, so it can tell you whether the problem is size or a defect before you spend an afternoon on it. Free, no signup, no upload.
Open the fixer