Downgrading QuickBooks Pro Plus to an Older Perpetual Version: What Survives
Payroll history, reconciliations and linked payments all ride on a Pro Plus to perpetual downgrade; learn what carries over, what drops, and how to verify.
When a Pro Plus subscription no longer earns its keep, many firms go back to an older perpetual licence they already own. The licence is the easy part. The company file is the risk, because payroll history, reconciliations, and payment links all live inside it. The question is whether an older Desktop release can still read, and edit, all of that.
The one-way door in the company file format
QuickBooks upgrades a company file permanently the first time a newer version opens it. The software rewrites the file to its own structure and offers no command to reverse that. A 2024 Pro Plus file contains internal tables the 2020 program has never seen, so the older program refuses to open it rather than guess at the contents.
A downgrade is therefore a rebuild, not an export. Every list, transaction, and link is rewritten into the older format, and it must be done on a copy. Firms that handle version downgrades of QuickBooks company files rebuild the file while your subscription copy stays untouched as the fallback. Our engineers assess the file first, along the lines we set out for moving a company file off the subscription onto a perpetual licence, before any rebuild starts.
Records that carry over intact
Done correctly, the downgrade preserves the working heart of the file. Customer, vendor, employee, and item lists survive, along with the chart of accounts. All transaction history survives, including payroll checks and year-to-date wage figures. Employee records keep their payroll items, wage rates, and withholding details.
Linked payments survive with their links. A receive-payment keeps its tie to the invoice, and a deposit keeps its tie to the payments inside it. Reconciliations survive too: each transaction keeps its cleared status, and the reconciliation reports for closed periods remain. Memorized transactions and the preferences the older release supports carry as well.
Does the file stay fully editable?
Yes. Once rebuilt, the file opens in the older release and behaves like any native file of that version. You can add, edit, void, and delete transactions, reconcile accounts, and run payroll reports normally. The history is not frozen or read-only.
Items that do not carry over
User accounts and permissions do not survive the rebuild. They are tied to the source installation, so plan to recreate each user and reassign roles in the older version. Bank feeds connected under the subscription must be disconnected before the work and reconnected afterward; downloaded but unmatched items are not carried.
Features that arrived after your target year do not exist in the older program, and preferences unique to them are dropped. Live payroll calculation is the main constraint. The payroll data inside the file is untouched, but the vendor's payroll service only calculates for releases it still supports. If the target version sits outside that window, plan to record payroll manually or through a service that supports it.
Baseline the file before the downgrade
You cannot prove nothing was lost unless you record what you had. Our engineers do this before every rebuild, and you should do the same.
Update the source version to its latest release, then run Verify from the File, Utilities menu. If Verify reports problems, run Rebuild and then Verify again. A file that will not verify clean must be repaired first; see our QuickBooks Verify and Rebuild repair service. Then:
- Make a full backup (QBB) and a portable company file, and store both away from the working machine.
- Press F2 and save the Product Information window. Note the counts of names, list entries, transactions, and targets, plus the file size and the date of the first transaction.
- Export key reports as PDF or Excel. Include the balance sheet and profit and loss, for full history and for year to date. Add A/R and A/P aging, a payroll summary by employee for recent years, and the latest reconciliation report for each bank and credit card account.
- Write down each user name and its permission role.
Verifying the file in the older release
Open the rebuilt file in the older version and confirm the version shown on its Product Information screen. Run Verify again and expect a clean result. Then compare against your baseline.
Match the balance sheet totals, net income for the full history, payroll totals per employee, and aging totals line by line. The F2 counts matter as much as the reports: transaction and target totals should match the baseline exactly. Open the most recent reconciliation report for each account and confirm it matches. Spot-check one linked payment by drilling from a paid invoice to the payment behind it. Confirm memorized transactions and employee wage details are present.
Finish with an edit test. Add a memo-only transaction, save it, reopen it, then delete it. If the file accepts those changes without error, editing is live. Recreate the users, reconnect bank feeds, and keep the original subscription backup until the downgraded file has cleared a full month-end close.