QuickBooks for Mac to Online: fixing a silent export timeout
A QuickBooks for Mac export to QuickBooks Online stalls with no error and no progress; our engineers show how to get the conversion done.
The move from QuickBooks for Mac to QuickBooks Online fails in two ways. The loud way ends in an error code. The quiet way ends in nothing at all: the progress indicator freezes, no message appears, and no confirmation email ever lands. This playbook is about the quiet way.
The situations this playbook covers
Run this playbook when the export command starts and then stalls with no error. It also fits when a retry ran overnight and produced nothing in the Online company. Use it as well when a cutover date is close and the export has already failed twice.
The causes behind a silent timeout
The Mac export uploads the whole company file to the import service and waits. The upload has no resume. A dropped connection, a sleeping Mac, or a busy import queue all look identical from your side: silence.
Size is the second cause. A file with many years of history, or lists holding tens of thousands of names, can run past what the import path accepts. The gateway gives up without telling the desktop app.
The third cause sits inside the file. List damage that Verify has never flagged can stop the import on a single record. The conversion dies there and nothing reports back.
Phase 1: rule out the simple causes
Clear these before any retry, because each of them has ended a silent stall in the field.
- Sign out of the Intuit account inside QuickBooks for Mac, then sign back in. A stale session can stop the export before it begins.
- Move to a wired connection if you can, pause cloud sync clients, and stop backup software that touches the company file mid-export.
- Set the Mac so it cannot sleep during the transfer. A dim screen is fine; a sleeping system kills the upload.
- Install the latest release of the Mac edition you are on, then restart the Mac.
- Close every other company file and make sure no second export attempt is queued.
Rollback point: none yet. Nothing in this phase changes the file.
Phase 2: verify the file and measure it
Make a fresh backup first. QuickBooks for Mac writes backups as disk images; treat that image as the source of truth for the rest of the job.
Run Verify Data from the Utilities submenu of the File menu. If Verify reports damage, run Rebuild and verify again, and repeat until Verify comes back clean. Damage that will not clear must be repaired before any export can succeed; see our QuickBooks for Mac file repair service for that path.
Then measure. Note the file size, the account count, and how far back the history runs. An oversized file is a preparation problem, not a retry problem; our desktop file preparation for QuickBooks Online import addresses exactly that.
Rollback point: the verified disk image. Keep it until the Online books tie out.
Phase 3: one controlled retry, then stop
With Phases 1 and 2 clean, allow exactly one more attempt. Run it wired, run it awake, and run it while the office network is quiet. Stay present for the first ten minutes so you can watch a stall begin.
Our engineers call off an attempt when nothing has moved for an hour, network traffic included. A second silent failure is your answer. Retrying the same file over the same path yields no new information, and every attempt costs a day.
A failed export does not modify the company file, so there is nothing to undo. If a partial import landed in a trial Online company, begin the next attempt in a fresh company instead of layering onto it.
Phase 4: finish the conversion off the export path
When the built-in export will not finish, the work moves off the Mac. The company file gets examined directly, the condition breaking the migration is found and repaired, and the conversion to Online runs on the service side. Our QuickBooks data migration service handles this end to end.
Three things are needed from you: the backup disk image or company file, its admin password, and the target, meaning the country and edition of the Online company plus the cutover date. Full history usually carries; where it cannot, the conversion starts from a chosen date.
Fix the cutover date now and stop entering transactions in the Mac file after it. Anything entered past that date needs a second pass into Online, and that gap is avoidable.
Rollback point: still the Phase 2 image. Nothing gets overwritten along the way; the Online company is new.
Phase 5: prove the import in QuickBooks Online
Do not call the conversion done because the import finished. Call it done when the numbers agree.
Run a trial balance in the Mac file as of the cutover date, then run the same report in Online. Every account should tie to the cent. Check the AR and AP aging totals, the inventory value, and each bank and card balance.
Spot-check the oldest open invoice, the oldest open bill, and a few transactions of each type from recent months. Expect reconciliation status not to carry from desktop, so reconcile the first statement in Online by hand. Bank feeds and app connections are rebuilt fresh. If anything looks off inside the new company, our QuickBooks Online troubleshooting guides cover the Online side.
A clean outcome
A clean finish looks like this: the Online trial balance ties to the desktop one at the cutover date, the lists are whole, and the first Online reconciliation is done. Bank feeds are connected, the Mac file is closed for entry, and its final backup is archived with the cutover date written on it.
The silence never tells you what went wrong. The file does, once an engineer opens it, and that step is what ends the loop.