Coordinated QuickBooks Desktop Repair and Supercondense in a Single Service Window

Sequencing data-damage verification, rebuild, and transaction removal in one planned downtime event so the file passes integrity checks and lands at target size.

When a QuickBooks Desktop company file has grown too large for reliable operation and also carries structural damage, running repair and supercondense operations separately means two full outages. Our engineers sequence both into a single planned service window so the rebuilt file passes integrity checks and lands at the target file size without requiring a second downtime event.

When to Run This Playbook

Run this combined operation when the company file exhibits both conditions: measurable data damage flagged by Verify Utility or by a third-party audit, and a file size that is large enough to cause performance degradation or to exceed a migration threshold. For files being prepared for QuickBooks Online conversion, the target file size is under 1 GB, with roughly 500 MB being ideal for the smoothest import experience.

Do not attempt this on a file that has not been backed up in the last 24 hours, or while any user is logged into the company file in multi-user mode.

Phase 1: Pre-Flight Assessment

Before scheduling the outage window, gather the information that determines scope and sequencing.

1. Open the file in single-user mode as the Admin user. Press F2 to open the Product Information screen and record the file size, list counts, and QuickBooks version.
2. Run File → Utilities → Verify Data. Capture the full result. If Verify reports no damage, skip directly to Phase 4 — the repair steps are unnecessary and the window can focus on condensing alone.
3. If Verify reports damage, note the specific error codes or the "Rebuild Now" prompt text. Run Rebuild Data once and re-run Verify. If damage persists after a single Rebuild, document the remaining errors for manual repair in Phase 3.
4. Record the current transaction count by running a Transaction Journal report for all dates. This baseline confirms how much the supercondense removed.

Rollback point: The backup created before running Verify is the clean restore point. If Rebuild introduces unexpected instability, restore this backup before proceeding.

Phase 2: Cutoff Date Selection

The cutoff date determines which transactions the supercondense retains and which it removes. Earlier cutoff dates reduce file size more aggressively.

1. Review the annual transaction volume. A file generating 40,000 transactions per year needs a more recent cutoff than one generating 8,000 to reach the same target size.
2. Identify any open transactions — unpaid invoices, unreconciled bank or credit card entries, outstanding purchase orders — dated before candidate cutoff dates. The cutoff should fall after the most recent meaningful open-item activity, or those items must be manually closed first.
3. Confirm the cutoff with the accounting team before the service window begins. Changing the cutoff mid-process invalidates the work done up to that point.

Phase 3: Structural Repair

Execute this phase inside the scheduled window, before any transaction removal begins. Repairing first ensures the supercondense operates on a structurally sound database.

1. Restore the pre-flight backup in single-user mode.
2. Run Rebuild Data. Allow it to complete without interruption — the process may appear to hang near the end. Do not force-close QuickBooks.
3. Re-run Verify Data. If it passes, proceed to Phase 4. If it fails again, the damage requires manual intervention at the list or transaction level. Our engineers typically handle this using targeted table-level repair tools before re-running Verify.
4. Repeat the Verify cycle until it returns a clean result with zero negative line items, zero orphaned list entries, and no balance sheet out-of-balance condition.

Rollback point: Once Verify passes cleanly, create a verified backup. This is the checkpoint that protects the supercondense phase. If anything goes wrong during transaction removal, restore this backup — the repair work is preserved.

Phase 4: Supercondense Execution

With a verified, repaired file in place, remove transactions dated before the cutoff.

1. Load the verified backup from the end of Phase 3.
2. Enter the confirmed cutoff date. The process removes transactions dated before this point while retaining all list items — accounts, customers, vendors, employees, and items — by default.
3. Decide whether to remove inactive list entries that have no remaining post-cutoff activity. This step requires explicit confirmation for each list type and is optional. Removing unused lists further reduces file size but is irreversible.
4. Run the supercondense. Depending on file size and transaction volume, this step may take several hours. Monitor progress but do not interrupt.

Rollback point: The verified backup from Phase 3 remains the restore point until Phase 5 confirms success.

Phase 5: Validation and Sign-Off

Confirm the file is both structurally sound and sized within target.

1. Run Verify Data one final time on the condensed file. A clean result confirms the supercondense did not introduce structural issues.
2. Press F2 and record the new file size. Compare against the target threshold.
3. Spot-check critical reports: Balance Sheet as of the cutoff date, Trial Balance, and A/R and A/P aging. Balances should match the pre-condense file as of the cutoff.
4. Create a final backup labeled with the date and "post-repair-condense."

A clean outcome is a file that passes Verify with no errors, lands at or below the target file size, and produces balance sheet and aging reports that reconcile to the pre-process file as of the cutoff date — all completed within a single scheduled outage.