Quick answer

A failed company file migration leaves the original .QBW half-converted and the update wizard unable to finish. Stop opening it, preserve the partially converted file, and restore the automatic pre-upgrade backup (a .QBB file) in the old version of QuickBooks. Clean the restored file, then retry the update once from a local drive. If it fails again, step through an intermediate version or contact Intuit support.

What a failed company file migration leaves behind

When you open an older company file in a newer year version of QuickBooks Desktop, the program asks to update the file. The update wizard converts the file's internal structure, and that conversion has to happen exactly once. When it fails partway through, you are left with three things:

  • The partially converted .QBW. It may still open in the old version, may open without some lists, or may refuse to open in both versions. Treat it as evidence, not as a working file.
  • The automatic pre-upgrade backup. Before conversion starts, QuickBooks creates a backup company file (a .QBB) of the file as it was in the old version. That backup is your rollback point.
  • Support files. The .TLG, .ND and .DSN files beside the company file can be left pointing at the interrupted conversion.

The failure usually appears as an error dialog while the progress bar runs, or as a "cannot open" message when the new version tries to load the file. Wording changes between versions, but the result is the same: the new version cannot finish, and the old version may no longer accept the file. This is different from a normal year-version upgrade, where the file converts and opens cleanly.

Symptoms of a failed conversion

  • The update stops or errors out, and the company file does not reopen.
  • The new version asks to update the same file every time QuickBooks launches.
  • The old version refuses the file, often saying it was created with a newer version.

Common causes, ranked by how often technicians see them

  1. Data damage that existed before the upgrade. Intuit's Enterprise update instructions call for Verify Data before installing, because a file with unresolved damage often fails conversion.
  2. The file was on a server, mapped drive or cloud-sync folder. Intuit tells users to move the company file to the local hard drive before updating. Network shares and sync tools introduce locks and partial writes.
  3. Another user or process held the file open. All users must sign out, and background processes such as QBW32.exe must be closed.
  4. Special characters in the file name. Intuit says to remove characters such as :, & and / from the name before upgrading, and to confirm the .qbw extension.
  5. The Admin account had no password. Enterprise updates require the Admin user to have a password, and only the Admin can convert the file.
  6. The version gap was too large. Intuit notes that some files cannot convert in one jump and must be stepped through an intermediate version.
  7. A product or region mismatch. A file created in a non-US version reports "This file was not created with a US version of QuickBooks," and an Enterprise file cannot open in Pro or Premier.

Stop reopening the partially converted file. Every launch can write more changes or restart the conversion, moving the file further from its original state. A half-converted .QBW is not a supported recovery point; the pre-upgrade .QBB backup is. Copy both to a safe location before you touch anything else.

Before you begin

  • Back up everything first. Copy the entire company-file folder to an external drive: the partial .QBW, every .QBB backup, and the .TLG, .ND and .DSN files.
  • Confirm your versions. Press F2 in QuickBooks to see the product, version and file name. You need the old version to restore and clean the backup, and the new version to retry.
  • Have the Admin password ready. Only the Admin user can update a company file.
  • Plan for time and possible re-entry. Allow 30–90 minutes for a large file. If you roll back, transactions entered after the backup must be re-entered; QuickBooks cannot export transactions between two company files or merge them.

How to recover a failed QuickBooks company file migration

1

Stop every conversion attempt and close QuickBooks

Close QuickBooks and open Task Manager with Ctrl + Shift + Esc. On the Details tab, end QBW32.exe, QBDBMgrN.exe, QBUpdate.exe and QBCFMonitorService.exe if they are running. Do not click Update Now again and do not open the affected file in either version. Your recovery sources survive only if you stop writing to them.

2

Preserve the evidence in a Pre-Conversion Backup folder

Create a folder named Pre-Conversion Backup on an external drive or a second computer, using Intuit's own label. Copy the whole company-file folder into it, then note the name, size and modified date of each file. If a recovery specialist ever examines the failed conversion, these untouched copies are what they work from.

3

Find the automatic pre-upgrade backup

The wizard creates the backup before it converts anything. It is a .QBB file, and if you selected Change this default location during the update, it sits in the folder you chose. Search your drives for *.qbb, sort by date, and pick the file created minutes before the failed conversion.

If no .QBB exists, do not keep experimenting with the partial file. Move to the escalation options below and let Intuit support or a specialist work from the copies you preserved.

4

Restore the pre-upgrade backup in the old version

Open the old version of QuickBooks. If you installed the new version over it, Intuit's guidance is to reinstall the old version into a separate folder so you can work with the pre-conversion backup. Go to File → Open or Restore Company, select Restore a backup copy, choose Local backup, and point the wizard at the .QBB.

