QuickBooks Desktop to Online: what doesn't transfer, and how to check your books after the move

I do not assume that QuickBooks Online is going to behave exactly like QuickBooks Desktop.

Before the move, I identify the Desktop features and workflows the business actually relies on. That matters much more than working from a generic list of everything QuickBooks can theoretically transfer.

For one business, the important pieces might be:

• estimates and invoicing;
• job costing;
• classes or locations;
• payroll;
• sales tax;
• memorized reports;
• custom forms;
• bank feeds;
• reconciliation history.

Another company may have a much simpler file and only care about a few bank accounts, customers, vendors, and normal monthly reporting.

I use the current Intuit migration documentation to verify anything that could behave differently between Desktop and Online, because the conversion tools and product features can change.

The goal is not to make QuickBooks Online look exactly like Desktop.

The goal is to know what the business depends on before the move, make sure the accounting data comes across correctly, and test the important workflows afterward.

Intuit publishes the list. Here is the part of it you'll feel.

Three of those hit owners first. Your reconciliation reports are gone, so the proof that last year's books tied to the bank is now a PDF you hopefully saved. Your bank connections are gone, so every account has to be reconnected, and that is where cash gets doubled (more on that below). Your invoice and statement templates are gone, so the first invoice out of the new file looks like Intuit's default until someone rebuilds yours.

Intuit also puts limits on the move itself. The file has to be under 4,000,000 targets or you condense it first. You get 90 days from the day you sign up for QBO to bring the file over, or 180 if your accountant set up the subscription. And if the QBO company already has data in it, the import replaces it, and Intuit's wording is that you can no longer undo that action.

When QuickBooks says the migration is complete, that tells me the raw data made it into QuickBooks Online. It does not tell me the new file is fully accurate, clean, or ready to become the company's working books.

There is usually still validation to do, and there may be cleanup.

I compare the Desktop file and the new QuickBooks Online file using the same cutoff date and the same accounting basis. I want to know that the accounting results carried over correctly before anyone starts treating the Online file as the new source of truth.

At minimum, I usually compare:

• Balance Sheet
• Trial Balance
• Profit and Loss
• Accounts Receivable aging
• Accounts Payable aging
• bank and credit-card balances

Then I look more closely at accounts that commonly expose problems, including Undeposited Funds, payroll liabilities, equity, and any material balance that does not make sense after the move.

A migration can also uncover problems that were already sitting in the Desktop file.

I regularly find old transactions that were categorized incorrectly, coded to the wrong account, duplicated, or left unresolved long before the migration started. That is one of the benefits of having someone who understands the accounting handle the migration instead of treating it like a software export.

The migration gives me an opportunity to validate the new file and identify problems in the old one.

I do not automatically "fix" every difference just to make the two systems match. First I want to understand what caused it.

If a report does not tie, I determine whether the difference came from:

• the way QuickBooks converted the data;
• a missing transaction;
• a duplicate;
• an account or mapping issue;
• or a problem that already existed in Desktop.

If I cannot explain a material difference, I do not consider the new file ready.

None of this is on Intuit's list. All of it is from doing the work.

The import summary talked you out of checking

When the export finishes, Intuit gives you an import summary. Read the counts before you read the words. Transactions in Desktop should equal transactions in Online. Vendors will usually be higher in Online, because Desktop's Other Names list becomes vendors, and that is fine. Accounts will usually be one lower, and estimates get skipped, and that is fine too. What is not fine is a transaction count that doesn't match, or a line saying account balances didn't match. If you see either, stop. Don't change anything in the new file to make the warning go away.

Your reconciliation history is gone, but the last one survived

Open Reconcile on any bank account in the new file and the history is empty, even though the register is full of R's. The last reconciliation you finished in Desktop is still there, though. It's sitting in the Beginning balance field. Match that number to a bank statement ending balance before you reconcile a single month forward. Until one full statement month reconciles to zero, treat every transaction that came over marked as reconciled as unproven. If you've ever had a QBO file that looked current and wasn't, this is the same problem with a different cause.

