Converting an Accountant's Copy to a Regular Company File When the Original QBW Is Lost

When the client's original .QBW is damaged or missing, our engineers extract a working company file from the Accountant's Copy and verify every change survived.

When a client's original .QBW is lost, corrupted, or trapped on an inaccessible machine, the Accountant's Copy (.QBA) may be the most complete surviving snapshot of the company's books. Our engineers regularly convert this file into a fully functioning regular company file. The operation is delicate: the .QBA carries accountant changes, restricting dates, and imported transactions that must all survive the conversion intact.

When to Run This Playbook

This procedure applies when the client's source .QBW is unrecoverable and the Accountant's Copy is the best or only remaining data source. If a recent .QBB backup or a working .QBW exists, recovering or repairing that file is always preferable. We have written about repairing damaged QuickBooks company files elsewhere; this page covers the specific scenario where those options are exhausted and the .QBA is the fallback.

Phase 1: Inventory and Isolation

Before touching the .QBA, we establish what we are working with. We confirm the QuickBooks version and edition that created the Accountant's Copy, the file size, and whether an Admin password is set. We copy the .QBA and its supporting files to an isolated working directory. The original is never operated on directly. If the client can provide the dividing date that was set when the Accountant's Copy was created, we record it, as it determines the boundary between client-editable and accountant-editable transactions.

Phase 2: Pre-Conversion Integrity Check

We open the .QBA in the matching version of QuickBooks Accountant. If the file opens without error, we press F2 to bring up the Product Information screen and capture the file's vital statistics: list counts, transaction counts, first transaction date, and file size. We then run Verify from the File > Utilities menu. If Verify reports problems, we run Rebuild. A file that fails Verify after Rebuild may require deeper QuickBooks data recovery before conversion can proceed. Attempting to convert a structurally damaged .QBA will carry the damage into the resulting .QBW.

Phase 3: Accountant Change Review

Before conversion, we review what the Accountant's Copy contains. We open the Client Data Review or the Accountant's Copy activity log to see what changes were made: general journal entries, reconciliations, payroll adjustments, and reclassified transactions. We document the count and type of these changes. This list becomes our verification baseline in Phase 6. Any transactions the client entered during the dividing-date window and imported into the .QBA are also noted.

Phase 4: Conversion Execution

QuickBooks provides a built-in mechanism to convert an Accountant's Copy to a regular company file. From within the open .QBA, we select File > Utilities > Convert Accountant's Copy to Company File (QBW). QuickBooks will warn that this action severs the link to the client's original file and that the resulting .QBW cannot be merged back. We acknowledge the warning and proceed. QuickBooks prompts for a save location and filename. We save to the isolated working directory with a name that clearly distinguishes it from the original .QBW. The conversion process runs internally; there is no intermediate export format to manage.

Phase 5: Post-Conversion Verification

Once the conversion completes, we open the new .QBW in the same QuickBooks version. We press F2 and compare the list counts and transaction totals against the baseline captured in Phase 2. We run Verify again on the converted file. If Verify fails, we run Rebuild and re-verify. A clean Verify pass on the converted .QBW is mandatory before we consider the operation complete.

Phase 6: Change Survival Confirmation

We now confirm that every accountant change documented in Phase 3 is present in the converted .QBW. We spot-check journal entries by number and date, verify that reclassified transactions reflect the correct accounts, and confirm that any reconciliation adjustments carried through. We also check that the restricting date has been removed and that the file behaves as a normal company file: full editing capability across all dates, no Accountant's Copy restrictions, and no pending-import status.

Rollback Points

The primary rollback point is the original .QBA copy preserved in Phase 1. If the conversion produces a corrupt or incomplete .QBW, we discard it and restart from that copy. If the .QBA itself fails Verify in Phase 2, the rollback is to stop and address the underlying file damage before attempting conversion.

Clean Outcome

A clean outcome is a .QBW that opens without errors, passes Verify, contains every transaction and list entry from the .QBA, shows no Accountant's Copy restrictions, and matches the documented baseline for list counts, transaction totals, and accountant changes.