Restore under a new file name such as CompanyName-PreUpgrade.qbw. Never restore over the partially converted file or leave the two files with the same name in one folder.

5

Clean the restored file in the old version

Sign in as the Admin user, then go to Window → Close All. Open File → Utilities → Verify Data. If QuickBooks reports lost integrity, run Rebuild Data, then verify again until it reports no problems. A file that verifies clean has the best chance of converting.

Then remove conversion blockers: take special characters out of the file name, confirm the Admin user has a password, and move the file to a local drive. Current builds edit the Admin user under Company → Users; older builds show Company → Set Up Users and Passwords. Both reach the same user list.

6

Test the conversion on a copy first

Copy the cleaned .QBW to a second file, such as CompanyName-Test.qbw, in a plain local folder, and convert the copy in the new version. If the copy converts, the data is healthy and you can convert the original. If it fails, you still hold a working old-version file and can escalate safely.

7

Retry the update with the official workflow

Make sure every user is signed out. Open the new version and go to File → Open or Restore Company → Open a company file → Next. Select the cleaned file and sign in as Admin. When QuickBooks offers to save the pre-upgrade backup, choose a clearly named folder or a different drive, then select Update Now and Done when it finishes.

Do not open other programs while the wizard runs, and do not let the machine sleep partway through; an interrupted conversion is how most of these failures start.

8

If it fails again, stage the upgrade or escalate

Intuit's instructions are to restore the backup and try again, then contact support if the second attempt fails. For a large version gap, the compatibility guidance is to step the file through an intermediate version instead of converting in one jump. Before that retry, verify and rebuild the file again, and plan to involve professional company file repair or a data recovery service rather than repeating the same conversion on the same damaged file.

Verify the migration worked

  1. Press F2 and confirm the product, version number and file name are what you expect.
  2. Run File → Utilities → Verify Data until QuickBooks reports no problems.
  3. Compare a Balance Sheet and an A/R Aging Summary against the pre-upgrade figures.
  4. Upgrade every workstation to the same version before opening the file in multi-user mode, then post and delete a test transaction from a second computer.
  5. Create a fresh backup, label it with the new version number, and store it off the machine.

If the migration still fails

  • Intermediate version. Install an older bridge version, convert the file there, then convert again in the target version. This is the official workaround when a single jump fails.
  • Intuit Data Services. If Verify and Rebuild cannot clean the file, Intuit's data services team can attempt recovery. This is the right escalation for damage that predates the upgrade.
  • A conversion specialist. Large Enterprise files, heavy customizations and files with years of damage are safer with a specialist than in a conference-room retry at month end.
  • Give them everything. Hand over the preserved partial file, the pre-upgrade .QBB, the exact error text, both version numbers, and the steps that led to the failure.

One hard rule: you cannot downgrade an upgraded file. Intuit states that a file converted to a newer version cannot be opened in the older version, and because QuickBooks cannot merge or export transactions between files, rolling back means restoring the pre-conversion backup and re-entering anything entered afterward.

Prevention

  • Run Verify Data, and Rebuild if needed, before installing a new version. Convert only a file that verifies clean.
  • Keep a dedicated Pre-Conversion Backup folder until you complete a full month-end close and payroll run in the new version.
  • Convert from the local hard drive, then move the file back to the server. Never convert across a network share or sync folder.
  • Keep the file name short and free of :, & and /, and make sure the Admin user has a password.
  • Schedule upgrades off-hours, never before payroll or a filing deadline, and test on a copy first.

Frequently asked questions

Can a partially converted QuickBooks file be repaired?

Sometimes, but only by Intuit Data Services or a data-recovery specialist, and results are never guaranteed. Do not keep reopening the file to test it; each attempt can change it further. The reliable path is the pre-upgrade .QBB backup.

Can I go back to the old QuickBooks version after the file converts?

No. Intuit's guidance is explicit: a file upgraded to a newer version cannot be opened in the older version. Going back means restoring the pre-conversion backup, which loses every transaction entered after that backup was created.

Did the failed upgrade damage my transactions?

Usually not. Most failures are environmental, such as a network location or a locked file, and the data inside the pre-upgrade backup is intact. Pre-existing damage is the main exception.

Will restoring the automatic backup lose data?

Only work entered after it was made. QuickBooks creates that backup immediately before converting, so when an update fails within minutes, the backup typically contains everything.

Why does QuickBooks ask to update the file every time I open it?

The conversion never completed and the file is still flagged as old. Stop launching it, confirm whether a .QBB backup exists, and follow the rollback steps above instead of letting the wizard run again.

Sources & further reading