QuickBooks Desktop Condense vs. SuperCondense: Choosing the Right Path for Canadian

Evaluate file size, transaction counts, and multi-currency impact to choose between the built-in Condense utility and a full SuperCondense for Canadian QuickBooks files.

When a QuickBooks Desktop company file grows past 1 GB, performance degrades and the risk of data corruption rises. Canadian edition files carry an additional wrinkle: multi-currency, which can block or complicate the built-in Condense utility. Our engineers use a structured evaluation to determine whether the built-in Condense tool will produce a meaningful size reduction or whether a full SuperCondense service is the safer, more effective path.

Gather File Intelligence

Open the company file in QuickBooks Desktop and press F2 (or Ctrl+1) to bring up the Product Information screen. Record the following:

• QuickBooks version and edition (Pro, Premier, or Enterprise, plus the year)
• Company file size (shown on the Product Information screen)
• Total targets and transactions (visible at the bottom of the same screen)
• List counts: customers, vendors, employees, and other names
• First transaction date in the file
• Inventory item count, if inventory is in use
• Multi-currency status: confirm whether multi-currency is enabled

Run File > Utilities > Verify Data and note whether it passes cleanly or reports errors. If Verify fails, run Rebuild and re-run Verify. A file that cannot pass Verify is not a candidate for the built-in Condense utility — it must be repaired first.

Assess Built-In Condense Feasibility

The built-in Condense utility (available under File > Utilities) removes closed transactions dated on or before a cutoff you specify, replacing them with journal-entry summaries. Evaluate it against these conditions:

• File size: The built-in tool typically yields 20–40 percent reduction. If the file is 2 GB or larger, the reduction may still leave it oversized.
• Multi-currency: If multi-currency is enabled, the Condense utility may refuse to run or may produce errors mid-process. This is one of the most common failure points for Canadian edition files.
• Transaction density: Files with heavy daily transaction volumes compress poorly because the summary journal entries themselves consume space.
• Inventory: Advanced inventory or large item assemblies can cause the Condense to stall or fail.
• Verify/Rebuild status: The file must pass Verify cleanly before Condense can be trusted.

If all conditions are favorable — multi-currency is off, the file passes Verify, and a 20–40 percent reduction is sufficient — the built-in utility is a reasonable first attempt.

Set a Clean Cutoff Date

Whether using the built-in Condense or preparing for a SuperCondense, the cutoff date determines which transactions are removed or summarized. We recommend the following approach:

1. Identify the fiscal year-end that is at least one full reporting cycle behind the current open period.
2. Confirm that all bank and credit card accounts have been reconciled through the cutoff date.
3. Confirm that all payroll liabilities and sales tax (GST/HST/PST) filings are closed through the cutoff.
4. Confirm that no uncleared bank deposits or payments exist dated before the cutoff.
5. Document the cutoff date and communicate it to all users who access the file.

Never set a cutoff date that falls inside an open reporting period or an unreconciled range. Doing so destroys the audit trail for transactions that may still need to be referenced.

Execute the Built-In Condense

If the assessment points to the built-in utility:

1. Create a verified backup (File > Back Up Company > Create Local Backup) and store it on separate media.
2. In single-user mode, run File > Utilities > Condense Data.
3. Select the option to summarize transactions up to the cutoff date.
4. Choose whether to keep inventory transactions uncondensed (recommended if inventory valuation accuracy is a concern).
5. Allow the process to run uninterrupted. For large files this can take several hours.
6. When it completes, press F2 and record the new file size and target count.
7. Run Verify Data on the condensed file.

Rollback point: If the Condense fails, produces errors on Verify, or results in an insufficient size reduction, restore from the backup created in step 1. Do not continue operating on a partially condensed file.

When to Escalate to SuperCondense

A full SuperCondense is warranted when any of the following are true:

• The file uses multi-currency and the built-in Condense will not run.
• The built-in Condense completed but the file remains oversized.
• The file needs to shrink below a specific threshold for a QuickBooks Online migration.
• The file needs to be reduced for a CRA audit period copy, retaining only a specific date range.
• The built-in Condense has failed on previous attempts and the file is now unstable.

To scope a SuperCondense, provide the F2 Product Information details, the file size, the Admin password, the desired cutoff date, multi-currency status, and whether Verify currently passes. Our engineers use those details to confirm feasibility and turnaround.

Verify a Clean Outcome

Regardless of which path was taken, a clean outcome means:

• The file opens without errors in single-user and multi-user mode.
• Verify Data passes with no issues reported.
• The balance sheet as of the cutoff date matches the pre-condense balance sheet.
• Trial balance by account for the current open period is unchanged.
• The file size on the F2 screen shows a meaningful reduction.
• All users can access the file and perform normal entry, reporting, and reconciliation tasks.

If any of these checks fail, stop activity on the file and restore the pre-condense backup. A partially successful condense is worse than no condense at all because it introduces uncertainty into the data.