Two-file financials path
The supported migration uses a Chart of Accounts CSV and a Journal CSV as the accounting source.
QuickBooks migration
Move the accounting history with a reviewable import.
LedgerHQ supports QuickBooks financials migration from Chart of Accounts and Journal CSV files, with upload, preview, validation, import history, and explicit confirmation when existing ledger data would be replaced.
Preview before import
Review parsed accounts, journal entries, balance, warnings, and current-company impact before committing.
Replacement safeguards
Replacing existing ledger data requires an explicit, current confirmation rather than an accidental re-upload.
01
Understand what the migration covers
The supported QuickBooks financials path focuses on the chart of accounts and journal history needed to establish LedgerHQ books. It is not a promise to copy every QuickBooks setting, attachment, operational module, bank connection, or third-party app relationship.
Firms should preserve the source export and define the intended cutoff before upload.
- Chart of Accounts CSV
- Journal CSV
- Selected LedgerHQ company
- Defined source and cutoff
02
Preview the accounting result
A preview should show whether accounts can be normalized, journal entries balance, dates and amounts parse correctly, and existing company data would be replaced.
Warnings should be resolved from the source data or an intentional mapping decision—not ignored simply to make the import finish.
- Account normalization
- Balanced journal validation
- Date and amount parsing
- Replacement and warning summary
03
Review the books after import
A successful import creates a starting accounting history, not a finished operating setup. The firm should review the chart, trial balance, financial statements, registers, bank-account mappings, statement coverage, and reconciliation readiness.
New bank activity should begin from a clear cutoff so it does not duplicate imported journal history.
- Trial balance and financial statements
- Account registers
- Bank account and feed setup
- Opening reconciliation position
How the workflow moves
A visible sequence, not a black box.
The exact action depends on permissions, company context, and the evidence available. The workflow stays inspectable from intake through review.
- 1Export the supported Chart of Accounts and Journal CSVs from QuickBooks.
- 2Upload both files to the correct LedgerHQ company and run preview.
- 3Resolve validation errors, review balances, and confirm any replacement impact.
- 4Import, then review reports, registers, bank setup, and reconciliation readiness.
Human control
Uploads and imports remain company-scoped. Preview comes first, and replacement of existing ledger data requires explicit confirmation tied to the current import plan.
Product boundary
The migration does not claim one-click parity for payroll, inventory, projects, attachments, bank rules, reconciliations, app integrations, or every QuickBooks feature.
Questions
What firms usually ask.
Can LedgerHQ import QuickBooks Online data?
LedgerHQ supports a financials import from QuickBooks Chart of Accounts and Journal CSV exports.
Will the import replace existing LedgerHQ books?
A preview identifies replacement impact. Replacing existing ledger data requires explicit confirmation; firms should never run replacement without reviewing the current company and plan.
Does the import bring over bank connections?
No. Plaid bank activity is configured separately in LedgerHQ after the financial history and cutoff are reviewed.
Keep exploring