A gentler move to new books
Choose a cutover, prove the opening balances, and keep a clear path back to the source.
· 6 min read
Choose the migration you actually need
A full-history move can be useful when you need transaction-level comparisons in the new system. An opening-balance move is often cleaner when the old file contains years of work that will remain available for reference. Decide before importing; mixing the two approaches usually creates more reconciliation work.
Pick a cutover date after a completed close whenever possible. Bring the chart of accounts, customer and vendor lists, open receivables and payables, inventory balances when relevant, and a trial balance dated at the cutover.
Stage, compare, then commit
Do not judge a migration by the number of rows it moved. Judge it by whether the new books agree with the source. Review account mappings and exceptions before posting, then compare the trial balance, profit and loss, balance sheet, receivables, payables, undeposited funds, and inventory for the same dates and accounting basis.
Document anything the source system transforms or cannot carry. A difference with a clear explanation is safer than a number that appears to tie because it was forced into the wrong account.
For QuickBooks Desktop files
QuickBooks Desktop company files use proprietary QBW, QBB, or QBM formats. Use Intuit’s supported conversion path to move the file into a temporary QuickBooks Online company, then connect that company for a one-time migration. If conversion is not practical, use a guided export of lists, the trial balance, open receivables and payables, and the limited history you need.
After the tie-out is approved, keep the old file read-only for the retention period your business requires, revoke the migration connection, and record who accepted the opening books.