Payroll came over as lump sums, then got imported again

Intuit brings current-year paychecks over as totals, not as itemized checks. That's workable. The trouble starts when someone downloads a year-to-date report from the payroll company and imports it on top, because now the year is in the file twice. The check is simple and boring: payroll provider report, then the bank withdrawal, then the QBO entry, one pay period at a time. When all three agree, that period is verified. If your payroll provider's export doesn't carry dates on its year-to-date block, don't import it at all.

Notes, lists, and a few accounts didn't make the trip

Customer notes, custom lists, and the occasional account with its notes attached will not always be in the new file, and the import summary won't always tell you. This is why the reports you pulled before the export matter more than the export. If you have the general ledger and the audit log for every account, you can rebuild what dropped. If you didn't pull them and Desktop is already shut down, you're rebuilding from memory.

You paid someone out of a file that wasn't proven yet

Until the six reports match, don't pay a bill, print a check, send an ACH, or run a transfer out of the new file. Every payment you make out of an unproven file is a payment you may have to unwind. There's no shortcut here. Prove it first, then run the business from it.

This August I converted a file for a commercial cleaning company with 17 or 18 recurring accounts, all with their own quirks, like how often the rate went up, and by how much, and the deals each one had made with the owner. Like many business owners who bought the one-time license for QuickBooks Desktop, she was not happy that support had been discontinued, and she was not looking forward to the monthly fee that QBO charges. Especially since that fee seems to go up every year. Her file was from the 2013 version of Desktop. So, very outdated. I went on site and pulled about 50 different reports from her file before we touched anything, because the thing about the Desktop to Online migration tool is that it rarely transfers cleanly. Things go missing, or get duplicated, or land in a new format that throws off the whole system. Having the general ledger and the audit log for every account was what made this migration work.

The import summary always says something is off, and it will deactivate old accounts or void old invoices to get itself through. That isn't always a helpful solution, but it's what the tool wants you to do in order to migrate.

When the cutoff finally happened, she was missing several accounts and their notes, plus a number of lists she had built over the years. Had she used the tool by itself, she would've lost important information about her accounts and how each one paid. Not ideal.

I recreated everything that was missing from the reports I pulled before shutting Desktop down. The first thing I do on any migration is reconcile EVERY account to the bank statements and the history. Her QBO matched her Desktop exactly. And in the process I found a few thousand dollars she was owed that had gotten lost in paperwork. We collected it and brought her accounts receivable down to $0.

I do not want new bank-feed activity muddying the waters while I am still proving the migration.

First I validate the converted accounting file.

Once I am comfortable with the balances and the cutoff, I reconnect the bank and credit-card feeds to the accounts that came across in the migration.

I also pay close attention to the download start date. If the bank pulls transactions that were already recorded in Desktop, it can create duplicates immediately.

The bank feed should pick up where the proven Desktop history stopped. It should not overlap it.

When something fails one of my checks, I do not immediately post an adjustment.

I work backward.

First I confirm that I am comparing the same date range and accounting basis.

Then I isolate the account or report total that is different and work down into the underlying transactions.

I am trying to answer a very specific question:

Did the migration create the difference, or was the problem already in the Desktop books?

That distinction matters.

If the Desktop books were wrong, forcing QuickBooks Online to match them perfectly can simply recreate an old accounting problem in a newer system.

I document the difference, determine what caused it, and separate migration corrections from actual bookkeeping cleanup.

That keeps the migration process honest and leaves a much clearer record of what changed and why.

Do this the same day the export finishes, before anyone sends an invoice out of the new file. None of it needs an accountant. It needs someone patient, and it helps if that person didn't do the export.

