Condense Data Falls Short Against the QuickBooks Online Target Limit
Files above roughly 350,000 targets fail the QuickBooks Online import, and the newer Condense Data utility keeps transactions, so counts barely fall.
Across community threads, a familiar roadblock greets QuickBooks Desktop users who try to carry their company file into QuickBooks Online: the import is measured in targets, not megabytes, and once the count passes roughly 350,000 the migration stalls. The remedy most threads point to, the Condense Data utility, carries a version-dependent catch that leaves many users back where they started.
Targets, not file size, decide the import
QuickBooks Online sizes an incoming Desktop file by its target count. Every line on an invoice, bill, check, or journal entry counts as a target, so a file that looks modest on disk can hold well over a million of them. Before planning any conversion, open the company file and bring up the Product Information window: press F2 on Windows, or Cmd+1 on Mac. The Total Targets figure shown there, not the file size, is the number that decides whether the Online import will go through.
What the accepted answer prescribes
The formally accepted solution begins with safety. Archive a backup of the original company file and store it somewhere secure, because a condense cannot be undone and reports may stop matching afterward. A portable copy, created from the File menu’s Create Copy option, adds a second layer of protection. QuickBooks also makes its own backup and leaves an archived copy of the pre-condense file in the same folder, its name tagged with the condense date.
The utility itself lives under File, then Utilities, then Condense Data, and some editions label it Clean Up Company Data instead; the Mac route asks you to close all open windows first. After acknowledging a warning that budget data may shift, choose the option to remove transactions before a chosen cutoff date, since closed transactions on or before that date are the ones affected. If you track inventory, set the cutoff to the last day of a month so the average cost for your items stays correct. From there, work through the wizard’s summarization and cleanup choices as they apply to your version, including any optional removal of unused list entries, and start the process.
The version split that changes the outcome
What condensing actually does depends on the Desktop version running it. In QuickBooks 2018 and older, the utility archived removed transactions and replaced them with summary journal entries. Target counts genuinely dropped, though the replacement entries generate targets of their own, and reports could stop reconciling with the originals.
In QuickBooks 2019 and newer, the utility was reworked. Transactions are kept, and the reduction comes from other data stored in the file. The file shrinks on disk, which helps performance, but the target count barely moves. For anyone condensing specifically to clear the Online import threshold, that is the crux: the modern tool improves speed and file size while rarely closing the gap that actually blocks the migration.
A second number adds to the confusion. In Desktop 2022 and newer, including Pro, Premier, Enterprise, and the Mac edition, the condense utility itself supports files below 4 million targets. That ceiling belongs to the Desktop tool alone, yet threads routinely blur it with the Online import limit, which sits an order of magnitude lower. A file that qualifies for condensing can still be far too target-heavy to import.
What users land on
A few practical patterns emerge from the discussions.
Check the target count first, before touching anything. If the figure sits only slightly above the import line, a condense with a cutoff set well back in history may bring it under, and rechecking the Product Information window confirms whether it worked.
If the count is far above the line, the built-in utility on a 2019-or-newer version is unlikely to close the gap on its own. The routes users take from there include importing lists and opening balances only, keeping the Desktop file running in parallel, or turning to a service that rebuilds the file with fewer targets, such as condensing an oversized company file ahead of an Online conversion.
Hold on to the archived copy regardless of the path chosen. Restoring it is the only way back if post-condense reports diverge, or if the Online import disappoints and the Desktop file needs to carry on as the system of record.
For users whose motive is slowness rather than migration, the newer behavior is less of a problem: the on-disk size still drops, which is what eases performance, even when the target count holds steady. The disappointment is specific to conversions, where the number that matters is the one the modern condense leaves alone.