Migrating QuickBooks Desktop to Online: what happens to your bank history

The short answer: the migration tool moves your ledger — the posted transactions, balances, lists and history in the company file. It does not move your bank feed: the connection to the bank, the For Review queue, and your bank rules are features of QuickBooks Online that start from nothing on the other side. Most of the post-migration "my bank transactions are missing" questions come from that distinction, and most of the cleanup is filling the gap between your last reconciled statement and the day the new feed begins.

Intuit's migration process, limits and tooling change over time; treat their current documentation as the authority on the mechanics. This guide covers the bank-history part specifically, as of 2026.

What carries over, and what doesn't

• Carries over: posted bank transactions, account balances, the chart of accounts, customers and vendors, and (subject to the tool's limits) transaction history. Reconciliation results come across as cleared transactions; the reconciliation reports themselves generally don't, so keep the Desktop PDFs.
• Doesn't carry over: the bank feed connection, downloaded-but-unmatched transactions, bank rules, and memorized-transaction automation. Some Desktop-only features (certain inventory, payroll and reporting setups) also don't map — outside this guide's scope, but check Intuit's current list before you move.

Before you migrate: get a clean cut-off

1. Reconcile every bank and credit-card account in Desktop to its latest statement. Note the statement date and ending balance for each — that's your cut-off line.
2. Clear the downloaded-transactions queue. Anything sitting unmatched in Desktop's bank feed center won't come across; either post it or accept that you'll re-import it.
3. Export the reconciliation reports and back up the company file. If a balance looks wrong in Online later, these are how you prove which side drifted.

After you migrate: reconnect, then backfill the gap

Connect each account to its bank in QuickBooks Online. The feed pulls a limited history — commonly around 90 days, and we've covered what to do when you need more than that. The key move is to set the feed's start date to the day after your cut-off (or exclude anything before it in For Review), because the ledger already contains every transaction up to the cut-off. Letting the feed re-deliver transactions you migrated is how migrated books end up with duplicates.

Then there are two gaps to check:

• Cut-off → feed start. If more than the feed window passed between your last reconciled statement and connecting the account, the middle is missing. Download the statements for those months, convert them to .qbo, and upload them into the bank transactions view. A .qbo import lands in For Review exactly like feed transactions and carries stable IDs, so an overlap with the feed is matched rather than duplicated.
• Post-migration duplicates. If the feed delivered transactions that were already in the migrated ledger, match them (QuickBooks usually suggests the match) rather than adding them. A balance that is exactly double a recent transaction is the tell.

Rebuild the rules — and consider doing it better

Bank rules don't migrate, and rebuilding dozens of them by hand is tedious. It's also a chance to fix the categorization habits Desktop accumulated. If the backlog is large, importing the statements with categories already assigned to your chart of accounts — which our converter does on the Pro and Firm tiers, learning from what you confirm — means the transactions land in For Review with accounts attached rather than waiting for rules to exist. Either way, run the first month of categorization deliberately; Online's suggestions learn from your early choices.

Verify the balances, then stop

For each account, the QuickBooks Online balance on the cut-off date should equal the Desktop reconciliation's ending balance to the cent. After the backfill, reconcile the first Online statement normally. If either check fails, the working papers from before the migration tell you which side to look at — and a two-sided reconciliation template makes the difference legible faster than staring at two registers.