Moving from QuickBooks Desktop to QuickBooks Online is usually described as a conversion, which makes it sound like a file format problem. It is not. Some of your history comes across, some of it does not, and the parts that do not are rarely the parts anyone warns you about until you go looking for them in January.
If you are on the Mac edition, add a layer. Most guidance you will find online was written for the Windows version, and the two do not behave the same way.
Why the Mac version is its own problem
QuickBooks Desktop for Mac has always been a separate product rather than the same program on a different operating system. It stores data differently, its export options are narrower, and a good deal of published advice about migrating simply assumes menus you do not have.
In practice that means the route out is often indirect, and the first thing worth establishing is not how to move the file but what condition it is in. A migration copies your decisions forward. If the file is a decade of accumulated improvisation, you now have that in a new place, with a subscription attached.
What comes across, and what quietly does not
Broadly, the things you would expect to move do move: your chart of accounts, your customers and vendors, and your transaction history. What tends not to survive intact is everything wrapped around those transactions.
- Reconciliation history. Transactions may arrive still flagged as cleared, but the reconciliation reports themselves — the record of which statement each one was reconciled against — generally do not come with them.
- Bank feed connections. None of them transfer. Every account is reconnected from scratch on the other side.
- Custom templates and memorized reports. Invoice layouts and saved report formats are usually rebuilt rather than moved.
- Attachments. Receipts and documents attached to transactions frequently do not follow.
- Sales tax setup. QuickBooks Online handles sales tax on an entirely different model, so this is generally reconstructed rather than converted.
None of these are disasters on their own. They become one when you assume they came across and discover in month three that they did not.
The bank feeds will not come with you, and that is where duplicates start
This is the single most common complaint after a migration, and it is the one that quietly damages the books.
When you reconnect an account in QuickBooks Online, the bank typically offers to pull back ninety days of history — sometimes more. If that period overlaps with transactions already imported in the conversion, you now have the same activity twice: once from the migrated file, once from the fresh feed.
Nothing warns you. The register simply has two of everything for a stretch, your balance is wrong by the value of the overlap, and the account will not reconcile against a statement no matter how many times you check the arithmetic.
The fix is to decide a cutover date before connecting anything, then exclude everything the feed offers before that date rather than accepting it. It takes a few minutes per account and saves a cleanup.
And if one account simply refuses to connect at all — which happens, particularly with smaller banks and credit unions — that is not a reason to stall the whole migration. That account runs from statements until the connection is sorted out.
Your reconciliation history does not travel, so decide where you are starting from
Because the reconciliation reports do not come across, QuickBooks Online has no record of what was reconciled to which statement. Your first reconciliation in the new file effectively starts from a beginning balance you have to establish yourself.
Get that wrong and every subsequent month inherits the error. It is worth taking the statement for the month before your cutover, agreeing the closing balance to the penny, and treating that as the line everything after is built on.
Do not carry a chart of accounts you already know is wrong
A migration is the one moment when restructuring costs nothing extra, because you are touching everything anyway.
If you own property, this is where per-property tracking either gets set up properly or does not get set up at all. Once a year of transactions is coded to a flat chart of accounts with no class or location behind it, adding that structure later means revisiting all of it. We wrote about the setup in tracking multiple properties in QuickBooks Online, and it is far cheaper to do at the point of migration than six months afterward.
The same applies to accounts you inherited from whoever set the file up originally and have never used since.
Obsolete accounts and dead projects: purge before, not after
Almost every Desktop file that has been running for years carries a layer of things nobody has touched in a long time — jobs that closed, projects that never started, accounts created for one transaction in 2019.
Migrating them means paying to store them, scrolling past them in every dropdown, and giving yourself more chances to code something to the wrong place. Deactivating them before the move is quicker than doing it after, and unlike deleting, deactivating keeps the history attached to the transactions that used them.
The exception worth stating: do not deactivate anything with an open balance or an unreconciled transaction against it. Clear it first, or bring it across and deal with it on the other side.
When to do it
The cleanest cutover is the first day of a period you have already closed and reconciled — the start of a quarter, or better, the start of a year. That gives you a defensible line: everything before this date lives in the old file, everything after lives in the new one, and the boundary agrees with a bank statement.
Mid-year migrations are entirely possible and we do them regularly. They just require more care about that boundary, because you will be answering questions about it at tax time.
One thing worth doing regardless: keep the Desktop file. Not as a backup you never open, but as the authoritative record of everything before the cutover. You will want it eventually, and it is easier to keep it than to recreate it.
If you are looking at this and it feels like more than you signed up for
It usually is. The migration itself is often the small part — the work is deciding what the new file should look like, establishing where the balances start, and making sure the first reconciliation after the move actually ties.
We do this for real estate investors and operators, and the reason we care about the structure is that property books fall apart in specific ways when it is wrong. The wider picture is in bookkeeping for real estate investors, and if the file is also behind, catch-up bookkeeping covers what that involves.
Send us read-only access to the file before you move anything and we will tell you what is worth bringing across, what should be rebuilt, and where the balances need to start.
Recent Comments