Your accountant needs last year's books by Friday, you're switching systems, or you're closing a subscription and want your records out first. You click export, a tidy Excel file lands in your downloads, and it looks finished. That's exactly where most export problems start.
A clean workbook proves a file exists. It doesn't prove the balances agree, the date range is complete, or the records your next system needs are in there. Learning how to export QuickBooks data properly means choosing the right format for the job, then checking control totals against the source company before you change anything, retire anything, or hand the file to anyone else.
Do the export in that order and you'll catch gaps while the source is still open in front of you. Skip the checks and you'll usually find them weeks later, when someone asks why receivables don't tie out.
| Goal | Platform | Format | What It Captures |
|---|---|---|---|
| Review or share a report | Desktop or Online | Excel or CSV | Report as displayed for the chosen period |
| Move customer, vendor or item lists | Desktop | Excel or CSV | Names, balances and contact details |
| Export transactions by type and date | Desktop or Online | Excel | Filtered invoices, bills, receipts, estimates or purchase orders |
| Full Desktop company move | Desktop | Portable company file (.QBM) | Compressed company data package |
| Desktop disaster recovery | Desktop | Backup file | Complete restore point for the company |
| Online bulk archive | Online | Excel .zip | Selected reports and lists for a chosen date range |
For most requests, you're sending a report to a CPA, lender, or board member for review. Excel suits that job because the recipient can sort, filter, and add notes without rebuilding the layout. CSV suits analysis and import work because it's flat and tabular, with no formatting to strip out first.
Intuit's Desktop import and export guidance documents Microsoft Excel and comma-separated values (CSV) as the two standard spreadsheet formats for lists and transactions. Exportable records include customer, vendor, employee/payroll, and item lists, plus transactions filtered by name or transaction type. A customer or vendor list export can carry names, balances, and contact information, which is enough to seed a new system or clean up duplicates.
Don't confuse that with a company move. A flat CSV can't rebuild a company file, restore linked transactions, or carry your configuration. It gives you rows, and rows are useful only if rows are what you asked for.
A portable company file (.QBM) is the format built for moving a Desktop company from one machine or location to another. A backup file is the format built for disaster recovery, giving you a complete restore point if the working file corrupts or a machine fails. They sound interchangeable, and they're not, so pick based on whether you're relocating data or protecting it.
Practical rule: Name the goal first, review, list transfer, transaction migration, or archive, then choose the format. The wrong format doesn't fail loudly. It quietly leaves out the records you need for reconciliation.
If you're still deciding which platform you'll be working in next, compare the differences between QuickBooks Desktop and Online before you export, because the destination changes what you should pull and in what shape. I would settle that question first. Exporting twice because the first file didn't match the new home is wasted work you can avoid in ten minutes.
A clean Excel download proves that a file exists. It does not prove the export is complete. In Desktop, lists, reports, and transactions follow different export paths, so match each file to the task and check its totals against the source company.
The visual summary below maps the four main moves before you start clicking.
Sign in as administrator and back up first. Keep the backup in a separate folder from the exports. It gives you a restore point if a later change affects the company file.
Export lists from the relevant center. Open the Customer, Vendor, Employee, or Item center, choose Excel, then select a new or existing worksheet. A new worksheet preserves the exported values for comparison.
Filter transactions before exporting. In the relevant center, set filters by name or transaction type and date, then export to Excel or CSV. Check the filters before you run the export. A filter left over from earlier work can exclude records without making the resulting file look incomplete.
Export reports from the report screen. Open the report, set the date range, and confirm its on-screen totals. Then choose the Excel menu, create a new worksheet, select CSV if needed, and save the file. The export reflects the report as displayed, including its date range and filters.
Create a portable file for a company move. Go to File, Create Copy, Portable company file, choose a unique filename and destination, and save the .QBM file. It is a compressed company-data file for moving a Desktop company. Keep a conventional backup separately for disaster recovery.
Prepare the file for transfer. Switch to single-user mode and securely share the QuickBooks product, year, and administrator credentials with the recipient. Without the credentials, the recipient may be unable to open the file.
Restore the .QBM to a separate test location and open it. Confirm that lists load, compare key balances and report totals with the source company, and check several known transactions. A file that opens can still be missing records, so totals provide a stronger completeness check than appearance alone.
For list transfers between Desktop files, the QuickBooks IIF file format offers another interchange option. Check that it suits the data you need to transfer before using it.
A spreadsheet export contains selected rows or report results. A portable file carries company data for a move. Keep the spreadsheet exports as review records, and verify the portable file by restoring and checking it.
Keep the original exported workbook unchanged. Save a separate copy for sorting or cleanup so you can compare your edits with the data QuickBooks produced.
Online exports are built around selection. You choose the period, you choose which reports and lists are on, and anything you leave off is not included in the file. That makes the setup steps more important than the download itself.
The image below shows the reports dashboard environment where this work starts.
The bulk export gives you reports and lists. For transaction detail, open the relevant sales or expense area, set filters for transaction type and date, apply them, and export to Excel. Cover invoices, receipts, bills, estimates, and purchase orders one type at a time, because exporting only the categories visible on screen is a common way people end up with partial history.
The walkthrough below shows the export screens in motion, which helps if your menus look slightly different from the written steps.
Save the ZIP and each workbook as read-only, with the period and export date in the filename. A file called "export final 2" tells the next person nothing. A file named with the fiscal year and export date tells them exactly what they're holding.
If another system needs the data connected rather than downloaded, look at how integration with QuickBooks Online works before you commit to repeated manual exports. Manual downloads suit a one-time archive. They get error-prone fast when someone has to repeat them every month.
For a multi-year archive, run one export per fiscal year instead of one large file. Smaller, year-bounded files are easier to verify, easier to re-run if one year fails a check, and much easier for an auditor or successor bookkeeper to review. Expect some reshaping afterward too, since the output is Excel and a receiving system may want a different structure than the one QuickBooks produces.
A bookkeeper exports a full year, opens a tidy workbook, and sees plausible totals. After the migration, recurring invoices are missing because templates were not included with posted transactions. The file opened successfully, but the transfer is incomplete. A clean Excel download proves only that a file exists; control totals checked against the source company prove whether the export is usable.
Intuit's guide to exporting data, reports and lists from QuickBooks Online explains that the migration tool can export financial data with or without transactions. It also states that product and service inventory is not exported through that route, and that reports may differ because of export limitations. Treat the export as a set of files to verify, not a guaranteed copy of every company record.
Some records and settings need their own export or documentation. Check each item before closing access to the source company:
A business preparing for a lender review or grant audit may need more history than a sole proprietor archiving a closed year. Decide what to preserve before access to the source company ends.
Save a short record beside the exported files. Include the company name, accounting basis, date range, export timestamp, and name of the person who ran the export. That information helps a future reviewer understand what the files contain and how they were produced.
Acceptance standard: An export is complete only when its totals agree with the source company, account by account, for the same period.
| Control Total | Where to Pull It | What to Compare |
|---|---|---|
| Ending trial balance | Trial balance report, period end date | Balance for each account |
| General ledger totals | General ledger report, same date range | Total debits and total credits |
| Accounts receivable | A/R aging summary | Total open balance |
| Accounts payable | A/P aging summary | Total open balance |
| Transaction count | Transaction list filtered by type and date | Number of rows for each transaction type |
Run the trial balance and general ledger in the source company for the export's end date. Compare each account and the total debits and credits with the exported figures. Then compare A/R and A/P aging totals. These subledger checks can reveal missing records even when the trial balance balances.
Count transactions by type in both the source and the export. Matching dollars with different counts can indicate duplicated or merged records. Matching counts with different dollar totals can point to a date-range or accounting-basis mismatch.
Check beginning and ending balances for the period, too. If the opening balances match but the closing balances do not, investigate activity within the period. If the opening balances already differ, confirm that you are comparing against the correct starting point before exporting again.
Trace every variance to the record that caused it. Do not edit exported rows just to force a tie-out. That hides the discrepancy instead of resolving it. If a category is missing, re-export that category and repeat the full comparison, not just the check for the new file.
Keep the source totals, variances, resolutions, and exporter's name together in one control sheet beside the read-only files. It gives a reviewer a clear record of what was checked and how differences were handled. Teams coordinating an accounting transfer with a broader system move can consult a CTO's cloud migration roadmap for 2026 for transition sequencing; accounting sign-off still depends on the control totals.
Keep the source company available until every check passes. If a check fails after access ends, resolving it may require reconstructing records from other documents.
The right choice depends on who needs the data and for how long. A one-time export is a snapshot, accurate on the day you take it and stale the day after. That's fine for closing a year, handing a defined dataset to an accountant, or keeping evidence for a specific period, and it's the wrong tool for anything people still work in daily.
If you go the backup route, build it as a routine rather than a reaction to a scare. The case for treating backups as a deliberate habit is laid out well in this piece on how to protect accounting data with reliable backups. For the QuickBooks-specific mechanics, our guide to backing up QuickBooks covers the restore side, which is the part people skip until they need it.
This decision isn't permanent. You can archive closed years now, keep working in a live file, and change the arrangement later when staffing or software changes. What you can't do later is verify an export against a source company you no longer have.
So run one test export this week for a closed period. Complete the control-total checks, resolve whatever they surface, and store the verified files, the control sheet, and your company note where your team can find them. A boring, successful test on old data is worth more than a confident first attempt on the live migration.
If your team needs the live company file accessible every day while you archive and verify exports on your own schedule, Cloudvara hosts QuickBooks Pro, Premier, Enterprise, and other versions on a fully managed dedicated server that your staff can reach from Macs, PCs, tablets, and phones. Visit Cloudvara to see how hosted access keeps one working file available to everyone while your verified archives stay safely stored alongside it.
