September 9, 2026

QuickBooks Desktop Verify and Rebuild: what the messages mean, when a rebuild is enough, and when the file is telling you to move

The short answer: Verify Data is a diagnostic, Rebuild Data is the repair, and the sequence Intuit publishes is Verify, then Rebuild with a fresh backup, then Verify again. If the second Verify comes back clean, you are done. If it does not, the remaining errors are listed in the QBWin.log and are fixed one at a time, or you restore a backup. What the help article does not say is when to stop repairing a file and start rebuilding the books somewhere else. That threshold is the point of this post, and it is the same whether the file lives in Toronto, Manchester or Houston.

What the three Verify results mean

Intuit’s Verify and Rebuild article (updated 5 August 2026) describes three outcomes. “QuickBooks detected no problems with your data” means exactly that; stop. A specific error message means a known condition with its own support article, which you search for by the message text. “Your data has lost integrity” is the generic finding of data damage, and it is the one that sends you to Rebuild. The tool is run from File, Utilities, after closing every open window (Window, Close All), and it is worth running on a schedule, monthly or before every year-end and every migration, rather than only when something looks wrong, because the damage it finds is usually older than the symptom that made you look.

The rebuild sequence, exactly as published

File, Utilities, Rebuild Data. QuickBooks requires a backup before it will proceed; select OK.
Choose a location, and give the backup a new file name. Intuit is explicit: do not replace another backup file.
Let it run. The companion “Fix data damage” article (updated 2 August 2026) warns the program may appear frozen; as long as the mouse moves, it is working.
When “Rebuild has completed” appears, select OK, then run Verify Data again.
If Verify is clean, keep working. If it still finds damage, Intuit’s next steps are, in order: rebuild once more; run QuickBooks File Doctor; open the Verify Results window, Expand All, and use See Online Article for each listed error; or contact support. Errors without an article are support cases.

Two cautions from the same documents. Assisted Payroll subscribers are told to contact Intuit before rebuilding at all. And if the first rebuild took two hours or more, Intuit’s own instruction is to stop and contact support rather than keep trying, which is a useful signal about the file’s condition.

What a rebuild fixes, and what it cannot

Rebuild repairs the index and structural links inside the company file: transactions that lost their link to a list entry, targets that no longer add up to their source, the “verify item history” and “target bad pending state” class of QBWin.log lines that have their own Intuit articles. It does not fix a file that is simply too large to serve quickly (that is a target-count question, covered in QuickBooks Desktop file too large: condense or convert), a file that is physically corrupt on disk, a file damaged by a network drop mid-write (the H-series and -6000 conditions we cover in our H202 and H505 post and -6000 series post), and it does not fix the bookkeeping. A rebuild will happily leave a negative inventory quantity, an unreconciled bank account or a payroll liability that never cleared exactly as it found them, because those are not damage; they are data.

That distinction matters for the restore option. Intuit’s fallback when an error cannot be fixed is to restore a recent backup, re-entering everything since. Before doing that, weigh how much work sits between the backup date and today. A month of transactions is a day of re-keying; a year is a project, and at that point restoring is rarely the cheapest route.

When the file is telling you to move

A file that verifies clean after one rebuild is healthy. The patterns below are the ones we see in files that arrive for conversion, and each is a reason to stop repairing:

The same integrity error returns every month. Usually a damaged list entry or a transaction the rebuild cannot rewrite; the fix is a fresh file, not a fourth rebuild.
Rebuilds take hours, which by Intuit’s own threshold means the file is past self-service. Large, old files with many years of detail are the typical case.
Reports disagree with themselves: a balance sheet that does not balance, a customer balance detail that does not equal the customer’s open invoices, an inventory valuation that moves without transactions. Those are data-damage symptoms that Verify sometimes misses.
The version is off support and a payroll or bank-feed subscription has already stopped, so the file cannot be updated to the current release the tools expect.

In each case the sensible path is to take the verified data (lists, open balances, and as much clean transaction history as reconciles) and rebuild the ledger on the destination: a new QuickBooks Desktop file, QuickBooks Online, or another product entirely. The damaged file stays as a read-only archive. What a rebuilt ledger keeps and what it leaves behind is set out in what doesn’t convert, and the reconciliation standard the new file is proved against is on our reconciliation page.

Data damage is not the only thing to clear before a conversion; a non-zero Opening Balance Equity balance is the other setup fault we find most often, and it is fixed with a drill-down and one journal entry.

Before you send a file anywhere

Run Verify, keep the QBWin.log, take a portable company file as well as a backup, and note the product version and release from the Product Information window (F2). Those four things let a support engineer or a conversion team tell you in a day whether the file is repairable, and if it is not, they are the inputs a fixed-price rebuild quote is built on. Our QuickBooks support service handles the repair side; the conversion pages handle the move.

Frequently asked questions

What does “Your data has lost integrity” mean in QuickBooks Desktop?

It is the Verify Data result that means data damage was found in the company file. Intuit’s instruction is to run Rebuild Data, accept the backup prompt, then run Verify again to confirm the repair.

Is it safe to run Rebuild Data?

Yes, provided you take the backup the tool insists on and save it under a new name rather than over an older backup. Intuit’s one exception is Assisted Payroll subscribers, who are told to contact support before rebuilding.

How long should a rebuild take?

Minutes for most files, longer for large ones; Intuit says the program can look stuck while the mouse still moves. Its own threshold is that a first rebuild taking two hours or more is a reason to contact support.

Does data damage transfer if I convert to QuickBooks Online?

A migration should start from a file that verifies clean; unfixed damage usually surfaces as balances that do not agree after the move. Verify first; if the error persists, a fresh rebuild of the ledger from the clean data is the safer path.