1. Print the same six reports from both programs and lay them side by side. Balance sheet, trial balance (every account and its balance on one page), profit and loss, the report that shows who owes you money (AR aging), the one that shows who you owe (AP aging), and the balance in each bank and credit card account. Date every report to the last day anyone entered something in Desktop, not today. QuickBooks can show these reports two ways, cash or accrual, and it will happily give you one of each. Set both programs to accrual so you're comparing like with like. Now go number by number: total assets, total liabilities, net income, each bank balance, the AR total, the AP total. They should match exactly. If one doesn't, that is the first thing to solve, and you don't use the new file for anything until you know why.
2. Save the import summary and read the numbers, not the warnings. When the export finishes, QuickBooks shows you a summary and lets you download it. Keep it. It tells you how many transactions were in Desktop and how many landed in Online, and whether your account balances matched. Those two transaction counts should be identical. If they're off, or it says balances didn't match, something didn't come over, and no amount of clicking around in the new file will show you what. Stop there and get help before you fix anything by hand. The summary will also list warnings about vendors, templates, and estimates. Most of those are noise. The vendor count going up, for example, is Desktop's Other Names list turning into vendors. The transaction count is the one that matters.
3. Open Reconcile on each bank and credit card account and look at the beginning balance. In QBO, go to reconcile any bank account. The history will be empty, which looks alarming. Ignore that and look at the beginning balance it shows you. That number is the last reconciliation you finished in Desktop. Go find the bank statement that ends at exactly that balance. If you can find it, you're fine, and you reconcile forward from there one month at a time. If you can't find it, don't start reconciling to see what happens. It means Desktop and the bank were already apart before the conversion. Make a list of what's on the statements that never made it into Desktop, get those entered, and then reconcile.
4. Connect your bank last, and connect it to the accounts that already exist. Don't link your bank to QBO until step 1 matches. When you do, QBO will offer to create a brand-new account for the feed, named after whatever your bank calls it. Say no. Pick the checking or credit card account that came over from Desktop. Then set the start date for the download to the day after your last Desktop entry, so it doesn't pull in months of transactions you already have. If it still shows you checks and deposits that are already in the file, exclude them. Don't add them a second time.
5. Send logins, then lock the past. Nobody who used Desktop automatically has a login to the new file, and that includes your bookkeeper. Send the invites. Then set a closing date on the last day of Desktop and put a password on it, so nobody can go back and change the numbers you just proved.
6. If you collect sales tax, check what QBO thinks you owe against your last return. See the Washington section below.
7. Keep the Desktop file.Make a backup of the Desktop company file and put it somewhere you'll still find in three years. Once you replace the data in QBO you can't undo it from that side. The original on your computer is untouched until you delete it. Don't delete it.

If the Desktop file was already wrong before the move, the export carried that too. That's a cleanup, and it's a different job from a conversion.

Intuit's own transfer notes say some sales tax moves as journal entries, that sales tax won't copy for every transaction, and that payments you made in Desktop can apply to the wrong filings in QBO. For a Washington business that means your sales tax center may not agree with your last combined excise return. Before the next return is due, compare what QBO thinks you've collected and paid against what My DOR shows filed and paid. That's a setup check, and it's bookkeeping. Which classification your revenue belongs in is a tax question for whoever signs your returns.

QuickBooks Desktop is not simply disappearing. Intuit still supports current Desktop subscribers, and QuickBooks Desktop Enterprise remains an active product.

The better question is whether Desktop is still the right system for how your business works.

I usually look at the workflows first: who needs access, how information moves between people and systems, which Desktop features the business relies on, and what the owner expects the accounting process to look like after the move.

If QuickBooks Online is the better fit, then the migration should be planned and validated carefully. If Desktop still fits the business better, migration should not happen just because of a generic software deadline.

We've also moved a Contractor edition file, and those have their own quirks.

I handle QuickBooks Desktop to QuickBooks Online migrations as an accounting project, not just a file transfer.

Before the move, I review the Desktop file and preserve the reports I will need to validate the result.

After the migration, I compare the new QuickBooks Online file against the source books, investigate material differences, and identify cleanup that needs to happen before the new file is treated as reliable.

That can create a second benefit from the migration: old bookkeeping problems often become much easier to see when someone is deliberately comparing the old system to the new one.

If cleanup is required, I keep that work distinct from the migration itself so there is a clear record of what transferred and what was corrected afterward.

Schedule a Consultation · Financial Systems & Workflow Improvement