Condense failed, or it finished and the file is still huge

What is actually happening

Condense (File, Utilities, Condense Data) is built to do what a rebuild does. You pick a date. QuickBooks keeps full detail after it and summarizes what came before. Before it starts, it saves an archive copy of the whole file.

Then it works through every transaction dated before your date, inside your existing file. Closed transactions are removed and replaced with summary journal entries, by month or as a single entry depending on the option chosen. It keeps anything it cannot safely summarize: invoices and bills still open, open sales orders and purchase orders, transactions not yet reconciled, and anything linked to a transaction after the date. Inventory is summarized or kept in detail depending on another choice in the wizard. Your lists stay unless you choose to remove unused entries.

On an old file, that is a long walk through decades of records, with everyone else locked out. Damage that Verify Data would report tends to stop it partway. So can an interruption: a computer that sleeps, a network drop, a backup job that starts mid-run.

When it does finish, the file is rarely much smaller. Everything open, unreconciled, linked or kept for inventory stays, the lists stay, and you are still in the same aging database. Meanwhile, Sales by Item, inventory detail and reconciliation reports for the condensed years go blank. The summary entries move the general ledger. They do not move item detail, so the inventory account and the inventory reports can stop agreeing.

What people try first, and what it costs them

Running it again. Same file, same damage, usually the same stopping point. Each attempt costs another weekend with the file offline.

Verify, Rebuild, then Condense. The right order, and on a moderately sized file it sometimes gets Condense through. On a damaged or very large file, Condense often stops on what Rebuild leaves behind.

A paid condense service. Someone else runs a similar process, sometimes with better results on damaged data. The outcome is the same kind of file: detail summarized away before the date, inside the old database.

Starting over or a summary conversion. Small and clean, and your history stays behind in the old file.

Restoring the backup. If Condense stopped partway, this is the right move: do not keep working in a file that stopped mid-condense until you know its state. But the backup, like the archive copy, is your old file, full size, with every problem it had.

What a line-by-line rebuild does instead

A rebuild uses the same idea as Condense and changes the two things that make it fail.

First, it does not work inside your old file. We build a fresh QuickBooks Desktop file: lists, items, the opening position at your cutover date, then every transaction since, line by line, and every open order with its real lines. Nothing has to be removed from an aging database, so there is nothing to stall on.

Second, nothing before the cutover is summarized. Those years stay in your current file, which becomes the retired file, read-only and untouched. Every old invoice, build and reconciliation is still there in full.

If your file was condensed successfully years ago, its summary entries sit before the cutover and stay in the retired file. Their effect on your balances comes forward in the opening position, exactly as your file shows it. We do not plug a gap between the inventory account and the inventory detail. We carry it as it stands and give your CPA a written breakdown of where it came from.

You see a scorecard before the final payment: trial balance at every month-end, AR and AP by name, inventory by item and site, open orders.