A backup that happens before the risky moment, not after
Before any batch import, large data cleanup, or multi-user heavy operation, a fresh backup gets created automatically, so a rebuild gone wrong never costs real work.
Go to File, then Utilities, then Rebuild Data. QuickBooks backs up your file automatically before it starts, then scans for and repairs data damage on its own, no further input needed until it finishes. It's a QuickBooks Desktop feature; QuickBooks Online has no equivalent since there's no local file to damage in the first place.
1. Close out other work first. Rebuild Data needs exclusive access to the file, so make sure nobody else is in it if you're on a network, and save any report customizations you're mid-edit on.
2. Open the Rebuild Data utility. Go to File, then Utilities, then Rebuild Data.
3. Let QuickBooks create the backup it prompts for. It asks to back up the company file before touching anything; don't skip this. If the rebuild goes wrong for any reason, that backup is your way back to where you started.
4. Wait for the rebuild to finish. QuickBooks scans the file and repairs whatever data issues it finds. Larger files can take a while; don't close the program or restart your computer while it's running.
5. Review the rebuild log if you want the detail. QuickBooks keeps a technical log (QBWin.log) of exactly what it found and fixed, useful if you're troubleshooting with support or trying to figure out whether the same issue keeps recurring.
6. Run Verify Data afterward. Go back to File > Utilities, this time choosing Verify Data, to confirm the rebuild actually cleared the problem instead of just hiding it. If Verify still flags something, you may need to rebuild again or move on to other repair options.
Rebuild Data is good at patching structural damage inside the file itself. It doesn't do anything about whatever's causing that damage in the first place, which is often something outside the file entirely: a flaky network connection for a multi-user setup, a file that's grown too large for comfortable daily use, or one workstation losing its connection mid-save.
That distinction matters because a business that rebuilds the same file every few weeks isn't actually fixing anything, it's treating a symptom on a schedule. Someone ends up doing this as a recurring chore, watching for the warning signs (slow performance, odd error messages, a report that doesn't tie out) and running the utility reactively instead of addressing whatever keeps causing the damage.
Before any batch import, large data cleanup, or multi-user heavy operation, a fresh backup gets created automatically, so a rebuild gone wrong never costs real work.
File size, error frequency, and which workstation keeps dropping connection get tracked over time, so a pattern that usually precedes a crash gets flagged before the crash happens, not after.
Tell us how frequently you're running this utility and what seems to trigger it, and we'll tell you if the real cause is something that can be fixed instead of patched.
Tell us what the file's actually doing right before it breaks, slow saves, a specific error, a particular workstation acting up, and we'll tell you whether that's fixable for good instead of something you keep patching. And file damage is just one example of a repeating manual fix; we take on anything else in the business that's stuck in the same loop.
Let's talk →It means QuickBooks is scanning its own company file for internal data damage, broken links between transactions, corrupted list entries, and similar structural problems, then fixing what it can automatically. It's not the same as restoring from a backup; the file stays the same one you were already using, just repaired in place.
Yes, they're different tools. Rebuild Data is built into QuickBooks and focuses on damage inside the file itself. File Doctor is a separate download from Intuit aimed more at network and connectivity issues, the kind that show up as "can't open the company file" across a multi-user setup rather than data corruption inside it.
Sometimes, if the crash is caused by data damage that Rebuild Data can actually reach. If the file won't open far enough for the utility to even run, or the crash is really about file size, a damaged hard drive, or antivirus software interfering, rebuilding won't help and you'll need File Doctor, a restored backup, or a support ticket with Intuit instead.
Try File Doctor next, since it catches a different category of problem. If that doesn't clear it either, restoring from your most recent clean backup is usually the safest next step, followed by re-entering anything that happened after that backup was made.