Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
Define the purpose and required retention with the responsible accountant, tax adviser, lawyer, regulator, insurer, or contract owner; inventory every record location; export financial reports, detailed transactions, lists, nonposting records, attachments, payroll and tax records, audit evidence, user and integration records, and product-native backup where available; hash or otherwise inventory the files; open and reconcile samples; store protected copies; and test retrieval before cancelling access.
Best for: administrators, owners, accountants, auditors, and businesses preparing archives, handoffs, or product exit
What this guide covers—and what it does not
The page owns one search intent: exporting and retaining a complete, verifiable QuickBooks accounting record package. Related jobs have their own canonical guides so you can move between them without mixing product selection, setup, troubleshooting, and migration advice.
- This page owns portable exports, archive completeness, verification, retention ownership, and exit readiness.
- The backup-and-restore guide owns operational recovery after deletion, corruption, import, or service incident.
- It does not prescribe a universal retention period or claim that an Excel export can recreate a QuickBooks company.
Evidence-first workflow
Create an archive that another person can verify
An export is complete only when its scope is known, files open, totals reconcile, and the organization can retrieve them later.
- 1
Scope
Define entities, products, regions, periods, legal holds, retention owners, users, apps, payroll, tax, and evidence required.
Evidence: The archive manifest is approved.
- 2
Export
Collect native backups where available plus reports, detail, lists, nonposting records, attachments, audit and external-system evidence.
Evidence: Every manifest category has a file or explained exception.
- 3
Verify
Open files, record counts and hashes, reconcile statements and control totals, and sample attachments and links.
Evidence: The package is readable and internally consistent.
- 4
Protect
Encrypt, restrict access, separate copies, document keys, and apply retention and legal-hold rules.
Evidence: Authorized retrieval and deletion controls are tested.
- 5
Exit
Confirm downstream systems, revoke integrations and access, retain cancellation evidence, and test future retrieval.
Evidence: The organization can answer an audit question without live product access.
Decision control
Choose from evidence, not a feature list
Use the same four gates for exporting and retaining a complete, verifiable QuickBooks accounting record package: define the job, surface constraints, choose the smallest workable option, then verify the records.
Match the export to the purpose
Different incidents require different artifacts; no single download is a universal backup, audit package, or migration file.
| Your situation | Direction | Why |
|---|---|---|
| Recover from accidental change or deletion | Use the backup and recovery plan | Reports and spreadsheets may document data but cannot necessarily restore the application state. |
| Respond to audit or tax inquiry | Create a period-specific evidence package | Reports, detail, sources, filings, approvals, and reconciliation need to be reproducible. |
| Migrate to another accounting system | Build an export-to-target reconciliation | A successful import does not prove historical balances, open items, tax, payroll, or attachments transferred. |
| Cancel QuickBooks or a connected app | Complete and test the exit archive first | Access, export features, logs, and attachments may be unavailable after cancellation. |
Inventory records across QuickBooks and connected systems
List company files or Online companies, legal entities, fiscal years, bank and card statements, sales, purchases, inventory, payroll, tax, fixed assets, loans, attachments, recurring records, audit logs, users, permissions, integrations, ecommerce channels, payment processors, expense systems, and external workpapers. Name the authoritative system for each.
Document retention authority by record class and jurisdiction, including legal holds, contracts, grant or donor requirements, insurance, payroll, tax, privacy, and industry obligations. Do not adopt one internet retention table as universal policy.
Export posting, nonposting, evidence, and configuration records
Use the current product export paths for financial statements, trial balance, general ledger, transaction detail, journals, account lists, customers, vendors, products/services, open receivables and payables, inventory, bank reconciliations, sales tax, budgets, estimates, purchase orders, recurring templates, attachments, receipts, payroll and tax records, audit evidence, users, and connected apps.
For Desktop, retain verified native backups and product/version information in addition to portable reports. For Online, do not describe a report export as a full restorable backup. Record missing or inaccessible categories and the approved alternative evidence.
Verify readability, completeness, and accounting control totals
Open every file type on a second authorized device or environment, check filenames and periods, record row or document counts, and calculate hashes or a tamper-evident inventory where appropriate. Sample attachments and confirm they match transaction references.
Reconcile exported trial balance and financial statements, receivables, payables, inventory, fixed assets, payroll liabilities, sales tax, loans, bank accounts, and equity to the approved close. For migrations, compare source and target at record and control-total levels and retain unresolved differences.
Protect the archive and complete product exit safely
Store at least two protected copies under the approved security and geographic policy, restrict sensitive payroll, tax, customer, vendor, bank, and identity data, document encryption keys and custodians, and test retrieval. Define legal-hold override and defensible deletion.
Before cancellation, confirm invoices and statements were delivered, filings and payments completed, apps exported, bank connections disconnected where appropriate, users revoked, administrator ownership transferred, billing stopped, and cancellation evidence retained. Schedule future readability tests.
Retention and deletion requirements can conflict across tax, legal, privacy, employment, grant, contract, and regulatory regimes. Obtain qualified advice and document the authority for each schedule.
Completion checklist
Do not call the decision or setup complete until someone independent of the initial change can verify these items.
Frequently asked questions
Is exporting QuickBooks reports the same as a backup?
No. Reports and lists are valuable portable evidence, but they may not restore transactions, links, settings, attachments, audit history, payroll, apps, or the complete company state.
What should I export before cancelling QuickBooks Online?
At minimum inventory and export financial reports, transaction detail, lists, open items, reconciliations, tax and payroll records, nonposting records, attachments, audit and user evidence, app data, and cancellation documentation appropriate to the business.
How long should QuickBooks records be kept?
There is no universal period. Use current tax, payroll, legal, privacy, industry, contract, grant, insurance, and litigation-hold requirements for each record class and jurisdiction.
Still comparing adjacent tasks? Use the complete guide library to find the one page that owns your intent.
Optional free utilities
Tools that support this workflow
These run in your browser and can help prepare or inspect files. They do not replace reconciliation, source-document review, or an accountant’s approval.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.