Recovering a QuickBooks company file stranded by a failed upgrade
A failed upgrade can leave a QuickBooks company file that opens in neither the old nor the new version; this playbook gets you back on your books.
An upgrade that fails midway leaves a QuickBooks company file stranded between two versions. The new release has rewritten part of the file into its newer internal format, so the old release refuses it. The conversion never finished, so the new release stops partway too. This playbook covers the triage, the restore, and the decision that follows, so your books come back whole and nothing needs to be re-keyed.
Stop before the second attempt
Do not retry the upgrade. Every failed attempt writes more of the new format into the file and can turn a recoverable state into real damage. Close QuickBooks on every workstation and on the server, then work at the file system level.
Copy the whole company file folder to a separate location: the .qbw file, its .tlg transaction log, and any .qbb backup beside it. File-level copies are safe. Opening the file is not, not yet. Confirm the drive holding the file has several times its size in free space. A conversion that runs out of room mid-write leaves deeper damage than one that stops for any other reason.
Triage the stranded file
When we triage a stranded file, we look for three things before anything is opened.
First, the backup made just before the conversion started. Many upgrade runs create one automatically, or you accepted the prompt for one; look for a fresh .qbb beside the company file, timestamped within minutes of the attempt. If it is there, you already hold your route back.
Second, the .tlg. If transaction logging was on, transactions posted after your last backup may still sit in that log. Keep it, whatever you do next.
Third, the details that decide what a later conversion can carry: the exact year and release of both versions, whether a non-US edition is in use, and whether multi-currency or advanced inventory is enabled.
Restore and verify the pre-upgrade backup
Restore in the old version, the release that ran before the upgrade. Use Open or Restore Company, choose Restore a backup copy, and point it at the best .qbb you found. Restore into a new folder. Never restore over the half-converted file; keep that untouched as a last resort and as evidence of what the attempt did.
When the restored file opens, check it before you trust it. Press F2 for the Product Information screen and confirm the version, the transaction count and the last transaction date against your books. Open the most recent invoice and the most recent payment. Then run Verify under the File menu, Utilities. If Verify reports problems, run Rebuild once, then Verify again.
If Verify still fails, stop. A backup that will not verify cannot serve as a rollback point, and it needs QuickBooks file repair before anything is built on it. If it passes, make a fresh manual backup immediately. That verified backup is your first rollback point for everything that follows.
Fill the gap the backup left
A backup is a snapshot, and work continued after it was taken. If the .tlg from the failed attempt is recent, transactions posted since the backup may be recoverable from it; the log is a sequential record and survives even when the file beside it will not open.
Reconcile the recovered file against bank and credit card statements for the missing weeks. Whatever the log cannot supply is usually a short list, re-enterable from statements or the last reconciliation report, and that is a small job rather than a rebuild.
Re-upgrade or downgrade?
Take this decision only when a verified backup exists, and never on the only surviving copy.
Our engineers split the two routes on one question: did the upgrade fail because of the environment, or because the move no longer makes sense? An interrupted install, an antivirus lock, a full disk or a Windows permissions fault will stop a conversion, and all of them can be fixed. Confirm the new release is fully installed and updated, take a second backup, and convert that backup in one pass. Never convert the half-converted file; convert the verified backup.
A downgrade is the right call when the reason for upgrading has gone away, most often because a subscription lapsed and the licence in hand is an earlier year. QuickBooks opens files forward, never backward; the format conversion is one-way, and there is no menu option that takes a newer-format file back to an older release. It is an external conversion, and specialist services such as QuickBooks file downgrade and conversion handle it without re-keying history.
State the exact versions on both sides, and whether the file is a non-US edition, before anyone starts work. Whichever route you take, convert a copy and keep the last good backup beside it. That copy is your rollback point if the conversion fails a second time.
A clean outcome looks like this
The file opens in its target version without an error. The F2 screen shows the expected year and release, and the last transaction date matches the books. Verify runs clean. A dated backup of the converted file exists somewhere other than the machine that failed the upgrade.
The half-converted file and its .tlg stay quarantined and clearly labelled until the recovered file has survived a full month-end close and a reconciliation. Delete them only after that. If a restored backup will not open in either version, or Verify cannot be made to pass, the damage predates the upgrade and the file needs recovery work, not another conversion.